Get email notifications whenever Rithum for Brands Status Page creates, updates or resolves an incident.
Get webhook notifications whenever Rithum for Brands Status Page creates an incident, updates an incident, resolves an incident or changes a component status.
Visit our support site.
All Systems Operational
System
?
Operational
Platform
Operational
Products
?
Operational
Sell: Marketplaces, First Party & Webstores
?
Operational
Fulfill: Orders & Fulfillment
?
Operational
Marketing
?
Operational
Shoppable Media
?
Operational
API
?
Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Past Incidents
Nov 30, 2025
No incidents reported today.
Nov 29, 2025
No incidents reported.
Nov 28, 2025
No incidents reported.
Nov 27, 2025
No incidents reported.
Nov 26, 2025
No incidents reported.
Nov 25, 2025
No incidents reported.
Nov 24, 2025
Resolved -
This incident has been resolved. All systems are operating as expected, and ongoing monitoring confirms platform stability.
If you notice any discrepancies or need assistance, please contact your Client Success Manager or email support-brands@rithum.com.
Nov 24, 23:18 UTC
If you notice any discrepancies or need assistance, please contact your Client Success Manager or email support-brands@rithum.com.
Nov 24, 23:18 UTC
Update -
Access to the Rithum for Brands Platform has now been fully restored for all clients following the outage that occurred at 11:40 a.m. ET on November 20, 2025.
All systems are now operating as expected.
To help you get back to business smoothly, we’ve created this go-live guide, https://learn.rithum.com/pages/brands-platform-go-live-guide, with key steps to review, as well as FAQs to answer common questions. Please refer to the guide for recommendations on confirming your data, reviewing recent orders and inventory, and best practices for resuming operations.
If you notice any discrepancies or need assistance, please contact your Client Success Manager or email support-brands@rithum.com.
Nov 23, 17:53 UTC
All systems are now operating as expected.
To help you get back to business smoothly, we’ve created this go-live guide, https://learn.rithum.com/pages/brands-platform-go-live-guide, with key steps to review, as well as FAQs to answer common questions. Please refer to the guide for recommendations on confirming your data, reviewing recent orders and inventory, and best practices for resuming operations.
If you notice any discrepancies or need assistance, please contact your Client Success Manager or email support-brands@rithum.com.
Nov 23, 17:53 UTC
Update -
Access to the Rithum for Brands Platform has now been fully restored for all clients following the outage that occurred at 11:40 a.m. ET on November 20, 2025.
Orders from all channels are importing. We have resumed sending product data.
Nov 22, 19:43 UTC
Orders from all channels are importing. We have resumed sending product data.
Nov 22, 19:43 UTC
Monitoring -
Access to the Rithum for Brands Platform has now been fully restored for all clients following the outage that occurred at 11:40 a.m. ET on November 20, 2025.
Orders from all channels are importing. Once we’ve worked through the orders backlog, we will then proceed with product data.
Nov 22, 09:36 UTC
Orders from all channels are importing. Once we’ve worked through the orders backlog, we will then proceed with product data.
Nov 22, 09:36 UTC
Update -
We continue to restore access to the Rithum for Brands Platform following the outage that occurred at 11:40 a.m. ET on November 20, 2025.
All clients now have access and certain channels are actively transacting. Another communication will be published to confirm when full restoration is complete.
Nov 22, 08:10 UTC
All clients now have access and certain channels are actively transacting. Another communication will be published to confirm when full restoration is complete.
Nov 22, 08:10 UTC
Update -
We have begun restoring access to the Rithum for Brands Platform following the outage that occurred at 11:40 a.m. ET on November 20, 2025.
Some clients already have access and certain channels are actively transacting. We are continuing to load client data and will expand access to more clients over the coming hours.
We are confident Rithum’s platform is ready to support your business during peak season. We will be closely monitoring performance, but do not anticipate any further risk to platform up-time in the days ahead as our teams have worked to thoroughly validate all restored components of our platform for accuracy and stability.
Nov 22, 06:04 UTC
Some clients already have access and certain channels are actively transacting. We are continuing to load client data and will expand access to more clients over the coming hours.
We are confident Rithum’s platform is ready to support your business during peak season. We will be closely monitoring performance, but do not anticipate any further risk to platform up-time in the days ahead as our teams have worked to thoroughly validate all restored components of our platform for accuracy and stability.
Nov 22, 06:04 UTC
Update -
We are continuing to work through a 6-stage recovery process:
-Assessment – Identify what needed rebuilding. (Complete)
-Infrastructure Rebuild – Restore core systems. (Complete)
-Database Platform Rebuild – Rebuild SQL Server environment. (Complete)
-Data Restoration – Continued Progress:
--System-level databases (complete)
--Client-specific databases (Over 75% complete)
--Supporting databases (complete)
-Application Recovery – Bring client services online in a controlled, staggered way (continued progress)
-Final Validation – Confirm all systems and services are functioning before closing the incident (after)
Nov 22, 05:09 UTC
-Assessment – Identify what needed rebuilding. (Complete)
-Infrastructure Rebuild – Restore core systems. (Complete)
-Database Platform Rebuild – Rebuild SQL Server environment. (Complete)
-Data Restoration – Continued Progress:
--System-level databases (complete)
--Client-specific databases (Over 75% complete)
--Supporting databases (complete)
-Application Recovery – Bring client services online in a controlled, staggered way (continued progress)
-Final Validation – Confirm all systems and services are functioning before closing the incident (after)
Nov 22, 05:09 UTC
Update -
We are continuing to work through a 6-stage recovery process:
-Assessment – Identify what needed rebuilding. (Complete)
-Infrastructure Rebuild – Restore core systems. (Complete)
-Database Platform Rebuild – Rebuild SQL Server environment. (Complete)
-Data Restoration – Continued Progress:
--System-level databases (complete)
--Client-specific databases (Over 50% complete)
--Supporting databases (complete)
-Application Recovery – Bring client services online in a controlled, staggered way (continued progress)
-Final Validation – Confirm all systems and services are functioning before closing the incident (after)
Nov 22, 03:11 UTC
-Assessment – Identify what needed rebuilding. (Complete)
-Infrastructure Rebuild – Restore core systems. (Complete)
-Database Platform Rebuild – Rebuild SQL Server environment. (Complete)
-Data Restoration – Continued Progress:
--System-level databases (complete)
--Client-specific databases (Over 50% complete)
--Supporting databases (complete)
-Application Recovery – Bring client services online in a controlled, staggered way (continued progress)
-Final Validation – Confirm all systems and services are functioning before closing the incident (after)
Nov 22, 03:11 UTC
Update -
We are continuing to work through a 6-stage recovery process:
-Assessment – Identify what needed rebuilding. (Complete)
-Infrastructure Rebuild – Restore core systems. (Complete)
-Database Platform Rebuild – Rebuild SQL Server environment. (Complete)
-Data Restoration – Continued Progress:
--System-level databases (complete)
--Client-specific databases (continued progress)
--Supporting databases (complete)
-Application Recovery – Bring client services online in a controlled, staggered way (continued progress)
-Final Validation – Confirm all systems and services are functioning before closing the incident (after)
Nov 22, 01:07 UTC
-Assessment – Identify what needed rebuilding. (Complete)
-Infrastructure Rebuild – Restore core systems. (Complete)
-Database Platform Rebuild – Rebuild SQL Server environment. (Complete)
-Data Restoration – Continued Progress:
--System-level databases (complete)
--Client-specific databases (continued progress)
--Supporting databases (complete)
-Application Recovery – Bring client services online in a controlled, staggered way (continued progress)
-Final Validation – Confirm all systems and services are functioning before closing the incident (after)
Nov 22, 01:07 UTC
Update -
We are continuing to work through a 6-stage recovery process:
-Assessment – Identify what needed rebuilding. (Complete)
-Infrastructure Rebuild – Restore core systems. (Complete)
-Database Platform Rebuild – Rebuild SQL Server environment. (Complete)
-Data Restoration – Continued Progress:
--System-level databases (complete)
--Client-specific databases (continued progress)
--Supporting databases (complete)
-Application Recovery – Bring client services online in a controlled, staggered way (continued progress)
-Final Validation – Confirm all systems and services are functioning before closing the incident (after)
Nov 21, 22:56 UTC
-Assessment – Identify what needed rebuilding. (Complete)
-Infrastructure Rebuild – Restore core systems. (Complete)
-Database Platform Rebuild – Rebuild SQL Server environment. (Complete)
-Data Restoration – Continued Progress:
--System-level databases (complete)
--Client-specific databases (continued progress)
--Supporting databases (complete)
-Application Recovery – Bring client services online in a controlled, staggered way (continued progress)
-Final Validation – Confirm all systems and services are functioning before closing the incident (after)
Nov 21, 22:56 UTC
Update -
We are continuing to work through a 6-stage recovery process:
-Assessment – Identify what needed rebuilding. (Complete)
-Infrastructure Rebuild – Restore core systems. (Complete)
-Database Platform Rebuild – Rebuild SQL Server environment. (Complete)
-Data Restoration – (In-Progress):
--System-level databases (Complete)
--Client-specific databases (In-Progress)
--Supporting databases (Complete)
-Application Recovery – Bring client services online in a controlled, staggered way. (In-Progress)
-Final Validation – Confirm all systems and services are functioning before closing the incident. (After)
Nov 21, 20:57 UTC
-Assessment – Identify what needed rebuilding. (Complete)
-Infrastructure Rebuild – Restore core systems. (Complete)
-Database Platform Rebuild – Rebuild SQL Server environment. (Complete)
-Data Restoration – (In-Progress):
--System-level databases (Complete)
--Client-specific databases (In-Progress)
--Supporting databases (Complete)
-Application Recovery – Bring client services online in a controlled, staggered way. (In-Progress)
-Final Validation – Confirm all systems and services are functioning before closing the incident. (After)
Nov 21, 20:57 UTC
Update -
Our ETA for platform restoration is end of day Friday November 21, 2025 Pacific Standard Time. It is possible that this timeline changes given the size and complexity of the restoration efforts.
We are continuing to work through a 6-stage recovery process:
-Assessment – Identify what needed rebuilding. (Complete)
-Infrastructure Rebuild – Restore core systems. (Complete)
-Database Platform Rebuild – Rebuild SQL Server environment. (Complete)
-Data Restoration – (In-Progress):
--System-level databases (Complete)
--Client-specific databases (In-Progress)
--Supporting databases (Complete)
-Application Recovery – Bring client services online in a controlled, staggered way. (In-Progress)
-Final Validation – Confirm all systems and services are functioning before closing the incident. (After)
Nov 21, 18:56 UTC
We are continuing to work through a 6-stage recovery process:
-Assessment – Identify what needed rebuilding. (Complete)
-Infrastructure Rebuild – Restore core systems. (Complete)
-Database Platform Rebuild – Rebuild SQL Server environment. (Complete)
-Data Restoration – (In-Progress):
--System-level databases (Complete)
--Client-specific databases (In-Progress)
--Supporting databases (Complete)
-Application Recovery – Bring client services online in a controlled, staggered way. (In-Progress)
-Final Validation – Confirm all systems and services are functioning before closing the incident. (After)
Nov 21, 18:56 UTC
Update -
Rithum for Brands Platform is still experiencing a platform outage. This was NOT caused by a cyberattack, ransomware, or malicious actors. This was an unusual event during regular maintenance on November 20, 2025.
This incident affected hundreds of servers and databases. Each database must be restored and checked to make sure everything is accurate and stable.
We’ve been working through a 6-stage disaster recovery process:
-Assessment – Identify what needed rebuilding. (Complete)
-Infrastructure Rebuild – Restore core systems. (Complete)
-Database Platform Rebuild – Rebuild SQL Server environment. (Complete)
-Data Restoration – Currently in progress:
--System-level databases (nearly complete)
--Client-specific databases (next)
--Supporting databases (after)
-Application Recovery – Bring client services online in a controlled, staggered way.
-Final Validation – Confirm all systems and services are functioning before closing the incident.
We cannot give a specific time for the platform going live given the size and complexity of the restoration efforts.
Our teams are fully focused on restoring service as quickly as possible.
We will share progress updates on this page every two hours, even if there is no new information.
In addition to your customer success manager, you can also contact us at the support email support-brands@rithum.com
Nov 21, 16:25 UTC
This incident affected hundreds of servers and databases. Each database must be restored and checked to make sure everything is accurate and stable.
We’ve been working through a 6-stage disaster recovery process:
-Assessment – Identify what needed rebuilding. (Complete)
-Infrastructure Rebuild – Restore core systems. (Complete)
-Database Platform Rebuild – Rebuild SQL Server environment. (Complete)
-Data Restoration – Currently in progress:
--System-level databases (nearly complete)
--Client-specific databases (next)
--Supporting databases (after)
-Application Recovery – Bring client services online in a controlled, staggered way.
-Final Validation – Confirm all systems and services are functioning before closing the incident.
We cannot give a specific time for the platform going live given the size and complexity of the restoration efforts.
Our teams are fully focused on restoring service as quickly as possible.
We will share progress updates on this page every two hours, even if there is no new information.
In addition to your customer success manager, you can also contact us at the support email support-brands@rithum.com
Nov 21, 16:25 UTC
Update -
Our engineering team still continues to work on restoring full functionality and efforts are progressing as expected.
Nov 21, 13:48 UTC
Nov 21, 13:48 UTC
Update -
Our engineering team still continues to work on restoring full functionality and efforts are progressing as expected.
Nov 21, 10:39 UTC
Nov 21, 10:39 UTC
Update -
Our engineering team still continues to work on restoring full functionality and efforts are progressing as expected.
Nov 21, 08:22 UTC
Nov 21, 08:22 UTC
Update -
Our engineering team continues to work on restoring full functionality and efforts are progressing as expected.
Nov 21, 06:17 UTC
Nov 21, 06:17 UTC
Update -
We are continuing to work on a fix for this issue.
Nov 21, 04:15 UTC
Nov 21, 04:15 UTC
Update -
Our engineering team continues to work on restoring full functionality and efforts are progressing as expected.
Nov 21, 03:18 UTC
Nov 21, 03:18 UTC
Identified -
As of 11:40 a.m. ET, November 20, 2025, the Rithum for Brands Platform is experiencing a full outage.
Your marketplace listings remain active and will continue to support sales, and you can still access your channel accounts outside of the Rithum platform.
During the outage, feeds, orders, inventory, and ad campaigns will not update in Rithum. Restoration will take several hours.
This was an unusual event during regular maintenance that impacted a key database. We have identified a clear path to resolution and are focused on restoring full functionality as quickly as possible. The impact was limited to specific hardware and systems, which we have now contained.
Nov 20, 22:13 UTC
Your marketplace listings remain active and will continue to support sales, and you can still access your channel accounts outside of the Rithum platform.
During the outage, feeds, orders, inventory, and ad campaigns will not update in Rithum. Restoration will take several hours.
This was an unusual event during regular maintenance that impacted a key database. We have identified a clear path to resolution and are focused on restoring full functionality as quickly as possible. The impact was limited to specific hardware and systems, which we have now contained.
Nov 20, 22:13 UTC
Update -
This issue is still ongoing. Our Engineering team is working to resolve this issue with high priority. This alert will be updated as more information is available.
Nov 20, 19:33 UTC
Nov 20, 19:33 UTC
Update -
This issue is still ongoing. Our Engineering team is working to resolve this issue with high priority. This alert will be updated as more information is available.
Nov 20, 17:30 UTC
Nov 20, 17:30 UTC
Investigating -
We are currently investigating connectivity issues with Rithum. As a result, you may be unable to log in to the Rithum for Brands platform or access certain features. We are working on a resolution as our highest priority. We apologize for the inconvenience.
Nov 20, 16:51 UTC
Nov 20, 16:51 UTC
Nov 23, 2025
Nov 22, 2025
Nov 21, 2025
Nov 20, 2025
Nov 19, 2025
No incidents reported.
Nov 18, 2025
No incidents reported.
Nov 17, 2025
No incidents reported.
Nov 16, 2025
No incidents reported.