- Level
- confirmed
- Worst impact
- Partial outage
- Down Index
- 42of 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 4h 10m it lasted.
Anything that failed between 2026-05-15 17:17 UTC and 2026-05-15 21:27 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 4
- investigating
Team have noticed increased error rates in both ingest and queries. We started investigating...
provider
- identified
We have identified a problem with one of our internal databases. Mitigations are in progress.
provider
- monitoring
We see return to nominal error levels.
provider
- resolved
This incident is fully resolved.
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-bfea3e8625
Is Axiom still down?
No, this incident was resolved 2026-05-15 21:27 UTC. For Axiom's live state, see https://down.guide/axiom.
How long did it last?
4h 10m, from 2026-05-15 17:17 UTC to 2026-05-15 21:27 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.