Axiom: Elevated errors from queries
Affected components: AlertingQuerying
Timeline of updates
- investigating
We're investigating elevated error rates from querying in our US region.
- identified
We have identified the problem and are deploying a fix.
- identified
While the query error rate has been nominal for a while, we're seeing second-order effects that manifest as delays with monitors.
- monitoring
All queues have cleared, we continue monitoring to ensure system stability.
- resolved
Monitors are now processing in real time, no visible delays.
Changes Rewindex caught on this incident
- Major incident: Elevated errors from queries
- Incident updated: Elevated errors from queries
- Incident updated: Elevated errors from queries
- Incident updated: Elevated errors from queries
- Incident updated: Elevated errors from queries
- Incident silently edited: Elevated errors from queries
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves these records existed by then and have not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured
In the 2026-10-27 checkpoint, timestamped by DigiCert and FreeTSA on . Record hash
abbe6c5d6a03489f…Version 2 captured
In the 2026-10-27 checkpoint, timestamped by DigiCert and FreeTSA on . Record hash
7c3dba6f23666ef5…Version 3 captured
In the 2026-10-27 checkpoint, timestamped by DigiCert and FreeTSA on . Record hash
2567b3462b5cab29…Version 4 captured
In the 2026-10-27 checkpoint, timestamped by DigiCert and FreeTSA on . Record hash
5ba748e985a331a4…Version 5 captured
In the 2026-10-27 checkpoint, timestamped by DigiCert and FreeTSA on . Record hash
2dc6fa609494285a…
Rewindex captured a newer version after the last checkpoint; the next run () commits it.
Impact, status and times are the vendor’s own, as last archived. View on status.axiom.co (opens in new tab).