outages.live
Live
AxiomIncident · 2026-10-07 17:28 UTC

EU Monitor alerting degraded

ResolvedOfficial update

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

The latest update from Axiom.

State

Resolved

Started

25 d ago

2026-10-07 17:28 UTC

Lasted

1 h 7 min

until 2026-10-07 18:36 UTC

Worst impact

Partial outage

Timeline

2 updates
17:2817:4518:0218:1918:36
Partial outageUpdate postedTimes in UTC

Monitoring

1 h 7 min 100%

Updates

Times in UTC

As posted by Axiom

Resolved2026-10-07 18:36 UTC

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

Monitoring2026-10-07 17:28 UTC

A backlog in monitor executions in the EU region is causing delays in monitor evaluation. A fix has been deployed for the issue, and the backlog is decreasing in size. We are monitoring the backlog progress and will update once it has cleared

Axiom in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

7

Days with an incident

9

Median duration

1 h 7 min

This incident

About the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

2 days
median 1 h 7 min
90 days agoToday

Other Axiom incidents

All incidents

Axiom·Metrics Ingest on US-east-1

All ingest issues have been addressed

Resolvedresolved 2 d ago

Axiom·Elevated errors from queries

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

Resolvedresolved 5 d ago

Axiom·Queries on Metrics Datasets Suffer from Elevated Error Rates

Error rate have returned to nominal levels.

Resolvedresolved 7 d ago

Axiom·Metrics query failures in US region

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

Resolvedresolved 17 d ago

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.

Resolvedresolved 17 d ago

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.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.

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

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane