- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 21of 100
What to do
Check whether your product depends on Apollo.io. 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 4h 15m it lasted.
Anything that failed between 2026-05-12 15:10 UTC and 2026-05-12 19:25 UTC may need a replay.Subscribe to Apollo.io's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=apollo-io works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Apollo.io 3
- update
Our queue infrastructure is degraded. Data changes may take longer time to propagate, and sequences take longer time to run.
provider
- update
We have stabilized the cluster and queues are catching up. Latency is starting to stabilize.
provider
- resolved
The issue has been resolved and all products should be operating normally.
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-ad4ba167e6
Is Apollo.io still down?
No, this incident was resolved 2026-05-12 19:25 UTC. For Apollo.io's live state, see https://down.guide/apollo-io.
How long did it last?
4h 15m, from 2026-05-12 15:10 UTC to 2026-05-12 19:25 UTC, by the times Apollo.io posted.
What caused it?
Apollo.io hasn't published a root cause. If it does, it shows here.
Where does this come from?
Apollo.io's official status page, https://status.apollo.io, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.