Users stuck on call status

What to do

• Check whether you use Aircall Aircall Workspace (Web), Aircall Workspace (Desktop). 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 1h 9m it lasted.

  Anything that failed between 2026-08-26 18:30 UTC and 2026-08-26 19:38 UTC may need a replay.

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

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

Updates from Aircall 4

1. investigatingAug 26, 2026, 6:30 PM UTC

   We are currently investigating some occurrences of Users being in the On a Call status and not moving automatically to Available.

   provider

2. identifiedAug 26, 2026, 6:40 PM UTC

   The issue seems to be caused by a transient spike in errors that was circumscribed to the specific moment in time: 17:26 UTC. We are working on releasing the impacted users from the On a Call status.

   provider

3. monitoringAug 26, 2026, 7:15 PM UTC

   The system has been operating normally since the error spike, and the impacted Users should now be on regular User status.

   provider

4. resolvedAug 26, 2026, 7:38 PM UTC

   The root cause of the issue has been found and resolved.

   provider

Corrections

None so far.

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