Changes / Aircall / Calls and Messages failing to connect
Aircall: Major incident: Calls and Messages failing to connect
Summary
Aircall’s major degradation disrupted calls, messaging, Agent Status and Call Controls from 2025-10-20 07:07 UTC to 2025-10-21 06:46 UTC (23 h 39 min). Aircall cited provider 500 errors and an AWS-related messaging-provider disruption. Service was restored and monitoring confirmed stability; users with lingering issues were advised to reload the app.
Machine-written from the diff below (Sol; type: incident degradation). Check the diff before relying on it.
Major incidentLabel: degradation (model (Jev), 52%)Changed Detected Source: stspg.io (opens in new tab)
What changed
Before: not present
After: Calls and Messages failing to connect
Before: not present
After: major
Before: not present
After: resolved
Before: not present
After: 2025-10-20 07:07 UTC
Before: not present
After: 2025-10-21 06:46 UTC
Before: not present
After: Aircall Apps - Agent Status, Aircall Apps - Keypad & Call Controls, Aircall Dashboard - Analytics, Inbound Calls, Network - Inbound Calls, Network - Inbound Messaging (SMS/MMS), Network - Outbound Calls, Network - Outbound Messaging (SMS/MMS), Outbound Calls
Before: not present
After: We are currently investigating an issue with call and messaging connection.
Before: not present
After: The issue has been identified as caused by our communication platform provider responding with error code 500 to a subset of our connection requests.
We are in communication with our provider, and we will provide further details as soon as progress is made.
Before: not present
After: Our communication platform provider is being impacted by an issue with a worldwide infrastructure provider.
This issue with the worldwide infrastructure provider is directly impacting Aircall Analytics.
Before: not present
After: We continue to work with our providers to try to mitigate the impact of the infrastructure provider. The impact is spread across different internet-based services, and they are addressing it with the highest priority.
We will provide further details as soon as progress is made.
Before: not present
After: The infrastructure provider has identified the issue as being related to a DNS resolution service and applied a fix.
We will provide further details as soon as progress is made.
Before: not present
After: We start to observe signs of recovery. Connectivity rates are increasing for Messaging. We continue to monitor the Analytics and Calling services.
Before: not present
After: We are seeing partial recovery as our communication platform provider is scaling systems to handle the influx of traffic. Users may notice Inbound and Outbound calling improvements.
Before: not present
After: We can confirm that most of the Calls and Messages are connecting.
Analytics may still present some delays in loading historical data due to queued requests.
We continue to be in contact with our providers, and we're actively monitoring the system performance to ensure full resolution.
Before: not present
After: All the services have been recovered to regular performance, including Analytics.
Before: not present
After: We are seeing service degradation on Calling service, and we're currently investigating it.
Before: not present
After: We continue to monitor the system and we can observe some sporadic issues with Calls and Call Controls.
Before: not present
After: There is currently intermittent impact on a subset of inbound and outbound calls.
We continue to be in contact with our providers to ensure full system stabilization.
Before: not present
After: Customers may be experiencing some issues with Calling (Dequeuing, Call Controls, etc) due to the degradation of response times of our communication platform.
We are working with our providers to stabilize their services and we will provide further updates about the as soon as progress is made.
Before: not present
After: One of our real time messaging providers is being impacted by the AWS incident which causes Aircall Users to currently experience issues with Agent Status and Call Controls.
We are working with our providers to stabilize their services and we will provide further updates about the as soon as progress is made.
Before: not present
After: Our messaging provider has recovered from the issue caused by the AWS incident. Agents should now see recovery in Agent Status updates and Call Controls.
We are closely monitoring the situation to ensure full stability and will provide another update once we confirm everything is functioning as expected.
Before: not present
After: System performance has remained stable during the past hours of monitoring.
We appreciate your patience and understanding while we worked with our Providers to restore normal functionality.
If you continue to experience any related issues, please reload the app, and in case the issue persists, don’t hesitate to reach out to our Support team for further assistance.
First version of this incident archived by Rewindex. View the live incident (opens in new tab).
History of this incident
| When (UTC) | Change | Kind |
|---|---|---|
| Major incident: Calls and Messages failing to connect (this change) Aircall’s major degradation disrupted calls, messaging, Agent Status and Call Controls from 2025-10-20 07:07 UTC to 2025-10-21 06:46 UTC (23 h 39 min). Aircall cited provider 500 errors and an AWS-related messaging-provider disruption. Service was restored and monitoring confirmed stability; users with lingering issues were advised to reload the app. | Major incident |