Axiom had 25 outages in the last 2 years totaling 105h 53m of downtime — averaging 1 incident per month.
There were 25 Axiom outages since October 20, 2025 totaling 105h 53m of downtime. Each is summarised below — incident details, duration, and resolution information.
Status: Identified Metrics query service in us region has issues, identified the issue and currently deploying the fix Affected components Querying (Partial outage)
Status: Resolved We've resolved the issue, we will improve the operational process to prevent the issue Affected components Querying (Operational)
Status: Identified Metrics ingest is experiencing issues due to an infrastructure change. We've identified the problem and are working on it. Affected components Ingest (Partial outage)
Status: Resolved We've fixed the problem and Metrics ingest is back to normal. Affected components Ingest (Operational)
Status: Resolved The query service was also affected during the incident, it failed to discover recent metric data during this time window, and this is fixed now Affected components Ingest (Operational)
Status: Investigating We've observed elevated error rates and slower responses for some queries in the US region. You may see failed or partially loaded dashboards, query errors (HTTP 500), or failed queries from the API and monitors. Ingest is not affected, and no data has been lost. Failed queries can be retried. We'll post another update within 30 minutes or as soon as we know more. Affected components Alerting (Degraded performance) Querying (Degraded performance)
Status: Monitoring We've rolled back the change behind the US query errors. Since 19:15 UTC, query error rates have been back to normal. We're monitoring and will post another update by 20:00 UTC. Affected components Alerting (Operational) Querying (Operational)
Status: Resolved 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. Affected components Alerting (Operational) Querying (Operational)
Status: Monitoring 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 Affected components Alerting (Partial outage)
Status: Resolved The backlog has been fully drained and monitor processing latency is back within normal range. Affected components Alerting (Operational)
Status: Investigating 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. Affected components App (Degraded performance)
Status: Identified 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. Affected components App (Degraded performance)
Status: Identified 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. Affected components App (Degraded performance)
Status: Monitoring 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. Affected components App (Operational)
Status: Resolved 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. Affected components App (Operational)
Status: Investigating Some queries are failing due to recent deployment, we are on it. Affected components Querying (Degraded performance) Querying (Degraded performance)
Status: Resolved A revert has happened, the query service is now operating normally. The root cause has also been identified and we are actively working on it so queries are not affected again. Affected components Querying (Operational) Querying (Operational)
Status: Investigating We are investigating reports of 403 errors when using Firehose (/v1/ingest/.../firehose) with our US edge domain. As a workaround, impacted customers can use our legacy ingest endpoint: https://api.axiom.co/v1/datasets/.../ingest/firehose. Affected components Ingest (Degraded performance)
Status: Resolved We have rolled back the changes we have made in our infrastructure to fix the firehose ingestion. Firehose ingestion should be back now. Affected components Ingest (Operational)
Status: Identified We are experiencing some infrastructure issues on our EU Edge Deployment which may effect query performance for Metrics. Affected components Querying (Degraded performance)
Status: Monitoring We have rolled out a fix and currently monitoring to ensure query performance is optimal. Affected components Querying (Degraded performance)
Status: Resolved Underlying infrastructure issues have been resolved, metrics queries on EU Edge Deployment should now be fully operational. Affected components Querying (Operational)
Status: Investigating Team have noticed increased error rates in both ingest and queries. We started investigating... Affected components API (Partial outage) Alerting (Partial outage) Querying (Partial outage) Endpoints (Partial outage) Ingest (Partial outage) App (Partial outage)
Status: Identified We have identified a problem with one of our internal databases. Mitigations are in progress. Affected components Alerting (Degraded performance) Querying (Degraded performance) Endpoints (Degraded performance) Ingest (Degraded performance) App (Degraded performance) API (Degraded performance)
Status: Monitoring We see return to nominal error levels. Affected components API (Operational) Alerting (Operational) Querying (Operational) Endpoints (Operational) Ingest (Operational) App (Operational)
Status: Resolved This incident is fully resolved. Affected components Endpoints (Operational) Ingest (Operational) App (Operational) API (Operational) Alerting (Operational) Querying (Operational)
Status: Investigating We are investigating increase in query errors Affected components Querying (Degraded performance)
Status: Identified We have identified a problem in our query cluster and are mitigating it Affected components Querying (Degraded performance)
Status: Resolved We see full recovery of the query subsystem Affected components Querying (Operational)
Status: Investigating We have noticed an increase to the Error Rate on the ingest path, we are working on it Affected components Ingest (Degraded performance)
Status: Monitoring We have identified the root cause of the issue, which was introduced in the most recent deployment, and have reverted the changes. A permanent fix is currently being developed and will be deployed to production shortly. Affected components Ingest (Operational)
Status: Resolved All systems are operating normally. The issue has been fully resolved and we are continuing to monitor to ensure stability. Affected components Ingest (Operational)
Status: Identified Dataset trimming operations in the US region are currently experiencing delays. This may cause temporary increases in dataset size and delays in enforcing data retention policies across affected datasets. The root cause has been identified, and remediation is in progress. Due to the nature of the issue and the required processing backlog, recovery is expected to take at least 24 hours before trimming operations return to normal performance levels.
Status: Resolved This incident is now resolved.
Status: Investigating We are investigating increased ingest error rate Affected components Ingest (Degraded performance)
Status: Monitoring We've identified the source of the problem and applied mitigations, we observe decrease in ingest errors. Affected components Ingest (Operational)
Status: Resolved This incident is resolved Affected components Ingest (Operational)
Status: Resolved Just before 3pm on 26th of Feb '26, an incorrect configuration was accidentally deployed to our EU environment which impacted query performance. We quickly identified the issue and released a fix. Affected components Querying (Operational) Endpoints (Operational) Ingest (Operational) App (Operational) App (Operational) Ingest (Operational) Alerting (Operational) Endpoints (Operational) API (Operational) Alerting (Operational) API (Operational) Querying (Operational)