Provider
AircallIncident detail
Calls and Messages failing to connect
Timeline window
to
Get alerted the next time Aircall breaks
Free email alerts for the handful of vendors you cannot afford to miss. No card, live in about a minute. Paid plans add Slack, Teams, Discord, and webhook delivery across your whole stack, plus higher API quotas.
Timeline
Incident updates
Every update on the official status source, oldest to newest, exactly as it appeared there.
Investigating
We are currently investigating an issue with call and messaging connection.
Identified
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.
Identified
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.
Identified
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.
Identified
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.
Identified
We start to observe signs of recovery. Connectivity rates are increasing for Messaging. We continue to monitor the Analytics and Calling services.
Identified
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.
Monitoring
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.
Monitoring
All the services have been recovered to regular performance, including Analytics.
Monitoring
We are seeing service degradation on Calling service, and we're currently investigating it.
Identified
We continue to monitor the system and we can observe some sporadic issues with Calls and Call Controls.
Identified
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.
Identified
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.
Identified
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.
Monitoring
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.
Resolved
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.
Keep exploring
More from Aircall
Neighboring incidents on Aircall's timeline and the rest of their record on OutageDeck.