- Detected by Pingoru
- Aug 11, 2026, 12:08 PM UTC
- Resolved
- Aug 12, 2026, 07:15 AM UTC
- Duration
- 19h 6m
Affected: Inbound CallsOutbound Calls
Timeline · 5 updates
-
investigating Aug 11, 2026, 12:08 PM UTC
We are currently investigating an issue impacting some German numbers receiving "number unavailable" messages when calling.
-
identified Aug 11, 2026, 12:28 PM UTC
The issue has been identified as being caused by a specific Carrier Partner in Germany. Numbers hosted by different carriers are unaffected.
-
identified Aug 11, 2026, 02:06 PM UTC
We are observing improvements in outbound calling, despite our partner continuing to work to resolve the issue.
-
monitoring Aug 11, 2026, 02:06 PM UTC
There has been an improvement with outbound calls. We continue monitoring.
-
resolved Aug 12, 2026, 07:15 AM 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.
Read the full incident report →
- Detected by Pingoru
- Aug 11, 2026, 10:05 AM UTC
- Resolved
- Aug 11, 2026, 12:30 PM UTC
- Duration
- 2h 25m
Affected: eSIM
Timeline · 3 updates
-
investigating Aug 11, 2026, 10:05 AM UTC
We are currently investigating issues impacting French eSIM numbers. The issue seems to have its origin with our Carrier Partner.
-
monitoring Aug 11, 2026, 11:50 AM UTC
A fix was implemented by our Partner. We are currently monitoring the results.
-
resolved Aug 11, 2026, 12:30 PM 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.
Read the full incident report →
- Detected by Pingoru
- Aug 05, 2026, 04:48 PM UTC
- Resolved
- Aug 05, 2026, 05:16 PM UTC
- Duration
- 27m
Affected: AI Voice Agent (AIVA) — InboundAI Voice Agent (AIVA) — OutboundAI Messaging Agent
Timeline · 3 updates
-
investigating Aug 05, 2026, 04:48 PM 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.
-
monitoring Aug 05, 2026, 04:59 PM 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
-
resolved Aug 05, 2026, 05:16 PM UTC
This is confirmed fully resolved
Read the full incident report →
- Detected by Pingoru
- Jul 30, 2026, 08:18 AM UTC
- Resolved
- Jul 30, 2026, 09:52 AM UTC
- Duration
- 1h 33m
Affected: Login
Timeline · 4 updates
-
investigating Jul 30, 2026, 08:18 AM UTC
We are currently investigating login issues in GB and CH.
-
identified Jul 30, 2026, 08:29 AM UTC
We are currently only seeing the issues on one ISP in CH and one in GB. We are continuing to investigate further.
-
monitoring Jul 30, 2026, 09:04 AM 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.
-
resolved Jul 30, 2026, 09:52 AM 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.
Read the full incident report →
- Detected by Pingoru
- Jul 28, 2026, 02:34 PM UTC
- Resolved
- Jul 28, 2026, 02:47 PM UTC
- Duration
- 12m
Affected: Analytics
Timeline · 3 updates
-
investigating Jul 28, 2026, 02:34 PM UTC
We are currently investigating an issue with Analytics high loading time on the Dashboard
-
identified Jul 28, 2026, 02:39 PM UTC
Aircall engineering is actively working on restoring the system performance
-
resolved Jul 28, 2026, 02:47 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 20, 2026, 02:27 PM UTC
- Resolved
- Jul 20, 2026, 04:25 PM UTC
- Duration
- 1h 58m
Affected: Hubspot IntegrationZendesk IntegrationOther Integrations
Timeline · 4 updates
-
investigating Jul 20, 2026, 02:27 PM 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.
-
identified Jul 20, 2026, 02:47 PM UTC
We're actively working on improving the call logging delays
-
monitoring Jul 20, 2026, 03:47 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Jul 20, 2026, 04:25 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 15, 2026, 03:43 PM UTC
- Resolved
- Jul 15, 2026, 04:03 PM UTC
- Duration
- 20m
Affected: Numbers Management (Purchase, Porting, Compliance)
Timeline · 2 updates
-
identified Jul 15, 2026, 03:43 PM 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.
-
resolved Jul 15, 2026, 04:03 PM UTC
Our partner carrier has fully resolved the issue and service is back to normal at this time
Read the full incident report →
- Detected by Pingoru
- Jul 13, 2026, 01:20 PM UTC
- Resolved
- Jul 13, 2026, 02:52 PM UTC
- Duration
- 1h 31m
Affected: Aircall Workspace (Desktop)Aircall Mobile App (iOS)Aircall Mobile App (Android)Aircall Workspace (Web)
Timeline · 4 updates
-
investigating Jul 13, 2026, 01:20 PM 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.
-
identified Jul 13, 2026, 01:32 PM UTC
The issue has been identified and we are working on a fix.
-
monitoring Jul 13, 2026, 02:26 PM 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.
-
resolved Jul 13, 2026, 02:52 PM 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.
Read the full incident report →
- Detected by Pingoru
- Jul 09, 2026, 07:46 AM UTC
- Resolved
- Jul 09, 2026, 08:45 AM UTC
- Duration
- 58m
Affected: Analytics
Timeline · 3 updates
-
investigating Jul 09, 2026, 07:46 AM UTC
We are currently investigating a performance issue that is impacting Analytics and Call History loading time
-
monitoring Jul 09, 2026, 08:21 AM UTC
We observe a return to normal performance with loading times. We keep monitoring the results.
-
resolved Jul 09, 2026, 08:45 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 02, 2026, 09:27 AM UTC
- Resolved
- Jul 02, 2026, 03:38 PM UTC
- Duration
- 6h 10m
Affected: Inbound Calls
Timeline · 4 updates
-
investigating Jul 02, 2026, 09:27 AM 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 re-engaged with the carrier and are working to confirm the root cause and prevent further recurrence. We will share updates as soon as we have more information.
-
identified Jul 02, 2026, 01:05 PM UTC
We are seeing improvements but are waiting for our carrier partner to confirm that the fix is permanent.
-
identified Jul 02, 2026, 01:10 PM UTC
We are continuing to work on a fix for this issue.
-
resolved Jul 02, 2026, 03:38 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 19, 2026, 10:43 AM UTC
- Resolved
- Jun 19, 2026, 07:29 PM UTC
- Duration
- 8h 46m
Affected: Analytics
Timeline · 8 updates
-
investigating Jun 19, 2026, 10:43 AM UTC
We are currently investigating a performance issue that is impacting Analytics and Call History loading time
-
identified Jun 19, 2026, 10:48 AM UTC
The issue has been identified and a fix is being implemented
-
identified Jun 19, 2026, 12:29 PM UTC
We are observing some improvements with the loading times of Analytics Dashboards and Call history pages.
-
monitoring Jun 19, 2026, 01:20 PM UTC
We have implemented and observed a return to normal performances. We keep monitoring the results.
-
investigating Jun 19, 2026, 02:20 PM UTC
Performance is not stable again, and we are investigating.
-
identified Jun 19, 2026, 02:34 PM UTC
The issue has been identified by our 3rd party provider, and a fix is in progress.
-
monitoring Jun 19, 2026, 05:22 PM 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.
-
resolved Jun 19, 2026, 07:29 PM UTC
This incident has been resolved
Read the full incident report →
- Detected by Pingoru
- Jun 10, 2026, 06:52 AM UTC
- Resolved
- Jun 10, 2026, 11:05 AM UTC
- Duration
- 4h 12m
Affected: Inbound Messaging (SMS/MMS)Outbound Messaging (SMS/MMS)
Timeline · 7 updates
-
investigating Jun 10, 2026, 06:52 AM 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.
-
investigating Jun 10, 2026, 06:58 AM UTC
We are continuing to investigate this issue.
-
investigating Jun 10, 2026, 08:13 AM UTC
We are continuing to investigate the issue. Further updates to follow as we learn more.
-
investigating Jun 10, 2026, 09:14 AM UTC
We are continuing to investigate this issue. Some messages are not delivered for France and Spain numbers.
-
identified Jun 10, 2026, 10:30 AM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Jun 10, 2026, 10:42 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Jun 10, 2026, 11:05 AM UTC
Messages are being processed normally now.
Read the full incident report →
- Detected by Pingoru
- Jun 04, 2026, 07:04 AM UTC
- Resolved
- Jun 04, 2026, 07:49 AM UTC
- Duration
- 44m
Affected: Conversation Center
Timeline · 3 updates
-
investigating Jun 04, 2026, 07:04 AM UTC
We are currently investigating an issue with the Dashboard freezing or crashing when accessing call recordings.
-
monitoring Jun 04, 2026, 07:22 AM UTC
A fix has been implemented, and we are noticing significant improvements in Dashboard loading time.
-
resolved Jun 04, 2026, 07:49 AM UTC
The error loading recordings and insights has been fully resolved, and the Dashboard is performing normally.
Read the full incident report →
- Detected by Pingoru
- May 29, 2026, 06:14 AM UTC
- Resolved
- May 29, 2026, 06:57 AM UTC
- Duration
- 42m
Affected: Aircall Workspace (Desktop)Aircall Mobile App (iOS)Aircall Mobile App (Android)Aircall Chrome ExtensionAircall Workspace (Web)
Timeline · 3 updates
-
investigating May 29, 2026, 06:14 AM 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 progresses.
-
monitoring May 29, 2026, 06:43 AM 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.
-
resolved May 29, 2026, 06:57 AM UTC
This incident has now been resolved. If you experience any further problems, please don’t hesitate to contact our support team.
Read the full incident report →
- Detected by Pingoru
- May 28, 2026, 07:22 PM UTC
- Resolved
- May 28, 2026, 08:11 PM UTC
- Duration
- 48m
Affected: Inbound CallsOutbound Calls
Timeline · 3 updates
-
investigating May 28, 2026, 07:22 PM UTC
We are currently investigating an issue with Mexico phone numbers.
-
monitoring May 28, 2026, 07:40 PM 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.
-
resolved May 28, 2026, 08:11 PM 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.
Read the full incident report →
- Detected by Pingoru
- May 19, 2026, 03:48 PM UTC
- Resolved
- May 19, 2026, 05:15 PM UTC
- Duration
- 1h 26m
Affected: Aircall Workspace (Desktop)Aircall Workspace (Web)
Timeline · 5 updates
-
investigating May 19, 2026, 03:48 PM UTC
We are currently investigating an issue with loading conversations, impacting Aircall Workspace App
-
investigating May 19, 2026, 04:16 PM UTC
We continue the path of identifying the issue. We will provide further updates as soon as progress is made.
-
identified May 19, 2026, 04:30 PM UTC
We identified the issue. Mitigation measures are in progress.
-
monitoring May 19, 2026, 04:35 PM 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.
-
resolved May 19, 2026, 05:15 PM 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 Support team for further assistance.
Read the full incident report →
- Detected by Pingoru
- May 15, 2026, 05:15 AM UTC
- Resolved
- May 15, 2026, 07:16 AM UTC
- Duration
- 2h 1m
Affected: Inbound CallsAircall Workspace (Desktop)Outbound CallsAircall Mobile App (iOS)Aircall Mobile App (Android)Aircall Chrome ExtensionAircall Workspace (Web)
Timeline · 4 updates
-
investigating May 15, 2026, 05:15 AM 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.
-
monitoring May 15, 2026, 06:40 AM 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.
-
monitoring May 15, 2026, 07:12 AM UTC
We are continuing to monitor for any further issues.
-
resolved May 15, 2026, 07:16 AM UTC
This incident is resolved. Inbound/outbound call actions on the Aircall app are fully functional.
Read the full incident report →
- Detected by Pingoru
- May 01, 2026, 09:32 AM UTC
- Resolved
- May 01, 2026, 10:50 AM UTC
- Duration
- 1h 18m
Affected: Aircall Workspace (Desktop)Aircall Mobile App (iOS)
Timeline · 5 updates
-
investigating May 01, 2026, 09:32 AM UTC
We are investigating reports of calls not ringing on some devices.
-
investigating May 01, 2026, 09:45 AM UTC
The issue seems to be circumscribed to the iOS Mobile App. We will provide further details as soon as progress is made.
-
identified May 01, 2026, 10:00 AM 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.
-
monitoring May 01, 2026, 10:38 AM 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.
-
resolved May 01, 2026, 10:50 AM 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.
Read the full incident report →
- Detected by Pingoru
- Apr 29, 2026, 02:35 PM UTC
- Resolved
- Apr 29, 2026, 03:16 PM UTC
- Duration
- 41m
Affected: Inbound CallseSIM
Timeline · 5 updates
-
investigating Apr 29, 2026, 02:35 PM UTC
We are currently investigating ongoing issues impacting inbound French Numbers.
-
investigating Apr 29, 2026, 02:42 PM UTC
We are continuing to investigate this issue.
-
identified Apr 29, 2026, 02:55 PM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Apr 29, 2026, 02:56 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Apr 29, 2026, 03:16 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 21, 2026, 09:26 PM UTC
- Resolved
- May 14, 2026, 08:53 PM UTC
- Duration
- 22d 23h
Affected: Outbound Calls
Timeline · 3 updates
-
identified Apr 21, 2026, 09:26 PM 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 destinations as quickly as possible.
-
monitoring Apr 29, 2026, 01:29 PM 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 is working toward a permanent resolution. If you are experiencing outbound call failures from Chilean numbers, please contact our support team at https://support.aircall.io/ or your account manager to discuss options and any available immediate mitigations.
-
resolved May 14, 2026, 08:53 PM 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 further assistance.
Read the full incident report →
- Detected by Pingoru
- Apr 14, 2026, 03:24 PM UTC
- Resolved
- Apr 14, 2026, 03:55 PM UTC
- Duration
- 31m
Affected: Analytics
Timeline · 3 updates
-
identified Apr 14, 2026, 03:24 PM 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.
-
monitoring Apr 14, 2026, 03:31 PM 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.
-
resolved Apr 14, 2026, 03:55 PM UTC
Analytics' performance is fully stable and operating normally.
Read the full incident report →
- Detected by Pingoru
- Mar 31, 2026, 10:24 AM UTC
- Resolved
- Mar 31, 2026, 12:56 PM UTC
- Duration
- 2h 32m
Affected: Inbound CallsOutbound Calls
Timeline · 4 updates
-
investigating Mar 31, 2026, 10:24 AM 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 information becomes available.
-
identified Mar 31, 2026, 10:38 AM UTC
We applied a routing change for our downstream carrier to mitigate the issue.
-
monitoring Mar 31, 2026, 10:57 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Mar 31, 2026, 12:56 PM UTC
This incident has been resolved
Read the full incident report →
- Detected by Pingoru
- Feb 13, 2026, 08:32 PM UTC
- Resolved
- Feb 13, 2026, 09:58 PM UTC
- Duration
- 1h 25m
Affected: Inbound Messaging (SMS/MMS)
Timeline · 3 updates
-
investigating Feb 13, 2026, 08:32 PM 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.
-
monitoring Feb 13, 2026, 09:11 PM UTC
We are no longer seeing SMS and MMS errors at this time but will continue to monitor the situation
-
resolved Feb 13, 2026, 09:58 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Feb 04, 2026, 03:55 PM UTC
- Resolved
- Feb 04, 2026, 07:54 PM UTC
- Duration
- 3h 58m
Affected: Aircall Workspace (Desktop)Aircall Desktop App (Legacy)
Timeline · 4 updates
-
investigating Feb 04, 2026, 03:55 PM UTC
We are currently investigating high latency when loading Aircall. We will be providing updates as progress is made.
-
identified Feb 04, 2026, 04:15 PM UTC
We are actively implementing mitigation measures to improve system performance. We will be providing updates as progress is made.
-
monitoring Feb 04, 2026, 06:00 PM 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 monitor the system performance to ensure the root cause has been permanently tackled.
-
resolved Feb 04, 2026, 07:54 PM 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.
Read the full incident report →
- Detected by Pingoru
- Jan 22, 2026, 11:43 AM UTC
- Resolved
- Jan 22, 2026, 12:30 PM UTC
- Duration
- 46m
Affected: Inbound CallsOutbound Calls
Timeline · 2 updates
-
identified Jan 22, 2026, 11:43 AM 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 team is closely monitoring the situation.
-
resolved Jan 22, 2026, 12:30 PM 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.
Read the full incident report →
