Orb incident

Processing delays

Minor Resolved View vendor source →

Orb experienced a minor incident on October 20, 2025 affecting Reads and Writes and 1 more component, lasting 16h 17m. The incident has been resolved; the full update timeline is below.

Started
Oct 20, 2025, 07:38 AM UTC
Resolved
Oct 20, 2025, 11:55 PM UTC
Duration
16h 17m
Detected by Pingoru
Oct 20, 2025, 07:38 AM UTC

Affected components

ReadsWritesAnalyticsReal-time alerting

Update timeline

  1. investigating Oct 20, 2025, 07:28 AM UTC

    We are currently investigating API degradation. This seems to be related to an upstream cloud provider outage, and we are closely monitoring.

  2. investigating Oct 20, 2025, 07:38 AM UTC

    We are continuing to see and investigate errors.

  3. investigating Oct 20, 2025, 08:02 AM UTC

    We are continuing to investigate errors.

  4. investigating Oct 20, 2025, 08:17 AM UTC

    We are continuing to investigate this issue. We apologize for the disruption to impacted customers.

  5. investigating Oct 20, 2025, 08:47 AM UTC

    We are continuing to investigate this issue.

  6. investigating Oct 20, 2025, 09:14 AM UTC

    We are continuing to investigate the issue.

  7. investigating Oct 20, 2025, 09:53 AM UTC

    API services are broadly recovered; we're continuing to monitor the situation.

  8. investigating Oct 20, 2025, 10:19 AM UTC

    We are seeing recovery on most API endpoints - some analytics endpoints may still be degraded. We are continuing to work with upstream providers to resolve. Note also that consumption from payment processing may be delayed; we are working through the event backlog here.

  9. investigating Oct 20, 2025, 10:50 AM UTC

    We are failing over affected services gradually for our analytics APIs, which we expect to lead to errors in order to assist with full recovery.

  10. identified Oct 20, 2025, 11:17 AM UTC

    We're continuing to investigate, and working through usage calculation delays.

  11. identified Oct 20, 2025, 11:24 AM UTC

    We are working with our cloud provider to bring on more capacity to help with operational delays.

  12. identified Oct 20, 2025, 11:51 AM UTC

    We are continuing to investigate this issue. We are working with our cloud provider to bring on more capacity to help with operational delays.

  13. identified Oct 20, 2025, 12:43 PM UTC

    We are continuing to work with our cloud provider to bring on more capacity to help with operational delays.

  14. identified Oct 20, 2025, 02:00 PM UTC

    We are continuing to work with our cloud provider to bring on more capacity to help with operational delays. Asynchronous processing may be delayed, including the sending of webhooks.

  15. identified Oct 20, 2025, 02:51 PM UTC

    We are continuing to work with our cloud provider to bring on more capacity to help with operational delays. API calls may not reflect the latest usage data as we work through this. Asynchronous processing may be delayed, including the sending of webhooks and the receipt of information from your payment gateway connection. We are working diligently on our side to bring these up to date.

  16. identified Oct 20, 2025, 03:51 PM UTC

    We are continuing to work on a fix for this issue.

  17. monitoring Oct 20, 2025, 06:39 PM UTC

    We are seeing significant recovery as capacity is coming back online.

  18. monitoring Oct 20, 2025, 09:03 PM UTC

    Most async processing is operational, including webhooks and receipt of information from your payment gateway connection. We are continuing to monitor remaining recovery of usage calculations and alerting pipelines.

  19. resolved Oct 20, 2025, 11:55 PM UTC

    All systems are operational.