- Level
- confirmed
- Worst impact
- Partial outage
- Down Index
- 35of 100
What to do
Check whether your product depends on Axiom. 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 13m it lasted.
Anything that failed between 2026-11-04 12:14 UTC and 2026-11-04 12:27 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.
Root cause
Our team is working to identify the cause.Read the postmortem
Updates from Axiom 4
- investigating
We are investigating reports that customers cannot log in to Axiom. Customers signing in may encounter an error when starting or completing sign-in. Our team is working to identify the cause. We will share an update as soon as we have more information.
provider
- identified
The cause of the issue has been identified.
provider
- monitoring
A fix has been rolled out, we will continue to monitor the situation to ensure the issue has been resolved.
provider
- resolved
All Login capabilities should be restored.
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-29e6ecbb81
Is Axiom still down?
No, this incident was resolved 2026-11-04 12:27 UTC. For Axiom's live state, see https://down.guide/axiom.
How long did it last?
13m, from 2026-11-04 12:14 UTC to 2026-11-04 12:27 UTC, by the times Axiom posted.
What caused it?
Axiom wrote: "Our team is working to identify the cause." The postmortem: https://status.axiom.co/incidents/01M6K7Q2P1SVP9CG4FF86G8A2A
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.