Live

Console UI Authentication Degraded

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.

The latest update from Axiom.

State

Resolved

Started

83 d ago

2026-08-10 17:08 UTC

Lasted

2 days

until 2026-08-12 20:08 UTC

Worst impact

Degraded

Timeline

5 updates
Aug 10Aug 11Aug 11Aug 12Aug 12
DegradedUpdate postedDates in UTC

Investigating

13 h 27 min 26%

Identified

10 h 38 min 21%

Monitoring

26 h 55 min 53%

Updates

Times in UTC

As posted by Axiom

Resolved2026-08-12 20:08 UTC

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.

Monitoring2026-08-11 17:13 UTC

Access to the Axiom Console through Github is available as well as all other authentication methods. We are monitoring for any further disruption. 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.

Identified2026-08-11 12:13 UTC

Access to the Axiom Console is only available through Email, Google, and SAML/SSO authentication at present. Authentication with Github is unavailable. There is no impact on Axiom data or other services.

Identified2026-08-11 06:35 UTC

Access to Axiom Console through Github is unavailable. Other authentication methods are not affected. Resolution is expected soon. All Axiom data and other services are unaffected.

Investigating2026-08-10 17:08 UTC

Access to the Axiom Console is only available through Email, Google, and SAML/SSO authentication at present. Authentication with Github is unavailable. There is no impact on Axiom data or other services.

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

46× 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

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