- 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 7m it lasted.
Anything that failed between 2026-10-30 15:28 UTC and 2026-10-30 16:35 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 6
- investigating
We have noticed a partial degradation of performance on our metrics ingest nodes in US East 1.
provider
- identified
We have identified the issue and are currently rolling mitigations.
provider
- monitoring
Our fixes have addressed this issue, we will continue to monitor the situation to ensure stability returns to the system.
provider
- resolved
Metrics Query Performance since 3pm UTC should be fully restored.
provider
- investigating
Further performance issues have been identified
provider
- resolved
All ingest issues have been addressed
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-2b117761dc
Is Axiom still down?
No, this incident was resolved 2026-10-30 16:35 UTC. For Axiom's live state, see https://down.guide/axiom.
How long did it last?
1h 7m, from 2026-10-30 15:28 UTC to 2026-10-30 16:35 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.