Skip to content

Incident detail

Admin and On-Site Functionality Degraded

Resolved incidentCritical

Timeline window

to

Outage alerts

Get alerted the next time Rebuy breaks

Free email alerts for up to 5 providers. No card, live in about a minute. Paid plans add Slack, Teams, Discord, and webhook delivery across your whole stack, plus higher API quotas.

Timeline

Incident updates

Every update Rebuy posted, oldest to newest, exactly as it appeared on their official status page.

  1. Investigating

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

  2. Identified

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

  3. Monitoring

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

  4. Resolved

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

  5. Resolved

    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.

Keep exploring

More from Rebuy

Neighboring incidents on Rebuy's timeline and the rest of their record on OutageDeck.