Recharge incident

Required Maintenance: January 25

Critical Resolved View vendor source →

Recharge experienced a critical incident on January 26, 2025 affecting Recharge Analytics and Recharge API and 1 more component, lasting 8d 6h. The incident has been resolved; the full update timeline is below.

Started
Jan 26, 2025, 07:13 AM UTC
Resolved
Feb 03, 2025, 02:08 PM UTC
Duration
8d 6h
Detected by Pingoru
Jan 26, 2025, 07:13 AM UTC

Affected components

Recharge AnalyticsRecharge APIRecharge Charge ProcessingRecharge CheckoutRecharge Customer PortalRecharge Merchant PortalRecharge Webhooks

Update timeline

  1. investigating Jan 26, 2025, 07:13 AM UTC

    Maintenance is ongoing.

  2. monitoring Jan 26, 2025, 10:23 AM UTC

    Our Engineers have completed the upgrade work and are monitoring.

  3. investigating Jan 26, 2025, 11:12 AM UTC

    We are currently investigating this issue.

  4. investigating Jan 26, 2025, 01:49 PM UTC

    We are receiving reports of some users experiencing degraded performance and a delay in order processing. We are currently investigating this issue.

  5. investigating Jan 26, 2025, 06:13 PM UTC

    We are receiving reports of some users experiencing degraded performance and a delay in order processing. We are continuing to work to resolve this issue.

  6. monitoring Jan 26, 2025, 08:59 PM UTC

    We are seeing recovery across all systems and continue to monitor as any backlogs process.

  7. monitoring Jan 26, 2025, 11:24 PM UTC

    We continue to see recovery across all systems and continue to monitor as any backlogs process.

  8. monitoring Jan 27, 2025, 01:47 PM UTC

    We continue to see recovery across all systems, some stores may see a delay in the data from 1/26/25 populating in the Analytics dashboards.

  9. monitoring Jan 29, 2025, 04:37 PM UTC

    We are still seeing recovery, and analytics backfilling remains in progress. Analytics from January 26, 2025 onward, may be unavailable at this time. Our team is actively working to resolve fully.

  10. resolved Feb 03, 2025, 02:08 PM UTC

    This incident has been resolved.