Queries on Metrics Datasets Suffer from Elevated Error Rates
Error rate have returned to nominal levels.
The latest update from Axiom.
State
Resolved
Started
7 d ago
2026-10-25 17:35 UTC
Lasted
1 h 4 min
until 2026-10-25 18:39 UTC
Worst impact
Degraded
Timeline
3 updatesIdentified
55 min 86%
Monitoring
9 min 14%
Updates
Times in UTCAs posted by Axiom
Error rate have returned to nominal levels.
A fix was deployed and we are monitoring, error rates have already started to drop.
Queries performed on metrics datasets on us-east-1 region are currently failing at an elevated rate, we have identified the root cause and working on a fix.
Axiom in the last 90 days
Full historyIncidents in 90 days
7
Days with an incident
9
Median duration
1 h 7 min
This incident
About the median
Other Axiom incidents
All incidentsAxiom·Metrics Ingest on US-east-1
All ingest issues have been addressed
Axiom·Elevated errors from queries
Monitors are now processing in real time, no visible delays.
Axiom·Metrics query failures in US region
We've resolved the issue, we will improve the operational process to prevent the issue
Axiom·Elevated query errors in US region
Query performance in the US region has been fully restored since 19:15 UTC. Between 18:05 and 19:15 UTC, some queries and dashboards returned errors and some monitor runs were missed or delayed. Ingest was not affected and no data was lost. We'll share a follow-up describing what we're changing to prevent this.
Axiom·EU Monitor alerting degraded
The backlog has been fully drained and monitor processing latency is back within normal range.
Follow Axiom
Your coding agent knows when Axiom is down, and tells you when a failure is theirs, not yours. You can also get Axiom incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "axiom" and tell me if Axiom has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.cc/feed.xml?providers=axiom/feed subscribe https://outages.cc/feed.xml?providers=axiomFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane