Aircall Status

Resolved: System performance has remained stable during monitoring. We can confirm that this situation has been fully resolved.

We appreciate your patience and understanding while we worked with our Provider 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.

Monitoring: We are observing improvements from the past minutes.

The system seems to be stable now, but we continue to be in contact with our Provider, and we're actively monitoring the system performance to ensure full resolution of this issue.

We will provide further updates as soon as necessary.

Identified: We have identified service degradation in one of our real-time services, which is provided by one of Aircall's infrastructure providers.

Our provider is actively investigating increased latency on some of their clusters.

Investigating: We are currently investigating reports of instability in some services.

We will provide further feedback when possible.

Resolved: System performance has remained stable during the past few hours of monitoring.

We appreciate your patience and understanding while we worked with our Provider 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.

Monitoring: The system has been fully stable for the past 1 hour. Nonetheless, our provider has not yet considered the issue resolved.

We continue to monitor the situation, and we will provide further information as soon as further developments are made.

Monitoring: The mitigation implemented by our provider seems to be stabilizing the impacted clusters.

We continue to monitor the situation, and we will provide further information as soon as further developments are made.

Monitoring: We are observing a new recovery.

We continue to be in contact with our Provider, and we're actively monitoring the system performance.

We will provide further updates as soon as necessary.

Identified: We are observing another spike in the performance of our real-time services.

We have engaged with our provider, who continues to investigate the recurrence of the issue on some of their clusters.

We will provide further information as soon as further developments are made.

Resolved: System performance has remained stable during monitoring. We can confirm that this situation has been fully resolved.

We appreciate your patience and understanding while we worked with our Provider 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.

Monitoring: We are observing improvements from the past minutes.

The system seems to be stable now, but we continue to be in contact with our Provider, and we're actively monitoring the system performance to ensure full resolution of this issue.

We will provide further updates as soon as necessary.

Identified: We have identified service degradation in one of our real-time services, which is provided by one of Aircall's infrastructure providers.

Our provider is actively investigating increased latency on some of their clusters.

Investigating: We are currently investigating reports of instability in some services.

We will provide further feedback when possible.

Resolved: System performance has remained stable during the past few hours of monitoring.

We appreciate your patience and understanding while we worked with our Provider 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.

Monitoring: The system has been fully stable for the past 1 hour. Nonetheless, our provider has not yet considered the issue resolved.

We continue to monitor the situation, and we will provide further information as soon as further developments are made.

Monitoring: The mitigation implemented by our provider seems to be stabilizing the impacted clusters.

We continue to monitor the situation, and we will provide further information as soon as further developments are made.

Monitoring: We are observing a new recovery.

We continue to be in contact with our Provider, and we're actively monitoring the system performance.

We will provide further updates as soon as necessary.

Identified: We are observing another spike in the performance of our real-time services.

We have engaged with our provider, who continues to investigate the recurrence of the issue on some of their clusters.

We will provide further information as soon as further developments are made.

Resolved: System performance has remained stable during monitoring. We can confirm that this situation has been fully resolved.

We appreciate your patience and understanding while we worked with our Provider 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.

Monitoring: We are observing improvements from the past minutes.

The system seems to be stable now, but we continue to be in contact with our Provider, and we're actively monitoring the system performance to ensure full resolution of this issue.

We will provide further updates as soon as necessary.

Identified: We have identified service degradation in one of our real-time services, which is provided by one of Aircall's infrastructure providers.

Our provider is actively investigating increased latency on some of their clusters.

Investigating: We are currently investigating reports of instability in some services.

We will provide further feedback when possible.

Resolved: System performance has remained stable during the past few hours of monitoring.

We appreciate your patience and understanding while we worked with our Provider 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.

Monitoring: The system has been fully stable for the past 1 hour. Nonetheless, our provider has not yet considered the issue resolved.

We continue to monitor the situation, and we will provide further information as soon as further developments are made.

Monitoring: The mitigation implemented by our provider seems to be stabilizing the impacted clusters.

We continue to monitor the situation, and we will provide further information as soon as further developments are made.

Monitoring: We are observing a new recovery.

We continue to be in contact with our Provider, and we're actively monitoring the system performance.

We will provide further updates as soon as necessary.

Identified: We are observing another spike in the performance of our real-time services.

We have engaged with our provider, who continues to investigate the recurrence of the issue on some of their clusters.

We will provide further information as soon as further developments are made.

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.

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.

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.

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: 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: We continue to monitor the system and we can observe some sporadic issues with Calls and Call Controls.

Monitoring: We are seeing service degradation on Calling service, and we're currently investigating it.

Monitoring: All the services have been recovered to regular performance, including Analytics.

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.

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.

Identified: We start to observe signs of recovery. Connectivity rates are increasing for Messaging. We continue to monitor the Analytics and Calling services.

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 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: 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: 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.

Investigating: We are currently investigating an issue with call and messaging connection.

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.

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.

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.

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: 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: We continue to monitor the system and we can observe some sporadic issues with Calls and Call Controls.

Monitoring: We are seeing service degradation on Calling service, and we're currently investigating it.

Monitoring: All the services have been recovered to regular performance, including Analytics.

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.

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.

Identified: We start to observe signs of recovery. Connectivity rates are increasing for Messaging. We continue to monitor the Analytics and Calling services.

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 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: 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: 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.

Investigating: We are currently investigating an issue with call and messaging connection.

Resolved: The issue where the AI Voice Agent was not connecting to calls has been resolved.

Monitoring: A fix has been implemented and we are monitoring the results.

Investigating: We are currently investigating an issue where the AI Voice Agent is not connecting to calls.

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.

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.

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.

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: 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: We continue to monitor the system and we can observe some sporadic issues with Calls and Call Controls.

Monitoring: We are seeing service degradation on Calling service, and we're currently investigating it.

Monitoring: All the services have been recovered to regular performance, including Analytics.

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.

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.

Identified: We start to observe signs of recovery. Connectivity rates are increasing for Messaging. We continue to monitor the Analytics and Calling services.

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 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: 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: 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.

Investigating: We are currently investigating an issue with call and messaging connection.

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.

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.

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.

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: 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: We continue to monitor the system and we can observe some sporadic issues with Calls and Call Controls.

Monitoring: We are seeing service degradation on Calling service, and we're currently investigating it.

Monitoring: All the services have been recovered to regular performance, including Analytics.

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.

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.

Identified: We start to observe signs of recovery. Connectivity rates are increasing for Messaging. We continue to monitor the Analytics and Calling services.

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 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: 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: 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.

Investigating: We are currently investigating an issue with call and messaging connection.