Axiom Outage History

Axiom is up right now

Axiom had 22 outages in the last 2 years totaling 26h 41m of downtime — averaging 0.9 incidents per month.

There were 22 Axiom outages since July 11, 2025 totaling 26h 41m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.axiom.co/#

Minor June 30, 2026

Ingest through Firehose impacted

Detected by Pingoru
Jun 30, 2026, 09:39 PM UTC
Resolved
Jun 30, 2026, 09:39 PM UTC
Duration
—
Affected: Ingest
Timeline · 2 updates
  1. investigating Jun 30, 2026, 06:30 PM UTC

    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)

  2. resolved Jun 30, 2026, 09:39 PM UTC

    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)

Read the full incident report →

Minor June 19, 2026

EU Edge Deployment Metrics Query Performance Degradation.

Detected by Pingoru
Jun 19, 2026, 02:45 PM UTC
Resolved
Jun 19, 2026, 02:45 PM UTC
Duration
—
Affected: Querying
Timeline · 3 updates
  1. identified Jun 19, 2026, 10:24 AM UTC

    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)

  2. monitoring Jun 19, 2026, 11:50 AM UTC

    Status: Monitoring We have rolled out a fix and currently monitoring to ensure query performance is optimal. Affected components Querying (Degraded performance)

  3. resolved Jun 19, 2026, 02:45 PM UTC

    Status: Resolved Underlying infrastructure issues have been resolved, metrics queries on EU Edge Deployment should now be fully operational. Affected components Querying (Operational)

Read the full incident report →

Minor May 15, 2026

Increased Ingest and Query Error Rates

Detected by Pingoru
May 15, 2026, 09:27 PM UTC
Resolved
May 15, 2026, 09:27 PM UTC
Duration
—
Affected: APIAPIIngestQueryingEndpointsAppIngestAlerting
Timeline · 4 updates
  1. investigating May 15, 2026, 05:17 PM UTC

    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)

  2. identified May 15, 2026, 05:21 PM UTC

    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)

  3. monitoring May 15, 2026, 05:24 PM UTC

    Status: Monitoring We see return to nominal error levels. Affected components API (Operational) Alerting (Operational) Querying (Operational) Endpoints (Operational) Ingest (Operational) App (Operational)

  4. resolved May 15, 2026, 09:27 PM UTC

    Status: Resolved This incident is fully resolved. Affected components Endpoints (Operational) Ingest (Operational) App (Operational) API (Operational) Alerting (Operational) Querying (Operational)

Read the full incident report →

Minor May 8, 2026

Increase in query error rate

Detected by Pingoru
May 08, 2026, 12:50 AM UTC
Resolved
May 08, 2026, 12:50 AM UTC
Duration
—
Affected: QueryingQuerying
Timeline · 3 updates
  1. investigating May 08, 2026, 12:16 AM UTC

    Status: Investigating We are investigating increase in query errors Affected components Querying (Degraded performance)

  2. identified May 08, 2026, 12:33 AM UTC

    Status: Identified We have identified a problem in our query cluster and are mitigating it Affected components Querying (Degraded performance)

  3. resolved May 08, 2026, 12:42 AM UTC

    Status: Resolved We see full recovery of the query subsystem Affected components Querying (Operational)

Read the full incident report →

Minor April 28, 2026

Ingest Error Rate Spike

Detected by Pingoru
Apr 28, 2026, 03:09 PM UTC
Resolved
Apr 28, 2026, 03:09 PM UTC
Duration
—
Affected: IngestIngest
Timeline · 3 updates
  1. investigating Apr 28, 2026, 01:50 PM UTC

    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)

  2. monitoring Apr 28, 2026, 02:21 PM UTC

    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)

  3. resolved Apr 28, 2026, 03:09 PM UTC

    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)

Read the full incident report →

Minor April 18, 2026

Dataset trims are experiencing delays

Detected by Pingoru
Apr 18, 2026, 05:12 AM UTC
Resolved
Apr 18, 2026, 05:12 AM UTC
Duration
—
Timeline · 2 updates
  1. identified Apr 17, 2026, 03:00 PM UTC

    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.

  2. resolved Apr 18, 2026, 05:12 AM UTC

    Status: Resolved This incident is now resolved.

Read the full incident report →

Minor April 12, 2026

Degraded Query performance on EU Edge Deployment

Detected by Pingoru
Apr 12, 2026, 03:13 PM UTC
Resolved
Apr 12, 2026, 03:13 PM UTC
Duration
—
Affected: QueryingQuerying
Timeline · 4 updates
  1. investigating Apr 12, 2026, 11:05 AM UTC

    Status: Investigating We are experiencing a partial query outage on our EU Edge Deployment.

  2. identified Apr 12, 2026, 12:44 PM UTC

    Status: Identified We've identified the cause of the disruption, we're evaluating possible mitigations. Affected components Querying (Partial outage)

  3. monitoring Apr 12, 2026, 02:29 PM UTC

    Status: Monitoring We've applied mitigations and are observing full recovery of the query service. Affected components Querying (Operational)

  4. resolved Apr 12, 2026, 03:13 PM UTC

    Status: Resolved This incident is resolved Affected components Querying (Operational)

Read the full incident report →

Minor March 6, 2026

Increased ingest error rate

Detected by Pingoru
Mar 06, 2026, 02:02 AM UTC
Resolved
Mar 06, 2026, 02:02 AM UTC
Duration
—
Affected: IngestIngest
Timeline · 3 updates
  1. investigating Mar 06, 2026, 01:29 AM UTC

    Status: Investigating We are investigating increased ingest error rate Affected components Ingest (Degraded performance)

  2. monitoring Mar 06, 2026, 01:46 AM UTC

    Status: Monitoring We've identified the source of the problem and applied mitigations, we observe decrease in ingest errors. Affected components Ingest (Operational)

  3. resolved Mar 06, 2026, 02:02 AM UTC

    Status: Resolved This incident is resolved Affected components Ingest (Operational)

Read the full incident report →

Minor January 27, 2026

Queries partial outage

Detected by Pingoru
Jan 27, 2026, 07:40 PM UTC
Resolved
Jan 27, 2026, 07:40 PM UTC
Duration
—
Affected: Querying
Timeline · 4 updates
  1. investigating Jan 27, 2026, 05:08 PM UTC

    Status: Investigating We are experiencing increased error rate for queries. Affected components Querying (Partial outage)

  2. monitoring Jan 27, 2026, 05:44 PM UTC

    Status: Monitoring We identified a misconfiguration in monitor processing, which has now been mitigated. Query performance might be degraded while queues are processed. Affected components Querying (Operational)

  3. monitoring Jan 27, 2026, 07:10 PM UTC

    Status: Monitoring All queues have finished processing, query processing is nominal. Affected components Querying (Operational)

  4. resolved Jan 27, 2026, 07:40 PM UTC

    Status: Resolved This incident has been resolved. Affected components Querying (Operational)

Read the full incident report →