- Level
- confirmed
- Worst impact
- Degraded
- Regions
- us
- Down Index
- 38of 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 14h 11m it lasted.
Anything that failed between 2026-04-17 15:00 UTC and 2026-04-18 05:12 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 2
- identified
Dataset trimming operations in the US region are currently experiencing delays. This may cause temporary increases in dataset size and delays in enforcing data retention policies across affected datasets. The root cause has been identified, and remediation is in progress. Due to the nature of the issue and the required processing backlog, recovery is expected to take at least 24 hours before trimming operations return to normal performance levels.
provider
- resolved
This incident is now 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-80790f3973
Is Axiom still down?
No, this incident was resolved 2026-04-18 05:12 UTC. For Axiom's live state, see https://down.guide/axiom.
How long did it last?
14h 11m, from 2026-04-17 15:00 UTC to 2026-04-18 05:12 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.