ChannelAdvisor Status

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.

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 [email protected].

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. We have resumed sending product data.

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.

Identified: 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.

Identified: 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.

Identified: 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)

Identified: 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)

Identified: 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)

Identified: 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)

Identified: 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)

Identified: 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)

Identified: 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 [email protected]

Identified: Our engineering team still continues to work on restoring full functionality and efforts are progressing as expected.

Identified: Our engineering team still continues to work on restoring full functionality and efforts are progressing as expected.

Identified: Our engineering team still continues to work on restoring full functionality and efforts are progressing as expected.

Identified: Our engineering team continues to work on restoring full functionality and efforts are progressing as expected.

Identified: We are continuing to work on a fix for this issue.

Identified: Our engineering team continues to work on restoring full functionality and efforts are progressing as expected.

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.

Investigating: 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.

Investigating: 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.

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.

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.

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 [email protected].

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. We have resumed sending product data.

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.

Identified: 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.

Identified: 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.

Identified: 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)

Identified: 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)

Identified: 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)

Identified: 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)

Identified: 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)

Identified: 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)

Identified: 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 [email protected]

Identified: Our engineering team still continues to work on restoring full functionality and efforts are progressing as expected.

Identified: Our engineering team still continues to work on restoring full functionality and efforts are progressing as expected.

Identified: Our engineering team still continues to work on restoring full functionality and efforts are progressing as expected.

Identified: Our engineering team continues to work on restoring full functionality and efforts are progressing as expected.

Identified: We are continuing to work on a fix for this issue.

Identified: Our engineering team continues to work on restoring full functionality and efforts are progressing as expected.

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.

Investigating: 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.

Investigating: 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.

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.

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.

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 [email protected].

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. We have resumed sending product data.

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.

Identified: 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.

Identified: 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.

Identified: 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)

Identified: 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)

Identified: 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)

Identified: 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)

Identified: 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)

Identified: 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)

Identified: 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 [email protected]

Identified: Our engineering team still continues to work on restoring full functionality and efforts are progressing as expected.

Identified: Our engineering team still continues to work on restoring full functionality and efforts are progressing as expected.

Identified: Our engineering team still continues to work on restoring full functionality and efforts are progressing as expected.

Identified: Our engineering team continues to work on restoring full functionality and efforts are progressing as expected.

Identified: We are continuing to work on a fix for this issue.

Identified: Our engineering team continues to work on restoring full functionality and efforts are progressing as expected.

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.

Investigating: 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.

Investigating: 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.

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.

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.

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 [email protected].

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. We have resumed sending product data.

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.

Identified: 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.

Identified: 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.

Identified: 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)

Identified: 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)

Identified: 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)

Identified: 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)

Identified: 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)

Identified: 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)

Identified: 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 [email protected]

Identified: Our engineering team still continues to work on restoring full functionality and efforts are progressing as expected.

Identified: Our engineering team still continues to work on restoring full functionality and efforts are progressing as expected.

Identified: Our engineering team still continues to work on restoring full functionality and efforts are progressing as expected.

Identified: Our engineering team continues to work on restoring full functionality and efforts are progressing as expected.

Identified: We are continuing to work on a fix for this issue.

Identified: Our engineering team continues to work on restoring full functionality and efforts are progressing as expected.

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.

Investigating: 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.

Investigating: 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.

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.

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.

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 [email protected].

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. We have resumed sending product data.

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.

Identified: 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.

Identified: 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.

Identified: 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)

Identified: 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)

Identified: 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)

Identified: 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)

Identified: 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)

Identified: 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)

Identified: 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 [email protected]

Identified: Our engineering team still continues to work on restoring full functionality and efforts are progressing as expected.

Identified: Our engineering team still continues to work on restoring full functionality and efforts are progressing as expected.

Identified: Our engineering team still continues to work on restoring full functionality and efforts are progressing as expected.

Identified: Our engineering team continues to work on restoring full functionality and efforts are progressing as expected.

Identified: We are continuing to work on a fix for this issue.

Identified: Our engineering team continues to work on restoring full functionality and efforts are progressing as expected.

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.

Investigating: 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.

Investigating: 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.

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.

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.

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 [email protected].

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. We have resumed sending product data.

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.

Identified: 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.

Identified: 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.

Identified: 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)

Identified: 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)

Identified: 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)

Identified: 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)

Identified: 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)

Identified: 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)

Identified: 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 [email protected]

Identified: Our engineering team still continues to work on restoring full functionality and efforts are progressing as expected.

Identified: Our engineering team still continues to work on restoring full functionality and efforts are progressing as expected.

Identified: Our engineering team still continues to work on restoring full functionality and efforts are progressing as expected.

Identified: Our engineering team continues to work on restoring full functionality and efforts are progressing as expected.

Identified: We are continuing to work on a fix for this issue.

Identified: Our engineering team continues to work on restoring full functionality and efforts are progressing as expected.

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.

Investigating: 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.

Investigating: 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.

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.

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.

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 [email protected].

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. We have resumed sending product data.

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.

Identified: 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.

Identified: 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.

Identified: 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)

Identified: 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)

Identified: 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)

Identified: 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)

Identified: 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)

Identified: 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)

Identified: 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 [email protected]

Identified: Our engineering team still continues to work on restoring full functionality and efforts are progressing as expected.

Identified: Our engineering team still continues to work on restoring full functionality and efforts are progressing as expected.

Identified: Our engineering team still continues to work on restoring full functionality and efforts are progressing as expected.

Identified: Our engineering team continues to work on restoring full functionality and efforts are progressing as expected.

Identified: We are continuing to work on a fix for this issue.

Identified: Our engineering team continues to work on restoring full functionality and efforts are progressing as expected.

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.

Investigating: 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.

Investigating: 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.

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.