outages.live
Live
AxiomMaintenance ·

MetricsDB Maintenace

MaintenanceOfficial update

MetricsDB maintenance is underway and may cause **brief interruptions** to the ingestion path

The latest update from Axiom.

State

Scheduled

Started

Ongoing for

5 h 26 min

Worst impact

Maintenance

Timeline

1 update
12:2313:4415:0616:2717:49
MaintenanceUpdate postedTimes in UTC

Scheduled

5 h 26 min 100%

Updates

Times in UTC

As posted by Axiom

Scheduled

MetricsDB maintenance is underway and may cause **brief interruptions** to the ingestion path

Axiom in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

7

Days with an incident

7

Median duration

1 h 4 min

This incident

Not comparable

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

2 h 4 min
median 1 h 4 min
90 days agoToday

Other Axiom incidents

All incidents

Axiom·Login issues

Axiom customers could not log in to Axiom. Sign-in failed when customers started or completed sign-in. Axiom reports that the issue is resolved and login capabilities are restored. The outage lasted about 13 minutes.

Resolved

Axiom·Metrics Ingest on US-east-1

All ingest issues have been addressed

Resolved

Axiom·Elevated errors from queries

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

Resolved

Axiom·Queries on Metrics Datasets Suffer from Elevated Error Rates

Error rate have returned to nominal levels.

Resolved

Axiom·Metrics query failures in US region

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

Resolved

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

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane