Axiom status history
Current state: operational — “All Systems Operational” per https://status.axiom.co (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.
How long do Axiom incidents last?
From 19 incidents with a vendor-posted start and resolve time. Longest on record: Console UI Authentication Degraded — 2.1 days (2026-08-10 17:08 UTC). Excluded, never estimated: 5 resolved before started (vendor data error). Duration is the gap between the vendor's own posted timestamps — it is not measured downtime, uptime or an SLA figure, and a vendor that posts every blip will look worse here than one that posts nothing. Same rule as the outage-duration dataset.
Incidents on record (24)
| Started | Incident | Status | Impact | Duration |
|---|---|---|---|---|
| 2026-08-10 17:08 UTC | Console UI Authentication Degraded | resolved | minor | 2 d 2 h |
| 2026-07-15 10:17 UTC | Elevated Queries error rate | resolved | minor | 9 min |
| 2026-06-30 18:30 UTC | Ingest through Firehose impacted | resolved | minor | 3 h 09 min |
| 2026-06-19 10:24 UTC | EU Edge Deployment Metrics Query Performance Degradation. | resolved | minor | 4 h 21 min |
| 2026-05-15 17:17 UTC | Increased Ingest and Query Error Rates | resolved | major | 4 h 09 min |
| 2026-05-08 00:16 UTC | Increase in query error rate | resolved | minor | 33 min |
| 2026-04-28 14:27 UTC | Ingest Error Rate Spike | resolved | minor | 41 min |
| 2026-04-17 15:00 UTC | Dataset trims are experiencing delays | resolved | none | 14 h 11 min |
| 2026-04-14 09:43 UTC | Email notifications delayed for Legacy EU monitors | resolved | none | — |
| 2026-04-12 13:21 UTC | Degraded Query performance on EU Edge Deployment | resolved | major | 1 h 52 min |
| 2026-03-06 01:29 UTC | Increased ingest error rate | resolved | minor | 32 min |
| 2026-02-26 17:46 UTC | EU Query performance degradation. | resolved | none | — |
| 2026-02-26 16:13 UTC | EU Query Downtime | resolved | critical | — |
| 2026-01-27 17:16 UTC | Queries partial outage | resolved | major | 2 h 24 min |
| 2026-01-17 01:06 UTC | API Ingest Degraded Performance | resolved | minor | 11 h 54 min |
| 2026-01-13 22:08 UTC | Query issues | resolved | minor | 22 min |
| 2026-01-09 21:03 UTC | Increase in ingest error rates | resolved | major | 2 h 37 min |
| 2025-12-15 14:51 UTC | Increase in query error rates | resolved | major | 10 min |
| 2025-12-05 15:28 UTC | Axiom Console log-in disruption (resolved) | resolved | major | — |
| 2025-11-03 18:10 UTC | EU Monitor Processing failures | resolved | major | — |
| 2025-10-20 07:55 UTC | System issues | resolved | critical | 3 h 36 min |
| 2025-10-06 08:03 UTC | Integrations Degraded Performance | resolved | minor | 3 h 10 min |
| 2025-09-15 17:39 UTC | Increase in ingest errors | resolved | minor | 4 h 49 min |
| 2025-08-28 14:41 UTC | Increase in ingest errors | resolved | minor | 2 h 28 min |
Titles, statuses and impact levels are the vendor's own words. Durations marked approx. are inferred from the poll that first found the incident gone. Shows the latest 60; the JSON has everything we hold (up to 400 days).
Watch Axiom with the template
Put this in config.json of your fork and add a WEBHOOK_URL secret:
{
"vendors": [
"axiom"
],
"format": "auto",
"map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
"unreachable_after": 3,
"mute_maintenance": false
}