- Level
- confirmed
- Worst impact
- Degraded
- Regions
- us, us-east-1
- Down Index
- 37of 100
What to do
Check whether you use Axiom in us, us-east-1. 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 1h 4m it lasted.
Anything that failed between 2026-10-25 17:35 UTC and 2026-10-25 18:39 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
- identified
Queries performed on metrics datasets on us-east-1 region are currently failing at an elevated rate, we have identified the root cause and working on a fix.
provider
- monitoring
A fix was deployed and we are monitoring, error rates have already started to drop.
provider
- resolved
Error rate have returned to nominal levels.
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-1b6b4733ee
Is Axiom still down?
No, this incident was resolved 2026-10-25 18:39 UTC. For Axiom's live state, see https://down.guide/axiom.
How long did it last?
1h 4m, from 2026-10-25 17:35 UTC to 2026-10-25 18:39 UTC, by the times Axiom posted.
What was affected?
Axiom named in us, us-east-1.
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.