- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 27of 100
What to do
Check whether your product depends on Axiom. 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 34m it lasted.
Anything that failed between 2026-05-08 00:16 UTC and 2026-05-08 00:50 UTC may need a replay.Subscribe to Axiom's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=axiom works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Axiom 3
- investigating
We are investigating increase in query errors
provider
- identified
We have identified a problem in our cluster related to an ongoing incident at our infrastructure provider and are mitigating it.
provider
- resolved
We see full recovery of the query subsystem. For a small number of metrics datasets, there might be data missing between 00:15 and 01:24 UTC. We're working on recovery with our infrastructure provider.
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-0ff2ec77cc
Is Axiom still down?
No, this incident was resolved 2026-05-08 00:50 UTC. For Axiom's live state, see https://down.guide/axiom.
How long did it last?
34m, from 2026-05-08 00:16 UTC to 2026-05-08 00:50 UTC, by the times Axiom posted.
What caused it?
Axiom hasn't published a root cause. If it does, it shows here.
Where does this come from?
Axiom's official status page, https://status.axiom.co, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.