Rebuy Outage History

We recently made an update to our infrastructure to improve efficiency and performance. Following the release, some merchants experienced issues with Widgets and Post Purchase Offers due to CORS-related errors. Our team quickly identified the cause and implemented the necessary changes to resolve these issues. To prevent similar occurrences in the future, we’ve made improvements to our testing processes to catch the specific errors that were seen during this maintenance. We appreciate your patience and understanding as we continue to optimize our systems. If you have any questions or need assistance, our support team is here to help.

We recently made an update to our infrastructure to improve efficiency and performance. Following the release, some merchants experienced issues with Widgets and Post Purchase Offers due to CORS-related errors. Our team quickly identified the cause and implemented the necessary changes to resolve these issues. To prevent similar occurrences in the future, we’ve made improvements to our testing processes to catch the specific errors that were seen during this maintenance. We appreciate your patience and understanding as we continue to optimize our systems. If you have any questions or need assistance, our support team is here to help.

**What Happened** During a migration a configuration setting was unintentionally missed. This setting controlled rate limits for one of our key services, causing errors that disrupted functionality. ‌ **What We Did to Resolve It** After identifying the root cause, we implemented a temporary fix by adjusting the configuration to restore functionality. We also worked to port the missing configuration to V2 to prevent further disruptions. ‌ #### **Next Steps** We’ve now updated our processes to ensure all necessary configurations are accounted for in future migrations. This includes adding safeguards and testing mechanisms to catch similar issues before they impact functionality.

#### **What Happened** A high-demand process coincided with a scheduled daily job, leading to excessive resource usage in our database. This caused an overload, which resulted in an interruption of the **SmartCartV2 service**. ‌ **Initial Actions to Resolve the Outage** We adjusted the memory allocation for operations by increasing it from the default value. This change was applied dynamically without needing a full MySQL restart, minimizing disruption. ‌ #### **What We’re Doing Going Forward** 1. **Improved Resource Management:** * We’ve restructured how **SmartCartV2** data is processed to prevent resource conflicts between different tasks, such as the one that occurred in this instance. 2. **Update System Logic:** * Our applications will be updated to work seamlessly with this new data process, ensuring smooth and efficient performance with the new model.

**Post-Mortem: Service Disruption** We recently experienced an issue that temporarily impacted one of our core services, while other systems continued running normally. This occurred during a routine system update, where one service didn’t adapt to new settings as expected. We’re actively reviewing our processes and related integrations to understand the cause and ensure smoother transitions in the future.

**Cause:** We observed an unexpected increase in system activity over the past 24-48 hours, which revealed some challenges with the search system's ability to scale effectively under higher demand. **Resolution:** The search team addressed the issue by increasing system resources and rebalancing the search cluster, which restored full production health. **Prevention:** We are collaborating with our partners to conduct a comprehensive review of the incident and will continue to monitor the system to maintain stability. Additionally, there are several potential optimizations that are being evaluated for potential implementation to enhance overall system performance.