Aircall

Affected: Aircall Workspace (Web), Aircall Workspace (Desktop), Aircall Mobile App (iOS), Aircall Mobile App (Android), Aircall Chrome Extension

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-17 16:23 UTC

   We are currently investigating a subset of users with connectivity issues.

2. identified 2026-10-17 16:48 UTC

   The issue seems to be limited to one of the Roaming regions - Singapore. Affected users can navigate to Settings > Network Diagnosis > choose a different Roaming selection. Other regions are operating normally.

3. monitoring 2026-10-17 17:52 UTC

   Users connected to the Singapore Roaming location have been moved to the Roaming location Japan. We are now observing improvements. Our team will continue monitoring it until full resolution is confirmed.

4. resolved 2026-10-17 17:57 UTC

   We can confirm this issue is fully resolved. The Roaming region Singapore is fully operational. If you continue to experience any issues, don’t hesitate to reach out to our Support team for further assistance.

Excerpts are shortened. Read the full incident on Aircall's status page.

Affected: Inbound Calls, Conversation Center, Aircall Workspace (Web), Outbound Calls, Aircall Workspace (Desktop), Analytics, Live Monitoring

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-13 15:38 UTC

   We are currently investigating a spike in errors that may cause different sporadic issues.

2. investigating 2026-10-13 15:50 UTC

   We are continuing to investigate this issue.

3. identified 2026-10-13 15:50 UTC

   The issue is circumscribed to a subset of actions, and it's not permanent. We are developing the necessary actions to mitigate the impact.

4. monitoring 2026-10-13 15:53 UTC

   We are observing improvements across services. We will continue monitoring until full resolution is confirmed.

5. resolved 2026-10-13 16:19 UTC

   We can confirm this issue is fully resolved. If you continue to experience any issues logging into Aircall, making or receiving calls, or loading the Dashboard, please don’t hesitate to reach out to our Support team for further assistance.

Excerpts are shortened. Read the full incident on Aircall's status page.

Affected: Inbound Calls, Outbound Calls

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-12 09:29 UTC

   We are currently investigating reports of customers not being able to receive or make calls.

2. identified 2026-10-12 09:44 UTC

   The issue is circumscribed to a subset of customers and we are taking actions to mitigate the impact. Improvements should be experienced within a few minutes.

3. monitoring 2026-10-12 10:05 UTC

   A fix has been implemented, and we are monitoring the results. Voice traffic seems to be stable now.

4. resolved 2026-10-12 10:17 UTC

   The issue has now been resolved.

Excerpts are shortened. Read the full incident on Aircall's status page.

Affected: Other Integrations

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-10-07 01:20 UTC

   We are currently investigating an issue affecting the following Aircall partner integrations: Gorgias Jobadder Klaviyo Help Scout Bullhorn Sellsy What's impacted: Call events from Aircall are not being delivered to these integrations New installs and OAuth flows through these...

2. investigating 2026-10-07 03:53 UTC

   We continue to investigate the disruption affecting the following partner integrations: Gorgias Jobadder Klaviyo Help Scout Bullhorn Sellsy We have identified the root cause as an infrastructure issue on the third-party side. Our team is actively working with our integration...

3. identified 2026-10-07 08:02 UTC

   The issue originates with the infrastructure that hosts these integrations. We are working with our integration partner to restore it

4. identified 2026-10-07 13:40 UTC

   Our integration partner is working with their infrastructure provider to restore these services.

5. monitoring 2026-10-07 22:14 UTC

   Our integration partner has restored services, and we have confirmed the impacted integrations are working as expected. We have reconnected the integrations that were disabled, but in some cases customers may need to reinstall them from the Aircall Dashboard. We are monitoring...

6. resolved 2026-10-08 04:58 UTC

   The disruption affecting the following partner integrations has been resolved: Gorgias Jobadder Klaviyo Help Scout Bullhorn Sellsy Call events from Aircall are now being delivered successfully to these integrations. We apologise for the disruption and are conducting a...

Excerpts are shortened. Read the full incident on Aircall's status page.

Affected: Inbound Calls, Inbound Messaging (SMS/MMS), Outbound Calls, Outbound Messaging (SMS/MMS), eSIM

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-05 11:59 UTC

   We are investigating again reports of French and Spanish numbers failing intermittently with messaging and calling.

2. identified 2026-10-05 12:01 UTC

   We are working with our carrier that identified the issue and is taking remedial actions.

3. identified 2026-10-05 12:18 UTC

   We are observing recovery with the voice service.

4. monitoring 2026-10-05 12:22 UTC

   We are observing recovery for messaging too.

5. resolved 2026-10-05 13:00 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Aircall's status page.

Affected: Inbound Calls, Inbound Messaging (SMS/MMS), Numbers Management (Purchase, Porting, Compliance), eSIM

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-05 09:32 UTC

   We are investigating reports of French and Spanish numbers failing intermittently with messaging and calling.

2. investigating 2026-10-05 09:33 UTC

   We are continuing to investigate this issue.

3. identified 2026-10-05 09:58 UTC

   We are working with our carrier that identified the issue and taking remedial actions.

4. identified 2026-10-05 10:01 UTC

   Our carrier is seeing recovery with calls and messaging services.

5. monitoring 2026-10-05 10:02 UTC

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

6. monitoring 2026-10-05 10:05 UTC

   We are continuing to monitor for any further issues.

7. resolved 2026-10-05 10:12 UTC

   This has fully recovered and we confirm resolution.

Excerpts are shortened. Read the full incident on Aircall's status page.

Affected: Outbound Calls

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-01 16:02 UTC

   We are currently investigating an issue where some customers calling from mobile Spanish numbers are reaching an audio message.

2. identified 2026-10-01 16:15 UTC

   The issue seems to be caused by one of the local carrier routes. We are taking mitigation actions.

3. monitoring 2026-10-01 16:29 UTC

   We have mitigated the impact by changing the carrier route. We continue monitoring.

4. resolved 2026-10-01 16:37 UTC

   We can confirm this issue is fully resolved. If you continue to experience any issues, don’t hesitate to contact our Support team for further assistance.

Excerpts are shortened. Read the full incident on Aircall's status page.

Affected: Aircall Workspace (Web), Aircall Workspace (Desktop)

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-01 05:36 UTC

   We are currently investigating an issue with users being unable to login to Aircall Workspace or make and receive calls.

2. identified 2026-10-01 05:54 UTC

   This issue seems to have been caused by a spike in errors observed between 05:10 and 05:23 UTC. We are working on restoring full service stability.

3. monitoring 2026-10-01 06:33 UTC

   We have observed stable system performance for the past few minutes. Our team will continue monitoring it until we confirm full resolution.

4. resolved 2026-10-01 07:01 UTC

   We can confirm this issue is fully resolved. If you continue to experience any issues, don’t hesitate to contact our Support team for further assistance.

Excerpts are shortened. Read the full incident on Aircall's status page.

Affected: Inbound Calls, Outbound Calls

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-08 05:50 UTC

   We are currently investigating an issue with one of our partner causing no audio in inbound or outbound calls for a subset of Singapore customers.

2. investigating 2026-09-08 05:54 UTC

   We are continuing to investigate this issue.

3. identified 2026-09-08 08:05 UTC

   The issue has been identified, and we're evaluating a fix

4. monitoring 2026-09-08 08:11 UTC

   A routing change has been implemented and we are monitoring the results.

5. resolved 2026-09-08 08:51 UTC

   We have confirmation that this has been resolved

Excerpts are shortened. Read the full incident on Aircall's status page.

Affected: Call Routing & IVR, Live Monitoring, Users & Teams

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-09-03 21:59 UTC

   We are currently investigating signs of a possible service degradation. We will provide further details as soon as possible.

2. identified 2026-09-03 22:09 UTC

   This may cause sporadic impact on User status, Live Monitoring, Contacts, integrations, conversations, and other services. The issue appears to be caused by an ongoing regional incident with one of our Infrastructure Providers. We are continuously working to stabilize the system...

3. monitoring 2026-09-03 22:28 UTC

   We have been observing stabilization of the system performance for the past few minutes. Our team will continue monitoring it until full resolution is confirmed.

4. resolved 2026-09-03 22:38 UTC

   We can confirm this issue is fully resolved. If you continue to experience any issues, don’t hesitate to reach out to our Support team for further assistance.

Excerpts are shortened. Read the full incident on Aircall's status page.

Affected: Outbound Messaging (SMS/MMS)

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-01 18:43 UTC

   Our monitoring systems have detected a potential issue with MMS messages delayed delivery. We will update this page with more information when possible

2. investigating 2026-09-01 18:45 UTC

   We are continuing to investigate this issue.

3. monitoring 2026-09-01 19:02 UTC

   Thus far we have not detected any direct impact to our customers, but we will continue to monitor

4. resolved 2026-09-01 19:27 UTC

   We still have not seen any direct impact to customers, so this incident is resolved

Excerpts are shortened. Read the full incident on Aircall's status page.

Affected: Aircall Workspace (Web), Aircall Workspace (Desktop)

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-08-26 18:30 UTC

   We are currently investigating some occurrences of Users being in the On a Call status and not moving automatically to Available.

2. identified 2026-08-26 18:40 UTC

   The issue seems to be caused by a transient spike in errors that was circumscribed to the specific moment in time: 17:26 UTC. We are working on releasing the impacted users from the On a Call status.

3. monitoring 2026-08-26 19:15 UTC

   The system has been operating normally since the error spike, and the impacted Users should now be on regular User status.

4. resolved 2026-08-26 19:38 UTC

   The root cause of the issue has been found and resolved.

Excerpts are shortened. Read the full incident on Aircall's status page.

Affected: Inbound Calls

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-08-25 21:16 UTC

   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.

2. identified 2026-08-25 23:14 UTC

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

3. identified 2026-08-26 04:14 UTC

   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.

4. monitoring 2026-08-26 06:51 UTC

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

5. resolved 2026-08-26 07:48 UTC

   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.

Excerpts are shortened. Read the full incident on Aircall's status page.

Affected: Inbound Calls, Outbound Calls

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-08-11 12:08 UTC

   We are currently investigating an issue impacting some German numbers receiving "number unavailable" messages when calling.

2. identified 2026-08-11 12:28 UTC

   The issue has been identified as being caused by a specific Carrier Partner in Germany. Numbers hosted by different carriers are unaffected.

3. identified 2026-08-11 14:06 UTC

   We are observing improvements in outbound calling, despite our partner continuing to work to resolve the issue.

4. monitoring 2026-08-11 14:06 UTC

   There has been an improvement with outbound calls. We continue monitoring.

5. resolved 2026-08-12 07:15 UTC

   We can confirm this issue is fully resolved. If you continue to experience any issues, don’t hesitate to reach out to our Support team for further assistance.

Excerpts are shortened. Read the full incident on Aircall's status page.

Affected: eSIM

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-08-11 10:05 UTC

   We are currently investigating issues impacting French eSIM numbers. The issue seems to have its origin with our Carrier Partner.

2. monitoring 2026-08-11 11:50 UTC

   A fix was implemented by our Partner. We are currently monitoring the results.

3. resolved 2026-08-11 12:30 UTC

   We can confirm that the issue with the French eSIM partner has been fully resolved. We appreciate your patience and understanding while we worked with our partners to restore normal functionality.

Excerpts are shortened. Read the full incident on Aircall's status page.

Affected: AI Voice Agent (AIVA) — Inbound, AI Voice Agent (AIVA) — Outbound, AI Messaging Agent

Failure mode: AI model returned degraded, wrong or empty output (not errors or timeouts). Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-05 16:48 UTC

   We are currently investigating a possible issue with AI Agents missing connection to their configured Knowledge Base. Customers using Knowledge Base for AI Agents may experience degraded performance.

2. monitoring 2026-08-05 16:59 UTC

   The issue with AI Agent access to their configured Knowledge Bases has had a fix applied. We are no longer seeing errors and will continue to monitor

3. resolved 2026-08-05 17:16 UTC

   This is confirmed fully resolved

Excerpts are shortened. Read the full incident on Aircall's status page.

Affected: Login

Failure mode: Network, DNS, routing or connectivity failure. Root cause: Network or DNS. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-30 08:18 UTC

   We are currently investigating login issues in GB and CH.

2. identified 2026-07-30 08:29 UTC

   We are currently only seeing the issues on one ISP in CH and one in GB. We are continuing to investigate further.

3. monitoring 2026-07-30 09:04 UTC

   The issue has been identified as affecting one ISP in CH and one in GB. We recommend that customers use an alternative network if possible and contact their ISP to help resolve the issue.

4. resolved 2026-07-30 09:52 UTC

   The issue has been found to be affecting one specific ISP in CH and one in GB. We recommend that customers use an alternative network if possible and contact their ISP to help resolve the issue.

Excerpts are shortened. Read the full incident on Aircall's status page.

Affected: Analytics

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-28 14:34 UTC

   We are currently investigating an issue with Analytics high loading time on the Dashboard

2. identified 2026-07-28 14:39 UTC

   Aircall engineering is actively working on restoring the system performance

3. resolved 2026-07-28 14:47 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Aircall's status page.

Affected: Hubspot Integration, Zendesk Integration, Other Integrations

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-20 14:27 UTC

   We are currently investigating a delay in activity logging for integrations, where call/activity events are not being reflected in connected systems within the expected timeframe.

2. identified 2026-07-20 14:47 UTC

   We're actively working on improving the call logging delays

3. monitoring 2026-07-20 15:47 UTC

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

4. resolved 2026-07-20 16:25 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Aircall's status page.

Affected: Hubspot Integration, Salesforce Integration, Zendesk Integration, Other Integrations

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-17 11:45 UTC

   We are currently investigating a delay in activity logging for integrations, where call/activity events are not being reflected in connected systems within the expected timeframe. The team is actively looking into the root cause. Updates will follow as more information becomes...

2. identified 2026-07-17 12:18 UTC

   We have identified the root cause of the delay in activity logging for integrations. A fix is currently being applied. We will confirm once activities are being logged within normal timeframes and provide a final update at that point.

3. resolved 2026-07-17 14:51 UTC

   Our engineering team has resolved the issue with delayed logging to integrations.

Excerpts are shortened. Read the full incident on Aircall's status page.

Affected: Numbers Management (Purchase, Porting, Compliance)

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-07-15 15:43 UTC

   Some customers may experience issues setting or changing their registered E911 emergency location at this time. Our carrier partner has identified a problem with their system that is causing this problem and they are currently working on a fix.

2. resolved 2026-07-15 16:03 UTC

   Our partner carrier has fully resolved the issue and service is back to normal at this time

Excerpts are shortened. Read the full incident on Aircall's status page.

Affected: Aircall Workspace (Web), Aircall Workspace (Desktop), Aircall Mobile App (iOS), Aircall Mobile App (Android)

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-07-13 13:20 UTC

   We are currently investigating an issue where some Aircall users may become stuck in an active call and are unable to make new calls. Our team is actively working to identify the root cause and will provide an update as soon as more information is available.

2. identified 2026-07-13 13:32 UTC

   The issue has been identified and we are working on a fix.

3. monitoring 2026-07-13 14:26 UTC

   Our teams and partners have been working on a fix and have observed recovery. We will continue to monitor the system until the resolution is confirmed.

4. resolved 2026-07-13 14:52 UTC

   We can confirm this issue is fully resolved. If you continue to experience any issues, don’t hesitate to reach out to our Support team for further assistance.

Excerpts are shortened. Read the full incident on Aircall's status page.

Affected: Analytics

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-07-09 07:46 UTC

   We are currently investigating a performance issue that is impacting Analytics and Call History loading time

2. monitoring 2026-07-09 08:21 UTC

   We observe a return to normal performance with loading times. We keep monitoring the results.

3. resolved 2026-07-09 08:45 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Aircall's status page.

Affected: Inbound Calls

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-02 09:27 UTC

   We are seeing a recurrence of the inbound call connectivity issue with a UK Carrier that was previously reported and resolved. This is again causing sporadic retries on calls to Aircall UK numbers, and some customers may experience duplicate inbound call attempts. We have...

2. identified 2026-07-02 13:05 UTC

   We are seeing improvements but are waiting for our carrier partner to confirm that the fix is permanent.

3. identified 2026-07-02 13:10 UTC

   We are continuing to work on a fix for this issue.

4. resolved 2026-07-02 15:38 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Aircall's status page.

Affected: Inbound Calls

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-07-01 10:44 UTC

   We have identified an issue with a UK Carrier that is causing inbound call connectivity retries. This issue is sporadically impacting calls to Aircall UK numbers. Some customers may see duplicate inbound call attempts. We will provide further details as soon as downstream...

2. monitoring 2026-07-01 10:49 UTC

   The carrier partner has implemented a fix, and we are observing calls returning to the regular performance. We will continue to monitor the system until the resolution is confirmed.

3. resolved 2026-07-01 11:04 UTC

   We can confirm the issue with the UK carrier has been fully resolved. We appreciate your patience and understanding while we worked with our partners to restore normal functionality. If you continue to experience any issues, don’t hesitate to reach out to our Support team for...

Excerpts are shortened. Read the full incident on Aircall's status page.

Affected: Analytics

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-06-19 10:43 UTC

   We are currently investigating a performance issue that is impacting Analytics and Call History loading time

2. identified 2026-06-19 10:48 UTC

   The issue has been identified and a fix is being implemented

3. identified 2026-06-19 12:29 UTC

   We are observing some improvements with the loading times of Analytics Dashboards and Call history pages.

4. monitoring 2026-06-19 13:20 UTC

   We have implemented and observed a return to normal performances. We keep monitoring the results.

5. investigating 2026-06-19 14:20 UTC

   Performance is not stable again, and we are investigating.

6. identified 2026-06-19 14:34 UTC

   The issue has been identified by our 3rd party provider, and a fix is in progress.

7. monitoring 2026-06-19 17:22 UTC

   Following our 3rd party provider's work on this, we are observing that performance is back to normal. We are working with our vendor to determine the root cause and ensure we avoid a recurrence. We will continue to proactively monitor performance at this time.

8. resolved 2026-06-19 19:29 UTC

   This incident has been resolved

Excerpts are shortened. Read the full incident on Aircall's status page.

Affected: Inbound Messaging (SMS/MMS), Outbound Messaging (SMS/MMS)

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-06-10 06:52 UTC

   We are currently investigating delays affecting SMS delivery in France. Messages may take longer than usual to be delivered. We are working to identify the cause and restore normal delivery times. Further updates will follow as we learn more.

2. investigating 2026-06-10 06:58 UTC

   We are continuing to investigate this issue.

3. investigating 2026-06-10 08:13 UTC

   We are continuing to investigate the issue. Further updates to follow as we learn more.

4. investigating 2026-06-10 09:14 UTC

   We are continuing to investigate this issue. Some messages are not delivered for France and Spain numbers.

5. identified 2026-06-10 10:30 UTC

   The issue has been identified and a fix is being implemented.

6. monitoring 2026-06-10 10:42 UTC

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

7. resolved 2026-06-10 11:05 UTC

   Messages are being processed normally now.

Excerpts are shortened. Read the full incident on Aircall's status page.

Affected: Conversation Center

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-06-04 07:04 UTC

   We are currently investigating an issue with the Dashboard freezing or crashing when accessing call recordings.

2. monitoring 2026-06-04 07:22 UTC

   A fix has been implemented, and we are noticing significant improvements in Dashboard loading time.

3. resolved 2026-06-04 07:49 UTC

   The error loading recordings and insights has been fully resolved, and the Dashboard is performing normally.

Excerpts are shortened. Read the full incident on Aircall's status page.

Affected: Aircall Workspace (Web), Aircall Workspace (Desktop), Aircall Mobile App (iOS), Aircall Mobile App (Android), Aircall Chrome Extension

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-05-29 06:14 UTC

   We are currently investigating intermittent failures affecting in-call actions and buttons. Some users may experience unresponsive or unreliable controls during active calls. Our team is actively working to identify the root cause and will provide updates as the investigation...

2. monitoring 2026-05-29 06:43 UTC

   A fix has been implemented for the issue, and the app is functioning normally. We are actively monitoring the situation to ensure system stability and will provide further updates if necessary.

3. resolved 2026-05-29 06:57 UTC

   This incident has now been resolved. If you experience any further problems, please don’t hesitate to contact our support team.

Excerpts are shortened. Read the full incident on Aircall's status page.

Affected: Inbound Calls, Outbound Calls

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-05-28 19:22 UTC

   We are currently investigating an issue with Mexico phone numbers.

2. monitoring 2026-05-28 19:40 UTC

   The issue seems to be subscribed to a local carrier or local network and has returned to regular service. We continue to monitor the situation to ensure voice service remains stable.

3. resolved 2026-05-28 20:11 UTC

   Voice service for Mexico phone numbers has been fully restored. The issue was isolated to a local carrier, which has since returned to normal operation.

Excerpts are shortened. Read the full incident on Aircall's status page.

Affected: Aircall Workspace (Web), Aircall Workspace (Desktop)

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-05-19 15:48 UTC

   We are currently investigating an issue with loading conversations, impacting Aircall Workspace App

2. investigating 2026-05-19 16:16 UTC

   We continue the path of identifying the issue. We will provide further updates as soon as progress is made.

3. identified 2026-05-19 16:30 UTC

   We identified the issue. Mitigation measures are in progress.

4. monitoring 2026-05-19 16:35 UTC

   The previously applied fix has been successful, and the Workspace App is now loading conversations correctly. We will continue monitoring system performance over the upcoming moments to ensure full resolution.

5. resolved 2026-05-19 17:15 UTC

   The error loading conversations has been fully resolved, and the Workspace App is performing normally. We appreciate your patience and understanding while we worked to restore normal functionality. If you continue to experience any issues, don’t hesitate to reach out to our...

Excerpts are shortened. Read the full incident on Aircall's status page.

Affected: Inbound Calls, Aircall Workspace (Web), Outbound Calls, Aircall Workspace (Desktop), Aircall Mobile App (iOS), Aircall Mobile App (Android), Aircall Chrome Extension

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-05-15 05:15 UTC

   We are experiencing issues with Inbound/Outbound call actions on the Aircall App. Our team is working on this to fix the situation. We will be updating this status page to keep you informed of the resolution progress.

2. monitoring 2026-05-15 06:40 UTC

   We have implemented a fix, and you should now be able to action calls on the Aircall app. We will continue to monitor and provide another update as soon as more information becomes available.

3. monitoring 2026-05-15 07:12 UTC

   We are continuing to monitor for any further issues.

4. resolved 2026-05-15 07:16 UTC

   This incident is resolved. Inbound/outbound call actions on the Aircall app are fully functional.

Excerpts are shortened. Read the full incident on Aircall's status page.

Affected: Aircall Mobile App (iOS)

Failure mode: Login, tokens, certificates or credentials failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-05-01 09:32 UTC

   We are investigating reports of calls not ringing on some devices.

2. investigating 2026-05-01 09:45 UTC

   The issue seems to be circumscribed to the iOS Mobile App. We will provide further details as soon as progress is made.

3. identified 2026-05-01 10:00 UTC

   This root cause has been identified as a certificate issue with one of our communication platform providers. We're actively working on a fix.

4. monitoring 2026-05-01 10:38 UTC

   A fix has been implemented, and calls are now successfully ringing iOS Mobile App. We will continue monitoring the situation over the upcoming minutes to confirm full resolution.

5. resolved 2026-05-01 10:50 UTC

   The iOS Mobile App has remained stable during monitoring. We appreciate your patience and understanding while we worked to restore normal functionality. If you continue to experience any issues, don’t hesitate to reach out to our Support team for further assistance.

Excerpts are shortened. Read the full incident on Aircall's status page.

Affected: Inbound Calls, eSIM

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-04-29 14:35 UTC

   We are currently investigating ongoing issues impacting inbound French and Spanish Numbers.

2. investigating 2026-04-29 14:42 UTC

   We are continuing to investigate this issue.

3. identified 2026-04-29 14:55 UTC

   The issue has been identified and a fix is being implemented.

4. monitoring 2026-04-29 14:56 UTC

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

5. resolved 2026-04-29 15:16 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Aircall's status page.

Affected: Outbound Calls

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-04-21 21:26 UTC

   We have identified the cause of increased call failure rates affecting outbound calls to Chilean numbers. Our network and carrier relations teams are actively working with our partner carrier to find a resolution and restore call quality and connection rates to Chilean...

2. monitoring 2026-04-29 13:29 UTC

   We are actively working on an issue affecting outbound calls from certain Chilean phone numbers due to an unannounced policy change by a telecommunications carrier. Inbound calls to these numbers are not affected. Our team has applied routing adjustments to reduce the impact and...

3. resolved 2026-05-14 20:53 UTC

   We can confirm the outbound traffic to Chile has remained stable during monitoring. We appreciate your patience and understanding while we worked to restore normal functionality. If you continue to experience any issues, don’t hesitate to reach out to our Support team for...

Excerpts are shortened. Read the full incident on Aircall's status page.

Affected: Analytics

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-04-14 15:24 UTC

   We have identified an issue with Analytics performance, and we're implementing mitigation measures. During the mitigation attempt, Analytics data may be unavailable for a period of 15 minutes. Live Monitoring is not impacted. We will provide further updates as soon as possible.

2. monitoring 2026-04-14 15:31 UTC

   We have completed the mitigation actions, and performance levels are now stable. We continue to actively monitor Analytics' performance. Further updates will be provided as soon as progress is made.

3. resolved 2026-04-14 15:55 UTC

   Analytics' performance is fully stable and operating normally.

Excerpts are shortened. Read the full incident on Aircall's status page.

Affected: Inbound Calls, Outbound Calls

Failure mode: Network, DNS, routing or connectivity failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-03-31 10:24 UTC

   We are currently investigating reports of calls being unexpectedly disconnected for users in Germany. Some users may experience dropped calls on both inbound and outbound connections. Our engineering team is actively working to resolve the issue. We will provide updates as more...

2. identified 2026-03-31 10:38 UTC

   We applied a routing change for our downstream carrier to mitigate the issue.

3. monitoring 2026-03-31 10:57 UTC

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

4. resolved 2026-03-31 12:56 UTC

   This incident has been resolved

Excerpts are shortened. Read the full incident on Aircall's status page.

Affected: Inbound Messaging (SMS/MMS)

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-02-13 20:32 UTC

   We are presently investigating an issue with SMS and MMS delivery with one of our carriers. Some customers may experience delivery delays or MMS messages not arriving.

2. monitoring 2026-02-13 21:11 UTC

   We are no longer seeing SMS and MMS errors at this time but will continue to monitor the situation

3. resolved 2026-02-13 21:58 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Aircall's status page.

Affected: Aircall Workspace (Desktop)

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-02-04 15:55 UTC

   We are currently investigating high latency when loading Aircall. We will be providing updates as progress is made.

2. identified 2026-02-04 16:15 UTC

   We are actively implementing mitigation measures to improve system performance. We will be providing updates as progress is made.

3. monitoring 2026-02-04 18:00 UTC

   We have been observing improvements in the system performance after our mitigation attempts. Customers previously experiencing loading issues should reload the Aircall App (F5 on Windows and Ctrl+R on MacOS) in order to ensure operation with the latest updates. We continue to...

4. resolved 2026-02-04 19:54 UTC

   System performance has remained stable during monitoring. We appreciate your patience and understanding while we worked to restore normal functionality. If you continue to experience any issues, don’t hesitate to reach out to our Support team for further assistance.

Excerpts are shortened. Read the full incident on Aircall's status page.

Affected: Inbound Calls, Outbound Calls

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-01-22 11:43 UTC

   We are observing a drop in Iberian call traffic caused by issues that are external to Aircall. It seems that several telco providers, particularly in Spain, are experiencing issues, as can be seen on https://downdetector.es/. Although this is external to Aircall, our engineering...

2. resolved 2026-01-22 12:30 UTC

   We are observing a recovery of traffic in Spain to regular levels. Therefore, we believe that local telcos have been able to recover their network and fully resolve the situation.

Excerpts are shortened. Read the full incident on Aircall's status page.

Affected: Login

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-01-19 07:48 UTC

   We are currently investigating issues with logging in Aircall.

2. monitoring 2026-01-19 08:07 UTC

   The issue has been identified as impacting the login process of both Aircall Apps and Dashboard, and a fix has been deployed. We are already observing some successful login attempts and will continue to monitor the situation until full system stability is achieved.

3. resolved 2026-01-19 08:39 UTC

   System performance has remained stable during monitoring. We appreciate your patience and understanding while we worked to restore normal functionality. If you continue to experience any issues, don’t hesitate to reach out to our Support team for further assistance.

Excerpts are shortened. Read the full incident on Aircall's status page.

Affected: Login

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-01-15 08:31 UTC

   We are currently exploring an issue where users are unable to log in, and a "Something went wrong" error message is displayed.

2. identified 2026-01-15 08:32 UTC

   The root cause has been identified and we are applying a fix

3. monitoring 2026-01-15 08:32 UTC

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

4. resolved 2026-01-15 08:33 UTC

   This incident has been resolved. We have observed temporary instability impacting login performance from 08:12 to 08:20 UTC.

Excerpts are shortened. Read the full incident on Aircall's status page.

Affected: Inbound Calls, Outbound Calls

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2025-12-22 07:56 UTC

   We are investigating reports of some calls dropping and some facing quality issues

2. identified 2025-12-22 08:41 UTC

   We have identified the issue as coming from one of our Telco providers.

3. monitoring 2025-12-22 09:18 UTC

   Our telco partner has advised that the issue should be resolved. We are monitoring the results

4. resolved 2025-12-22 09:45 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Aircall's status page.

Affected: API & Webhooks

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-12-17 10:27 UTC

   We are investigating an error on our public API returning 500 error. The issue has been identified and we are working on a corrective release.

2. identified 2025-12-17 10:28 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2025-12-17 10:48 UTC

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

4. resolved 2025-12-17 11:00 UTC

   Our public API is now working as expected, this incident has been resolved.

Excerpts are shortened. Read the full incident on Aircall's status page.

Affected: Aircall Support Portal (Help Center)

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2025-12-05 08:57 UTC

   We are experiencing an issue with our Support Portal (support.aircall.io). This issue appears to be related to a network infrastructure incident affecting our portal's provider. In case you need immediate support from Aircall, please call us at +18882406923 or +33176360695.

2. identified 2025-12-05 09:08 UTC

   This is a confirmed global incident experienced by a major network infrastructure provider; it impacts multiple websites and platforms. We are in close contact with the provider, and we are internally assessing possible mitigation measures. Ticket Submission to Aircall Support...

3. monitoring 2025-12-05 09:14 UTC

   A fix has been implemented by the provider, and the Aircall Support Portal is now operational. We continue to monitor the situation.

4. resolved 2025-12-05 09:26 UTC

   The Support Portal and all its Support channels are operational and stable.

Excerpts are shortened. Read the full incident on Aircall's status page.

Affected: Inbound Calls

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-11-13 13:59 UTC

   We are currently investigating an issue with the following symptoms: The agent's availability is not updated Inbound calls are not ringing on agents, despite agents being available

2. monitoring 2025-11-13 14:11 UTC

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

3. monitoring 2025-11-13 14:24 UTC

   System stability is improving when synchronizing the agent status, which means that calls will ring according to the agent status.

4. monitoring 2025-11-13 15:58 UTC

   We are continuing to monitor for any further issues.

5. resolved 2025-11-13 16:23 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Aircall's status page.

Affected: Salesforce Integration

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2025-11-10 16:04 UTC

   We have identified an issue preventing some calls from logging in Salesforce, and we're actively working on a fix. We will provide further updates as soon as progress is made.

2. monitoring 2025-11-10 16:11 UTC

   We have implemented a fix, and we observe positive results from our tests. We continue to monitor the service performance.

3. resolved 2025-11-10 16:38 UTC

   System performance has remained stable during monitoring. We appreciate your patience and understanding while we worked to restore normal functionality. If you continue to experience any issues, don’t hesitate to reach out to our Support team for further assistance.

Excerpts are shortened. Read the full incident on Aircall's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-10-31 08:50 UTC

   We are investigating delays in processing changes to user status. Customers may see the correct status in the App, but the backend is processing the change with a delay.

2. identified 2025-10-31 08:58 UTC

   The issue has been identified, and we're actively working on the mitigation.

3. monitoring 2025-10-31 09:10 UTC

   We can observe signs of recovery. We continue to monitor the situation, and we will provide further information as soon as further developments are made.

4. resolved 2025-10-31 09:19 UTC

   System performance has remained stable during monitoring. We appreciate your patience and understanding while we worked to restore normal functionality. If you continue to experience any issues, don’t hesitate to reach out to our Support team for further assistance.

Excerpts are shortened. Read the full incident on Aircall's status page.

Affected: Aircall Mobile App (iOS)

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-10-27 15:40 UTC

   We are currently investigating an issue where calls are dropping from mobile applications.

2. investigating 2025-10-27 15:47 UTC

   We are currently investigating an issue where calls (inbound and outbound) are dropping from mobile applications. Calls from the desktop and web apps are not impacted.

3. investigating 2025-10-27 15:54 UTC

   We are currently investigating an issue where a subset of calls (inbound and outbound) is dropping from the applications (mobile, legacy, and workspace).

4. monitoring 2025-10-27 16:26 UTC

   We are in contact with one of our communication platform providers and have seen stable service for the past minutes. We keep on monitoring the results.

5. resolved 2025-10-27 16:52 UTC

   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.

Excerpts are shortened. Read the full incident on Aircall's status page.

Affected: Inbound Calls, Outbound Calls

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2025-10-20 07:07 UTC

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

2. identified 2025-10-20 07:17 UTC

   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.

3. identified 2025-10-20 07:42 UTC

   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.

4. identified 2025-10-20 08:34 UTC

   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.

5. identified 2025-10-20 09:01 UTC

   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.

6. identified 2025-10-20 09:58 UTC

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

7. identified 2025-10-20 10:37 UTC

   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.

8. monitoring 2025-10-20 11:42 UTC

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

9. monitoring 2025-10-20 12:36 UTC

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

10. monitoring 2025-10-20 14:13 UTC

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

11. identified 2025-10-20 15:07 UTC

    We continue to monitor the system and we can observe some sporadic issues with Calls and Call Controls.

12. identified 2025-10-20 16:37 UTC

    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.

13. identified 2025-10-20 17:25 UTC

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

14. identified 2025-10-20 19:10 UTC

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

15. monitoring 2025-10-20 20:09 UTC

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

16. resolved 2025-10-21 06:46 UTC

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

Excerpts are shortened. Read the full incident on Aircall's status page.