Live  /  Providers  /  Aircall

Aircall

aircall.ioNo open incidents

Independent assessment — SquidGrid is not affiliated with Aircall. Provider-published information is labeled as such; SquidGrid’s own measurements are observations of network paths, not determinations of fault.

SaaS & business software · SquidGrid tracks Aircall’s own status and independently measures the internet paths that reach it, so you can tell a provider-side problem from a problem on the route to it.

Public — what Aircall is reporting

Current & recent incidents

Resolved

Increased Platform Errors

Major impact · 2026-10-29 23:44 UTC · source

Resolved

Users with connectivity issues

Minor impact · 2026-10-17 17:57 UTC · source

Resolved

Increased Error Rate

Major impact · 2026-10-13 16:19 UTC · source

Resolved

Calling Issues

Major impact · 2026-10-12 10:17 UTC · source

Resolved

Partner Integrations Not Receiving Call Events

Minor impact · 2026-10-08 04:58 UTC · source

Incident titles and states as published by the provider. Times in UTC.

Track record

SquidGrid has archived 12 incidents from Aircall’s own status page since 2026-09-01.

Recent incidents in the archive

Computed by SquidGrid from the incidents Aircall published. Their own page shows only recent history; this archive keeps every one.

Independent path health

A status page tells you what Aircall has published. SquidGrid independently observes the actual routes from its own worldwide fleet against their own baselines — so when a path moves off its usual range before (or without) a status post, you still see it, and you see where.

Aircall runs its services on other companies’ networks rather than operating its own, so path measurements roll up to its hosting providers. SquidGrid’s assessment of Aircall is its published incident record, archived and analyzed above and kept after the provider’s own page forgets it.

SquidGrid is not affiliated with Aircall.