- Level
- confirmed
- Worst impact
- Major outage
- Regions
- eu
- Down Index
- 45of 100
What to do
Check whether you use Axiom in eu. 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 0m it lasted.
Anything that failed between 2026-02-26 16:13 UTC and 2026-02-26 15:55 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
- investigating
We are investigating reports of widespread query failures on the legacy EU instance. Users experiencing internal server errors when executing queries.
provider
- identified
We've identified the root cause as a network configuration change that disrupted internal service-to-service communication. This caused query requests to fail, resulting in HTTP 500 errors.
provider
- resolved
All services have returned to normal operation. Queries are executing successfully, and internal traffic between services has been fully restored. We are continuing to monitor the system to ensure stability.
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-8df00d3862
Is Axiom still down?
No, this incident was resolved 2026-02-26 15:55 UTC. For Axiom's live state, see https://down.guide/axiom.
How long did it last?
0m, from 2026-02-26 16:13 UTC to 2026-02-26 15:55 UTC, by the times Axiom posted.
What was affected?
Axiom named in eu.
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.