Live / Aircall / Incident
Aircall: Issues logging in to Aircall Workspace
Aircall · aircall.ioMajor incidentResolved2026-10-01 07:01 UTC
Public — what happened
Summary
Aircall reported a major incident on October 1, 2026, beginning at 05:36 UTC, in which users could not sign in to Aircall Workspace or place and take calls. By 05:54 UTC, Aircall said it believed the problem stemmed from a surge of errors it had seen between 05:10 and 05:23 UTC, and that it was working to bring the service back to full stability. At 06:33 UTC the company said performance had been steady for a short period and it was keeping watch, and the incident was marked resolved at 07:01.
Timeline
- Started — 2026-10-01 05:36 UTC
- Investigating — 2026-10-01 05:36 UTC
- Identified — 2026-10-01 05:54 UTC
- Monitoring — 2026-10-01 06:33 UTC
- Resolved — 2026-10-01 07:01 UTC · 1h 26m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Aircall against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Aircall: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Aircall report →
More from Aircall
Covered in The Squid’s Ink, Week 41, 2026, our weekly internet health report.