- Level
- confirmed
- Worst impact
- Degraded
- Components
- Webhooks
- Down Index
- 20of 100
What to do
Check whether you use Orb Webhooks. 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 52m it lasted.
Anything that failed between 2025-01-05 19:09 UTC and 2025-01-05 20:01 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 2
- monitoring
We have detected and are working to resolve delays for some customers for the following webhooks: - subscription.usage_exceeded - subscription.cost_exceeded - customer.credit_balance_depleted - customer.credit_balance_dropped - customer.credit_balance_recovered The underlying issue has been resolved and our systems are working to return our webhook latency back to normal. We expect a full recover within the next few hours.
provider
- resolved
Webhooks latencies have returned to normal levels for all webhooks.
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-26ed46276b
Is Orb still down?
No, this incident was resolved 2025-01-05 20:01 UTC. For Orb's live state, see https://down.guide/orb.
How long did it last?
52m, from 2025-01-05 19:09 UTC to 2025-01-05 20:01 UTC, by the times Orb posted.
What was affected?
Orb named Webhooks.
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.