Skip to main content
Orb

Processing delays

Degraded Lasted 16h 17m · started · Orb's page

Level
confirmed
Worst impact
Degraded
Components
Reads, Writes, Analytics, Real-time alerting
Down Index
34of 100

What to do

  • Check whether you use Orb Reads, Writes, Analytics, Real-time alerting. Check your stack

    Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
  • Confirm your retries, queues and scheduled jobs caught up after the 16h 17m it lasted.

    Anything that failed between 2025-10-20 07:38 UTC and 2025-10-20 23:55 UTC may need a replay.
  • Subscribe to Orb's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=orb works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Orb 19

  1. investigating

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

    provider

  2. investigating

    We are continuing to see and investigate errors.

    provider

  3. investigating

    We are continuing to investigate errors.

    provider

  4. investigating

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

    provider

  5. investigating

    We are continuing to investigate this issue.

    provider

  6. investigating

    We are continuing to investigate the issue.

    provider

  7. investigating

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

    provider

  8. investigating

    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.

    provider

  9. investigating

    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.

    provider

  10. identified

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

    provider

  11. identified

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

    provider

  12. identified

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

    provider

  13. identified

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

    provider

  14. identified

    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.

    provider

  15. identified

    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.

    provider

  16. identified

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

    provider

  17. monitoring

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

    provider

  18. monitoring

    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.

    provider

  19. resolved

    All systems are operational.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Questions about DWN-7c9f00360a

Is Orb still down?

No, this incident was resolved 2025-10-20 23:55 UTC. For Orb's live state, see https://down.guide/orb.

How long did it last?

16h 17m, from 2025-10-20 07:38 UTC to 2025-10-20 23:55 UTC, by the times Orb posted.

What was affected?

Orb named Reads, Writes, Analytics, Real-time alerting.

What caused it?

Orb hasn't published a root cause. If it does, it shows here.

Where does this come from?

Orb's official status page, https://status.withorb.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.