Is Axiom down?
Last checked just nowNo incidents right now.
Axiom is operational right now. Last checked just now; the most recent incident resolved 19d ago.
Real-time Axiom status, recent outages, and incident history — pulled directly from Axiom's official status page at https://status.axiom.co/# every 5 minutes. Pingoru tracks 12 Axiom services and has captured 8 incidents in the last 90 days (98.80% uptime). Get email, Slack, Discord, or webhook alerts the moment Axiom reports a new incident — free for 5 monitors, no credit card.
Recent outages & incidents
Past 90 days- Querying
Timeline · 2 updates
- investigating · Jul 15, 2026, 10:17 AM UTC
Status: Investigating Some queries are failing due to recent deployment, we are on it. Affected components Querying (Degraded performance) Querying (Degraded performance)
- resolved · Jul 15, 2026, 10:26 AM UTC
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)
Latest: 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 af…
-
- Ingest
Timeline · 2 updates
- 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)
- 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)
Latest: 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…
-
- Querying
Timeline · 3 updates
- 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)
- 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)
- 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)
Latest: Status: Resolved Underlying infrastructure issues have been resolved, metrics queries on EU Edge Deployment should now be fully operational. Affected components Querying (Operation…
-
- APIAPIIngestQueryingEndpointsAppIngestAlerting
Timeline · 4 updates
- 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)
- 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)
- 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)
- 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)
Latest: Status: Resolved This incident is fully resolved. Affected components Endpoints (Operational) Ingest (Operational) App (Operational) API (Operational) Alerting (Operational) Queryi…
-
- QueryingQuerying
Timeline · 3 updates
- investigating · May 08, 2026, 12:16 AM UTC
Status: Investigating We are investigating increase in query errors Affected components Querying (Degraded performance)
- 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)
- resolved · May 08, 2026, 12:42 AM UTC
Status: Resolved We see full recovery of the query subsystem Affected components Querying (Operational)
Latest: Status: Resolved We see full recovery of the query subsystem Affected components Querying (Operational)
-
- Elevated Queries error rate ResolvedStarted Jul 15, 2026, 10:26 AM UTC · Resolved Jul 15, 2026, 10:26 AM UTC · —
- Ingest through Firehose impacted ResolvedStarted Jun 30, 2026, 09:39 PM UTC · Resolved Jun 30, 2026, 09:39 PM UTC · —
- Started Jun 19, 2026, 02:45 PM UTC · Resolved Jun 19, 2026, 02:45 PM UTC · —
- Started May 15, 2026, 09:27 PM UTC · Resolved May 15, 2026, 09:27 PM UTC · —
- Increase in query error rate ResolvedStarted May 08, 2026, 12:50 AM UTC · Resolved May 08, 2026, 12:50 AM UTC · —