Rebuy experienced a critical incident on May 18, 2026 affecting API and Smart Cart and 1 more component, lasting 19m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating May 18, 2026, 07:10 PM UTC
Rebuy is currently experiencing issues affecting admin and on-site functionality. Our team is aware and actively working on a resolution.
- identified May 18, 2026, 07:16 PM UTC
The issue has been identified and a fix is being implemented.
- monitoring May 18, 2026, 07:20 PM UTC
A fix has been implemented and we are seeing on-site and admin functionality return to normal. The team continues to monitor.
- resolved May 18, 2026, 07:29 PM UTC
The issue has been resolved. We will be investigating the root cause and sharing a post-mortem once our review is complete.
- postmortem May 20, 2026, 03:05 PM UTC
**Incident Report: Admin and On-Site Functionality Disruption** **Date:** May 18, 2026 **Duration:** 3:10 PM – 3:29 PM ET \(~19 minutes\) **Summary** On May 18, 2026, merchants experienced a disruption affecting the Rebuy Admin Portal and on-site functionality including Smart Cart, Checkout Extensions, Post-Purchase Offers, A/B Testing, Smart Search, Smart Collections, and Rebuy Monetize. The issue was identified and resolved within 19 minutes. **Root Cause** The disruption was caused by a sequencing issue during a coordinated internal release. A database update that was required before new application code could safely serve traffic did not complete as expected. When the application code deployed and began serving requests, it encountered errors that cascaded across multiple product surfaces. **Resolution** We rolled back the affected services to the previous stable version within approximately 10 minutes of identifying the issue, which restored functionality for all merchants. The underlying database update was then completed successfully, and the full release was redeployed and verified shortly after. **What We're Doing** We are implementing additional verification gates in our multi-service release process to ensure that dependent infrastructure changes are confirmed live in production before downstream application code is allowed to deploy.