# Users stuck on call status

- Provider: [Aircall](https://down.guide/aircall)
- Level: confirmed
- Impact: Degraded
- lasted 1h 9m
- started 2026-08-26 18:30 UTC
- Aircall Workspace (Web), Aircall Workspace (Desktop)
- id: DWN-6c53918a8b
- Official page: https://stspg.io/yf9287sscxw8

## Updates from Aircall
### 2026-08-26 18:30 UTC: investigating
We are currently investigating some occurrences of Users being in the On a Call status and not moving automatically to Available.

### 2026-08-26 18:40 UTC: identified
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.

### 2026-08-26 19:15 UTC: monitoring
The system has been operating normally since the error spike, and the impacted Users should now be on regular User status.

### 2026-08-26 19:38 UTC: resolved
The root cause of the issue has been found and resolved.

From the builder: does your app depend on Aircall? [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=aircall) detects problems in your own logs without hand-written monitors, and you can ask it in plain language which errors mention Aircall.

---
down.guide reads providers' official status pages every minute and adds its own evidence, always labeled. Free, no account. Agents: MCP at https://down.guide/mcp, REST at https://down.guide/api/v1, feeds at https://down.guide/feed. Built by [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=DWN-6c53918a8b), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.