- Level
- confirmed
- Worst impact
- Degraded
- Components
- Ingest
- Down Index
- 18of 100
What to do
Check whether you use Orb Ingest. 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 22m it lasted.
Anything that failed between 2025-09-16 17:42 UTC and 2025-09-16 18:05 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 4
- investigating
We're looking into elevated API times on a subset of ingestion API requests. This does not affect any ingestion via S3.
provider
- identified
We've identified the issue, and API latency is recovering - we're continuing to monitor.
provider
- monitoring
Continuing to see quick recovery on API latencies. We'll provide any further updates in 10 minutes, or close out this incident.
provider
- resolved
API latencies have returned to normal, and services are fully recovered.
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-766f0bed7e
Is Orb still down?
No, this incident was resolved 2025-09-16 18:05 UTC. For Orb's live state, see https://down.guide/orb.
How long did it last?
22m, from 2025-09-16 17:42 UTC to 2025-09-16 18:05 UTC, by the times Orb posted.
What was affected?
Orb named Ingest.
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.