Vendor reports: degradedResolved · vendor status “resolved”Official status API
Query issues
Reported by Axiom · Observability & Incident · source last read just now
- Vendor start
- Jan 13, 2026, 22:08 UTC
- Vendor's clock
- Resolved
- Jan 13, 2026, 22:31 UTC
- Vendor's clock
- First seen by Statuswall
- Before tracking began
- Statuswall's clock
- Duration
- 23 min
- From vendor start and resolution
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-01-13 22:31 UTC · summary s1, evidence a0b75031722d1568
Evidence (7)
- E1Axiom reports degraded. (vendor) source (opens in a new tab)
- E2Vendor title: "Query issues". (vendor) source (opens in a new tab)
- E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
- E4Vendor-reported start: 2026-01-13 22:08 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-01-13 22:31 UTC. (vendor)
Affected scope
Not stated by the vendor
Components: not stated by the vendor
No region Statuswall recognises is stated for this incident (place names and provider-specific codes are not converted). 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.
- Jan 13, 2026, 22:08 UTCVendor-reported startVendor time
- Jan 13, 2026, 22:31 UTCVendor-reported resolutionVendor time
No changes observed yet. Statuswall began recording changes on incidents in November 2026.