Ordergroove incident

We are experiencing a performance degradation in the API response times

Major Resolved View vendor source →

Ordergroove experienced a major incident on January 21, 2026 affecting Subscription Creation and APIs and 1 more component, lasting 1h 56m. The incident has been resolved; the full update timeline is below.

Started
Jan 21, 2026, 06:22 PM UTC
Resolved
Jan 21, 2026, 08:18 PM UTC
Duration
1h 56m
Detected by Pingoru
Jan 21, 2026, 06:22 PM UTC

Affected components

Subscription CreationAPIsAdmin Dashboard (previously RC3)

Update timeline

  1. investigating Jan 21, 2026, 06:22 PM UTC

    We are currently investigating response latency and will have an update in about 30 minutes.

  2. monitoring Jan 21, 2026, 06:32 PM UTC

    We have identified and mitigated the effects of the latency. We are monitoring the performance of the system.

  3. investigating Jan 21, 2026, 07:05 PM UTC

    There is an ongoing spike in failed API responses. We are investigating again.

  4. monitoring Jan 21, 2026, 07:45 PM UTC

    We have identified a secondary cause of latency and addressed the issue. We are monitoring the system and will post an update shortly.

  5. resolved Jan 21, 2026, 08:18 PM UTC

    The issue is resolved, and all services are operating normally. We apologize for the inconvenience and will publish a post-mortem within 24 hours which will be available via our CS team.