Operational Aircall status
aircall.io · Official status page (Statuspage-compatible JSON)
FROM ALL SOURCES
No sign of a widespread Aircall problem right now; every source we read is quiet.
confidence: medium Vendor: operational · users: normal · routing: no data.
- Vendor status page Operational · 1 open incident
- User reports 0 in 15 min vs ~0 typical
- Routing / BGP no ASN mapped, so no routing view
- News & network weather no recent mentions
- Providers it may run on (inferred) no mapped dependencies
- CISA KEV (context) no recent entries for this vendor
Regions mentioned: Inbound Calls, Conversation Center, Aircall Workspace (Web)
| Clock | Started | Running |
|---|---|---|
| Vendor clock when the vendor's open incident started | 22 days | |
| Crowd clock when user reports began rising above normal | not seen | n/a |
| Network clock when routing anomaly data first flagged it | not seen | n/a |
| ORBIT clock when our checker first recorded the change | not seen | n/a |
Evidence
- Official page: Operational (“All Systems Operational”). evidence confidence: high
- Vendor stage: resolved on “Increased Platform Errors”. evidence confidence: high
- User reports are within normal range (0 in 15 min). evidence confidence: low
What we don't know: what is happening inside Aircall's own systems, how many users are actually affected (reports are self-selected and unverified), and anything from routing / bgp, providers it may run on (inferred). Routing data shows reachability, not whether the app works.
Automated analysis by Cloudy_Day NetWeather; not a personal statement. Generated .
Cloudy_Day's take
Stage vs. health
The vendor's stage is “resolved”. Stage tells you where they are in their process; health is what users experience. Right now vendor: operational · users: normal · routing: no data. Vendor status and outside signals roughly agree.
Who depends on whom
We don't map other services that depend on Aircall. Dependency chains are where single points of failure hide.
Identity & trust lens
Even without an identity system involved, outages push people toward workarounds: password resets, unofficial apps and “status” links in DMs. Each one is a trust decision. Use official channels.
For users
Nothing points to a broad problem. If it's broken for you, try “Is it just me?” and check your own network first.
For security teams
Treat this as an availability event unless an official source says otherwise. Check which of your systems sit on Aircall, watch for outage-themed phishing aimed at your users, and log what you see with timestamps (all four clocks).
What to watch next
Any new vendor incident, a jump in user reports above baseline, or trouble at the providers Aircall may depend on.
Automated analysis by Cloudy_Day NetWeather; not a personal statement. Independent researcher; not affiliated with Aircall. No blame or attack claims without an official source. Generated .
INCIDENT REPLAY
Increased Platform Errors
major resolved · started · resolved
4 updates
- identified
We are currently investigating elevated error rates affecting some Aircall services. Some customers may experience issues placing or receiving calls, saving call outcomes, or loading parts of the app. The issue appears related to a degradation at one of our infrastructure providers. We’re working closely with them to mitigate the impact and will share another update within 60 minutes, or sooner if we have more information. We are continuously working to stabilize the system performance.
- identified
We’re continuing to work on the elevated error rates affecting some Aircall services. Some customers may still experience issues placing or receiving calls, saving call outcomes, or loading parts of the app. The issue is still related to a degradation at one of our infrastructure providers. We’re working closely with them, and our teams are actively monitoring and pursuing mitigation options. We don’t have a resolution time yet. We’ll share our next update within 60 minutes, or sooner if anything changes.
- monitoring
A fix has been implemented, and we’re seeing error rates return to normal for the affected Aircall services. We’re continuing to monitor closely to make sure service remains stable. Some customers may still see lingering effects, such as calls or call outcomes that didn’t complete during the disruption. If you’re still experiencing issues, please contact Support and we’ll help. We’ll post another update within 60 minutes, or sooner if anything changes.
- resolved
This incident has been resolved and the affected Aircall services are operating as expected. Our infrastructure provider has confirmed recovery on their side, and we’ve monitored our systems to verify service has remained stable. If you’re still seeing any issues, please contact Aircall Support and we’ll help right away.
Community comments (0)
Comments are opinions of visitors, not statements by Cloudy_Day. Every comment is held for review before it appears. Links are removed, and personal data is redacted. Community guidelines.
No approved comments yet.
How to read this: official status comes from each provider's own public status page. User reports are unverified visitor reports. Things that happen at the same time are coincidence, not causation. Cloudy_Day is independent and not an official status source for any company listed.