- Level
- confirmed
- Worst impact
- Partial outage
- Regions
- us
- Down Index
- 44of 100
What to do
Check whether you use Axiom in us. 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 2h 4m it lasted.
Anything that failed between 2026-10-27 15:58 UTC and 2026-10-27 18:02 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 5
- investigating
We're investigating elevated error rates from querying in our US region.
provider
- identified
We have identified the problem and are deploying a fix.
provider
- identified
While the query error rate has been nominal for a while, we're seeing second-order effects that manifest as delays with monitors.
provider
- monitoring
All queues have cleared, we continue monitoring to ensure system stability.
provider
- resolved
Monitors are now processing in real time, no visible delays.
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-d3c4fa6359
Is Axiom still down?
No, this incident was resolved 2026-10-27 18:02 UTC. For Axiom's live state, see https://down.guide/axiom.
How long did it last?
2h 4m, from 2026-10-27 15:58 UTC to 2026-10-27 18:02 UTC, by the times Axiom posted.
What was affected?
Axiom named in us.
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.