Vendor reports: major outageResolved · vendor status “resolved”Official status API
EU Query Downtime
Reported by Axiom · Observability & Incident · source last read 3 min ago
- Vendor start
- Feb 26, 2026, 16:13 UTC
- Vendor's clock
- Resolved
- Feb 26, 2026, 15:55 UTC
- Vendor's clock
- First seen by Statuswall
- Before tracking began
- Statuswall's clock
- Duration
- Not available
- Needs both vendor times
Summary
Built from the facts below, no AI
Potential impact, not a confirmed outage of your systems.
What the vendor confirmed
What is unknown
Last update in these facts: 2026-02-26 16:13 UTC · summary s1, evidence ac1fb2014aeb614a
Evidence (7)
- E1Axiom reports major outage. (vendor) source (opens in a new tab)
- E2Vendor title: "EU Query Downtime". (vendor) source (opens in a new tab)
- E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
- E4Vendor-reported start: 2026-02-26 16:13 UTC. (vendor) source (opens in a new tab)
- E5The vendor did not state which regions are affected. (Statuswall)
- E6The vendor attached no components. (Statuswall)
- E7Vendor-reported resolution: 2026-02-26 15:55 UTC. (vendor)
Affected scope
Not stated by the vendor
Components: not stated by the vendor
The vendor's feed gives no region for this incident. It is not assumed to be global.
Potential relevance
Axiom is not in your stack. Follow it to see whether reports like this fall inside the regions you use.
Timeline
Vendor times come from the vendor. “Seen by Statuswall” times are when Statuswall noticed a change, which can lag the vendor by a few minutes. Statuswall does not store the vendor's update text; read it on the official page.
- Feb 26, 2026, 15:55 UTCVendor-reported resolutionVendor time
- Feb 26, 2026, 16:13 UTCVendor-reported startVendor time
No changes observed yet. Statuswall began recording changes on incidents in November 2026.