Elevated query error rates

What to do

• Check whether your product depends on Axiom. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 0m it lasted.

  Anything that failed between 2026-10-21 12:49 UTC and 2026-10-21 12:08 UTC may need a replay.

• Subscribe to Axiom's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=axiom works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Axiom 2

1. investigatingOct 21, 2026, 11:35 AM UTC

   We are investigating elevated query error rates and increased latency affecting some customers. Our engineering team is actively working to identify the cause and restore normal operation. We will provide further updates as more information becomes available.

   provider

2. resolvedOct 21, 2026, 12:08 PM UTC

   A portion of queries experienced increased latency and elevated error rates which was caused by an interaction between our service mesh and internal cache services. Following a deployment, some query workers continued attempting to connect to outdated cache instance addresses, even after the replacement instances had become healthy. This resulted in query timeouts and failures. We identified the underlying issue and mitigated it by adjusting the networking configuration of our query workers. Normal operation was restored by 12:07 UTC, and query error rates have returned to their expected levels. We are reviewing the incident and implementing measures to prevent similar issues in the future.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.