- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 28of 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 42m it lasted.
Anything that failed between 2026-04-28 14:27 UTC and 2026-04-28 15:09 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 have noticed an increase to the Error Rate on the ingest path, we are working on it
provider
- monitoring
We have identified the root cause of the issue, which was introduced in the most recent deployment, and have reverted the changes. A permanent fix is currently being developed and will be deployed to production shortly.
provider
- resolved
All systems are operating normally. The issue has been fully resolved and we are continuing to monitor to ensure stability.
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-f95dff1189
Is Axiom still down?
No, this incident was resolved 2026-04-28 15:09 UTC. For Axiom's live state, see https://down.guide/axiom.
How long did it last?
42m, from 2026-04-28 14:27 UTC to 2026-04-28 15:09 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.