Rebuy incident

Smart Cart, Post-Purchase Flows, and Admin Errors

Minor Resolved View vendor source →

Rebuy experienced a minor incident on March 18, 2026 affecting Admin Portal, lasting 33m. The incident has been resolved; the full update timeline is below.

Started
Mar 18, 2026, 04:43 PM UTC
Resolved
Mar 18, 2026, 05:16 PM UTC
Duration
33m
Detected by Pingoru
Mar 18, 2026, 04:43 PM UTC

Affected components

Admin Portal

Update timeline

  1. investigating Mar 18, 2026, 04:43 PM UTC

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

  2. investigating Mar 18, 2026, 05:00 PM UTC

    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.

  3. monitoring Mar 18, 2026, 05:08 PM UTC

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

  4. resolved Mar 18, 2026, 05:16 PM UTC

    This incident has been resolved.

  5. postmortem Mar 18, 2026, 08:24 PM UTC

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