- Level
- confirmed
- Worst impact
- Degraded
- Regions
- us
- Down Index
- 35of 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 3h 9m it lasted.
Anything that failed between 2026-06-30 18:30 UTC and 2026-06-30 21: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 2
- investigating
We are investigating reports of 403 errors when using Firehose (`/v1/ingest/.../firehose`) with our US edge domain. As a workaround, impacted customers can use our legacy ingest endpoint: `https://api.axiom.co/v1/datasets/.../ingest/firehose`.
provider
- resolved
We have rolled back the changes we have made in our infrastructure to fix the firehose ingestion. Firehose ingestion should be back now.
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-19d43b23a0
Is Axiom still down?
No, this incident was resolved 2026-06-30 21:39 UTC. For Axiom's live state, see https://down.guide/axiom.
How long did it last?
3h 9m, from 2026-06-30 18:30 UTC to 2026-06-30 21:39 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.