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
| Clock | Started | Running |
|---|---|---|
| Vendor clock when the vendor's open incident started | 87 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 “Inbound issues impacting some Mexico phone numbers”. 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
Inbound issues impacting some Mexico phone numbers
minor resolved · started · resolved
5 updates
- identified
We are currently handling an issue impacting one of Aircall's Carrier Providers in Mexico. We will provide updates as soon as we have progress.
- identified
We continue to actively work with the impaired Carrier Partner on a resolution. This issue, impacting a subset of Mexican numbers, causes duplicated inbound call entries, though the calls themselves do not connect. We are actively working on this and will share progress as soon as possible.
- identified
Aircall's Carrier Providers in Mexico have informed us that they are continuing to investigate the issue with their team of specialists and will update us as soon as they have progress.
- monitoring
Aircall's Carrier Partner in Mexico has informed us that they have applied a fix for the issue impacting a subset of Mexican numbers, which caused duplicated inbound call entries with calls failing to connect. Early results are positive, and we are now monitoring the situation closely to confirm full recovery. We will provide a further update once the fix is fully validated.
- resolved
The Carrier Partner's fix has been validated and inbound calls on the affected Mexican numbers are operating normally. This incident is now resolved. Thank you for your patience.
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.