outages.live
Live

Axiom

Axiom is operational

Checked 3 min ago Operational

History

90 days agoToday

Incidents in 90 days

7

Days with an incident

9

Median duration

1 h 7 min

Longest incident

2 days

Components

12
API Operational
90 days agoNo incidentsToday
Ingest Operational
90 days agoNo incidentsToday
Querying Operational
90 days agoNo incidentsToday
Alerting Operational
90 days agoNo incidentsToday
Endpoints Operational
90 days agoNo incidentsToday
App Operational
90 days agoNo incidentsToday
API Operational
90 days agoNo incidentsToday
Ingest Operational
90 days agoNo incidentsToday
Querying Operational
90 days agoNo incidentsToday
Alerting Operational
90 days agoNo incidentsToday
Endpoints Operational
90 days agoNo incidentsToday
App Operational
90 days agoNo incidentsToday

Past incidents

Provider status pageTimes in UTC

Oct 30, 2026

Duration1 h 7 min15:28 to 16:35Metrics Ingest on US-east-1Degraded

All ingest issues have been addressed

Oct 27, 2026

Duration2 h 4 min15:58 to 18:02Elevated errors from queriesPartial outage

Monitors are now processing in real time, no visible delays.

Oct 25, 2026

Duration1 h 4 min17:35 to 18:39Queries on Metrics Datasets Suffer from Elevated Error RatesDegraded

Error rate have returned to nominal levels.

Oct 15, 2026

Duration54 min12:21 to 13:15Metrics query failures in US regionPartial outage

We've resolved the issue, we will improve the operational process to prevent the issue

Oct 14, 2026

Duration51 min19:12 to 20:03Elevated query errors in US regionDegraded

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.

Oct 7, 2026

Duration1 h 7 min17:28 to 18:36EU Monitor alerting degradedPartial outage

The backlog has been fully drained and monitor processing latency is back within normal range.

Aug 10, 2026

Duration2 days17:08 to 20:08Console UI Authentication DegradedDegraded

Access to the Axiom Console through Github is available as well as all other authentication methods. Users might experience a one-time email verification step for their Primary Github email. The Primary email address should be configured as the email used with an Axiom account. Additional verified emails can be used to access separate Axiom accounts.

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.

Prompt
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.live/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.

RSS
https://outages.live/feed.xml?providers=axiom
Slack
/feed subscribe https://outages.live/feed.xml?providers=axiom

Go from tracking outages to fixing production issues with Polylane.

Try Polylane