Is Rebuy down?

Rebuy is currently experiencing issues affecting admin and on-site functionality. Our team is aware and actively working on a resolution.

The issue has been identified and a fix is being implemented.

A fix has been implemented and we are seeing on-site and admin functionality return to normal. The team continues to monitor.

The issue has been resolved. We will be investigating the root cause and sharing a post-mortem once our review is complete.

**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.

A release to the Rebuy storefront SDK on 2026-05-11 introduced a regression for merchants who have the Rebuy app installed but do not have Smart Cart V2 active: clicks on their native Shopify cart icon stopped opening their theme's cart drawer.

On May 11, 2026, a Rebuy Storefront SDK update introduced an issue that prevented the native Shopify cart icon from opening the cart drawer on storefronts where Smart Cart V2 was not active. The issue was present from 9:36 AM EDT and identified at 12:32 PM EDT. A fix was deployed by 12:50 PM EDT and full functionality was confirmed restored shortly after. Total time from identification to resolution was approximately 18 minutes. We apologize for any disruption this caused to your shoppers and are taking steps to prevent recurrence.

We have received multiple reports of Smart Cart loading inconsistently on some merchant storefronts.We have received multiple reports of Smart Cart loading inconsistently on some merchant storefronts. Our team is actively investigating and will provide updates as we learn more.

Our team continues to investigate. Current findings suggest the impact may vary by region.

A change has been deployed and merchants who reported issues are seeing improved results. We are continuing to investigate the root cause and will share more details as they become available.

This issue has been resolved. Our team is completing a full root cause analysis, which will be posted to the status page once available. Thank you for your patience.

**What happened:** On April 22, 2026, between approximately 11:45 AM and 1:02 PM ET, a subset of shoppers on Rebuy-powered storefronts experienced an inability to load SmartCart V2. Merchants and shoppers who encountered the issue during this window would have seen the cart fail to initialize. All other Rebuy functionality remained operational throughout the incident. ‌ **Duration:** Approximately 1 hour and 17 minutes. ‌ **Impact:** A subset of shoppers on affected storefronts were unable to load SmartCart V2 during the incident window. No data was lost or compromised. ‌ **What caused it:** A software release introduced changes that shifted internal script references in a way that caused the cart to fail for shoppers loading a fresh version of the storefront script during the deployment window. Shoppers with a cached version of the script were unaffected. ‌ **What we did:** Our team identified the issue within minutes of the first report, rolled back to the previous stable release, and confirmed full restoration of SmartCart V2 by 1:02 PM ET — approximately 16 minutes from first report to resolution. ‌ **What we are doing to prevent recurrence:** We have identified the root cause and are implementing structural improvements to our deployment pipeline, including additional validation steps to catch this class of issue before it reaches production.

We are currently investigating not being able to access Rebuy Admin.

This is only affecting admin accessibility and all on-site functionality is normal. We continue to investigate what is causing the errors with the admin platform.

The issue has been identified, and a fix has been implemented.

This incident has been resolved.

**What happened** On March 18, 2026, between approximately 12:25 PM and 1:05 PM ET, merchants experienced an inability to access the Rebuy Admin dashboard. Post-purchase flows, Smart Cart, and Rebuy Monetize offers were also unavailable during this window. All on-site storefront functionality remained fully operational throughout the incident. **Duration** Approximately 30-40 minutes. **Impact** Merchants were unable to access the Rebuy Admin interface or manage active offer flows during the incident window. No data was lost or compromised. **What caused it** A routine infrastructure update introduced an unexpected configuration conflict that prevented our admin service from accepting traffic. Once identified, our team rolled back the update to restore full functionality. **What we did** Our team identified the issue, implemented a rollback, and confirmed full resolution within the same hour. We posted updates to our status page throughout the incident. **What we are doing to prevent recurrence** We have identified the root cause and are implementing additional validation steps in our deployment process to catch this class of issue before it reaches production.