- Detected by Pingoru
- Oct 16, 2026, 06:54 AM UTC
- Resolved
- Oct 16, 2026, 08:45 AM UTC
- Duration
- 1h 50m
Affected: Europe & Middle East (EMEA) ([EMEA] Rainbow Core Services)Europe & Middle East (EMEA) ([EMEA] Rainbow Hub Voice Services)Europe & Middle East (EMEA) ([EMEA] Rainbow Conferencing)Europe & Middle East (EMEA) ([EMEA] Rainbow Media Relays)
Timeline · 3 updates
-
investigating Oct 16, 2026, 06:54 AM UTC
We are currently investigating an issue affecting calls involving Myriad devices using the Alphalink and Telenet SIP trunk. Our technical teams are actively working to identify the problem and restore normal service as quickly as possible. We will provide further updates as soon as more information becomes available.
-
monitoring Oct 16, 2026, 07:33 AM UTC
Our technical teams have identified a potential cause and have taken actions to restore the affected services. We are starting to see signs of recovery, but the service has not yet been fully restored. Our teams remain actively engaged, and we will provide further updates as the situation evolves.
-
resolved Oct 16, 2026, 08:45 AM UTC
The issue has been resolved, and normal service has been fully restored.
Read the full incident report →
- Detected by Pingoru
- Oct 02, 2026, 01:22 PM UTC
- Resolved
- Oct 02, 2026, 11:08 PM UTC
- Duration
- 9h 45m
Affected: Europe & Middle East (EMEA) ([EMEA] Rainbow Core Services)Europe & Middle East (EMEA) ([EMEA] Rainbow Hub Voice Services)Europe & Middle East (EMEA) ([EMEA] Rainbow Conferencing)Europe & Middle East (EMEA) ([EMEA] Rainbow Media Relays)
Timeline · 4 updates
-
investigating Oct 02, 2026, 01:22 PM UTC
We are currently experiencing a network issue involving our service provider, affecting some users in France connecting to Rainbow through the Orange network. We will share further updates as more information becomes available.
-
identified Oct 02, 2026, 01:50 PM UTC
OVHcloud has confirmed a network connectivity issue between Orange and OVHcloud. Their teams are working to restore normal connectivity. Users in France accessing Rainbow through an Orange internet connection may experience slow performance or intermittent access issues. You can follow the provider’s updates here: We will share further updates as more information becomes available.
-
monitoring Oct 02, 2026, 02:52 PM UTC
OVHcloud has confirmed that connectivity was fully restored on October 2, 2026, at 16:40 CEST (14:40 UTC). We are also monitoring Rainbow services to confirm continued stability. Further details are available on [OVHcloud’s status page](https://network.status-ovhcloud.com/incidents/jqxcrgr138b4).
-
resolved Oct 02, 2026, 11:08 PM UTC
Following the resolution of the network incident reported by OVHcloud, this incident is now resolved on our side as well. Further details are available on [OVHcloud’s status page](https://network.status-ovhcloud.com/incidents/jqxcrgr138b4).
Read the full incident report →
- Detected by Pingoru
- Sep 25, 2026, 04:27 PM UTC
- Resolved
- Sep 30, 2026, 01:55 PM UTC
- Duration
- 4d 21h
Affected: Europe & Middle East (EMEA) ([EMEA] Rainbow Hub Voice Services)
Timeline · 5 updates
-
investigating Sep 25, 2026, 04:27 PM UTC
$19
-
identified Sep 28, 2026, 06:56 AM UTC
Our teams have made progress on the issue affecting some Rainbow Hub customers. The issue is linked to a recent platform change affecting how transfers are handled. A fix has been developed and is being validated. We will share the deployment schedule as soon as validation is complete. Until the fix is deployed, we recommend: * using blind (direct) transfer instead of attended transfer, or * answering and transferring Call Queue calls from the Rainbow application on a PC. Our teams remain fully engaged to resolve this issue as quickly as possible.
-
identified Sep 29, 2026, 01:08 PM UTC
**Scheduled Deployment Update** Final validation testing has been successfully completed. A fix for the **Rainbow Hub Call Queue attended transfer issue** is scheduled for deployment in **EMEA today, September 29, at 21:00 CEST**. During the deployment window, a service interruption of up to **10 minutes** may occur. The service will be closely monitored following deployment, and we will provide a further update once the rollout has been completed. Thank you for your patience and understanding.
-
monitoring Sep 30, 2026, 09:44 AM UTC
**Monitoring** The fix for the Rainbow Hub Call Queue attended transfer issue was deployed yesterday at **21:00 CET**, as planned. We are currently monitoring the service and the fix is performing as expected.
-
resolved Sep 30, 2026, 01:55 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Sep 14, 2026, 01:46 PM UTC
- Resolved
- Sep 14, 2026, 04:41 PM UTC
- Duration
- 2h 54m
Affected: Germany (DE) ([DE] Rainbow Conferencing)
Timeline · 4 updates
-
investigating Sep 14, 2026, 01:46 PM UTC
Some users in Germany may be unable to start or join Bubble calls. Our technical teams are currently investigating the issue. We will provide an update as soon as more information is available.
-
identified Sep 14, 2026, 02:24 PM UTC
Our investigation has identified intermittent network instability within the underlying infrastructure. As a result, some users may experience difficulties accessing certain Rainbow services, including starting or joining Bubble calls. The issue has been escalated to our hosting provider, and our technical teams are continuing to monitor the situation. We will provide further updates as soon as more information becomes available.
-
monitoring Sep 14, 2026, 02:33 PM UTC
A configuration change has been applied to mitigate the issue, and the affected services are currently stable. Our technical teams are monitoring the situation while the underlying network issue remains under investigation with our hosting provider.
-
resolved Sep 14, 2026, 04:41 PM UTC
The situation has remained stable following the configuration change, and the affected services are operating normally.
Read the full incident report →
- Detected by Pingoru
- Aug 01, 2026, 09:55 PM UTC
- Resolved
- Aug 01, 2026, 09:55 PM UTC
- Duration
- —
Timeline · 1 update
Read the full incident report →
- Detected by Pingoru
- Jul 29, 2026, 08:35 AM UTC
- Resolved
- Aug 07, 2026, 03:01 PM UTC
- Duration
- 9d 6h
Affected: Europe & Middle East (EMEA) ([EMEA] Rainbow Hub Voice Services)
Timeline · 6 updates
-
investigating Jul 29, 2026, 08:35 AM UTC
We are currently investigating this incident.
-
investigating Jul 29, 2026, 02:21 PM UTC
Our teams continue to actively investigate the reported audio quality issues. Progress has been made in the analysis and targeted studies are performed to validate findings and determine the underlying cause. While a root cause has not yet been confirmed, the investigation is advancing and remains a top priority. We continue to monitor the platform closely and will share further updates as more information becomes available. Thank you for your continued patience and understanding.
-
investigating Jul 30, 2026, 08:22 AM UTC
Our teams are continuing to investigate the incident and have narrowed down the potential root cause. We are making progress in our analysis and expect to advance further shortly. We will provide additional updates as soon as more information becomes available. Thank you for your patience.
-
identified Jul 30, 2026, 03:58 PM UTC
We have identified the faulty workflow responsible for the audio issues experienced by affected end users. Our investigation has determined that, under several network conditions, the media relay tunnel establishment between the application software and the core media component does not complete as expected. As a result, audio is available only for a few seconds before being interrupted. The root cause has been identified, and our engineering teams are currently working on a solution. We will provide further updates as progress is made and a remediation plan is finalized. We apologize for the inconvenience and appreciate your patience while we work to resolve this issue.
-
identified Jul 31, 2026, 03:11 PM UTC
We have identified the solution and are currently working on its implementation. Testing activities are scheduled in the coming days to validate the fix and ensure service stability. Our objective is to deploy the solution to production by the middle of next week, following the successful completion of regression testing. We will continue to monitor progress closely and provide further updates as milestones are reached. We appreciate your continued partnership and will keep you informed of further developments.
-
monitoring Aug 05, 2026, 03:14 PM UTC
We are pleased to confirm that the new Rainbow version containing the fix is now available. The rollout is being progressively deployed and will reach all customers within the next 24 hours, in accordance with the update notification communicated in our service announcement. We are closely monitoring the deployment and will keep you informed of any significant developments.
Read the full incident report →
- Detected by Pingoru
- Jul 29, 2026, 08:35 AM UTC
- Resolved
- Jul 29, 2026, 08:35 AM UTC
- Duration
- —
Timeline · 1 update
Read the full incident report →
- Detected by Pingoru
- Jul 21, 2026, 06:00 AM UTC
- Resolved
- Jul 21, 2026, 12:53 PM UTC
- Duration
- 6h 53m
Affected: Europe & Middle East (EMEA) ([EMEA] Rainbow Hub Voice Services)
Timeline · 3 updates
-
investigating Jul 21, 2026, 06:00 AM UTC
We are currently investigating an issue affecting some Rainbow Hub customers using Alphalink SIP trunks. Calls routed through Call Queues may connect without audio or without a ringback tone. Direct calls appear to be working normally. As a temporary workaround, customers can replace the affected Call Queue with a standard Hunt Group. Our technical teams are actively investigating the issue. Further updates will be provided as soon as more information is available.
-
monitoring Jul 21, 2026, 08:00 AM UTC
The issue is no longer being observed. Our technical teams are continuing to monitor the service to confirm its stability.
-
resolved Jul 21, 2026, 12:53 PM UTC
The issue has been resolved. A configuration inconsistency introduced during the Call Queue migration to the new 3AZ infrastructure was identified and corrected without service disruption. The correction has been applied across the affected infrastructure, and Call Queue services are now operating normally.
Read the full incident report →
- Detected by Pingoru
- Jul 21, 2026, 06:00 AM UTC
- Resolved
- Jul 21, 2026, 06:00 AM UTC
- Duration
- —
Timeline · 1 update
Read the full incident report →
- Detected by Pingoru
- Jul 20, 2026, 06:00 PM UTC
- Resolved
- Jul 20, 2026, 06:00 PM UTC
- Duration
- —
Timeline · 1 update
-
resolved Jul 20, 2026, 06:00 PM UTC
Type: Maintenance Duration: 30 minutes Affected Components: [EMEA] Rainbow Hub Voice Services Jul 16, 13:41:45 GMT+0 - Identified - As part of the ongoing Rainbow migration to the new 3AZ infrastructure, ALE will perform a migration of Call Queue components. This operation is planned on July 20 at 20:00 CEST and is expected to impact Rainbow Call Queue services for up to 30 minutes. During this operation, customers using Call Queues will experience temporary service interruptions. Our teams will closely monitor the platform throughout the operation. 🚨Reminder: Please ensure that the latest Rainbow Network Requirements are implemented in your firewall and security policies to avoid connectivity issues during the ongoing migration. Rainbow Network Requirements: Jul 20, 18:00:01 GMT+0 - Identified - Maintenance is now in progress Jul 20, 18:30:00 GMT+0 - Completed - Maintenance has completed successfully
Read the full incident report →
- Detected by Pingoru
- Jul 19, 2026, 06:00 AM UTC
- Resolved
- Jul 19, 2026, 06:00 AM UTC
- Duration
- —
Timeline · 1 update
-
resolved Jul 19, 2026, 06:00 AM UTC
Type: Maintenance Duration: 16 hours and 7 minutes Affected Components: [WW] Rainbow Hybrid PBX Telephony Jul 16, 09:32:36 GMT+0 - Identified - As part of the ongoing Rainbow migration to the new 3AZ infrastructure, ALE will start the progressive migration of Hybrid Telephony connectivity components from July 19. After this operation, customer PBX new connections will be progressively re-established to the new 3AZ infrastructure. The operation is designed to be transparent for customers. No major service impact is expected; however, short telephony re-registrations may occur for some users during specific migration steps. Our teams will closely monitor the platform throughout the operation. 🚨Customers are reminded to ensure that the latest Rainbow Network Requirements are implemented in their firewall and security policies: Jul 19, 06:00:01 GMT+0 - Identified - Maintenance is now in progress Jul 19, 22:06:35 GMT+0 - Completed - Maintenance has completed successfully.
Read the full incident report →
- Detected by Pingoru
- Jul 01, 2026, 06:03 AM UTC
- Resolved
- Jul 01, 2026, 07:09 AM UTC
- Duration
- 1h 5m
Affected: Germany (DE) ([DE] Rainbow Conferencing)Asia-Pacific (APAC) ([APAC] Rainbow Conferencing)Australia-New Zealand (ANZ) ([ANZ] Rainbow Conferencing)
Timeline · 4 updates
-
investigating Jul 01, 2026, 06:03 AM UTC
We are currently investigating this incident.
-
identified Jul 01, 2026, 06:53 AM UTC
Problem is identified we are going to apply the fix
-
monitoring Jul 01, 2026, 06:58 AM UTC
We implemented a fix and are currently monitoring the result.
-
resolved Jul 01, 2026, 07:09 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 22, 2026, 06:00 AM UTC
- Resolved
- Jun 22, 2026, 06:00 AM UTC
- Duration
- —
Timeline · 1 update
Read the full incident report →
- Detected by Pingoru
- Jun 02, 2026, 09:15 AM UTC
- Resolved
- Jun 02, 2026, 09:35 AM UTC
- Duration
- 19m
Affected: Europe & Middle East (EMEA) ([EMEA] Rainbow Hub Voice Services)
Timeline · 5 updates
-
investigating Jun 02, 2026, 09:15 AM UTC
Some customers have reported issues on Rainbow Hub. Our technical teams are analyzing the issue to identify the root cause and assess the full impact. We will provide an update shortly.
-
identified Jun 02, 2026, 09:26 AM UTC
Our teams have identified the origin of the incident. Mitigation actions are in progress, including cleanup and restart of the impacted component. Service recovery is underway, and we will continue to keep you informed.
-
monitoring Jun 02, 2026, 09:32 AM UTC
**Service restoration in progress** Services are currently being restored. Please note that it may take some time before full service is fully restored for all customers. Our teams remain fully engaged to complete the recovery as quickly as possible.
-
resolved Jun 02, 2026, 09:35 AM UTC
This incident has been resolved. Thank you for your patience and understanding throughout this incident.
-
resolved Jun 03, 2026, 07:15 AM UTC
$16
Read the full incident report →
- Detected by Pingoru
- Jun 01, 2026, 01:58 PM UTC
- Resolved
- Jun 01, 2026, 04:27 PM UTC
- Duration
- 2h 28m
Affected: Europe & Middle East (EMEA) ([EMEA] Rainbow Hub Voice Services)North America (NA) ([NA] Rainbow Core Services)North America (NA) ([NA] Rainbow Conferencing)North America (NA) ([NA] Rainbow Media Relays)North America (NA) ([NA] Rainbow Hub Voices Services)Asia-Pacific (APAC) ([APAC] Rainbow Media Relays)
Timeline · 11 updates
Read the full incident report →
- Detected by Pingoru
- May 04, 2026, 09:53 AM UTC
- Resolved
- May 04, 2026, 09:53 AM UTC
- Duration
- —
Timeline · 1 update
Read the full incident report →
- Detected by Pingoru
- Apr 06, 2026, 11:59 AM UTC
- Resolved
- Apr 06, 2026, 11:59 AM UTC
- Duration
- —
Timeline · 1 update
-
resolved Apr 06, 2026, 11:59 AM UTC
Type: Incident Duration: 2 hours and 57 minutes Affected Components: [CALA] Rainbow Hub Voices Services Apr 6, 11:59:00 GMT+0 - Investigating - We are currently investigating this incident. Apr 6, 13:47:39 GMT+0 - Identified - We are continuing to work on a fix for this incident. Apr 6, 14:25:32 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Apr 6, 14:56:27 GMT+0 - Resolved - This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 01, 2026, 05:30 AM UTC
- Resolved
- Apr 01, 2026, 05:30 AM UTC
- Duration
- —
Timeline · 1 update
Read the full incident report →
- Detected by Pingoru
- Mar 31, 2026, 06:28 AM UTC
- Resolved
- Mar 31, 2026, 06:28 AM UTC
- Duration
- —
Timeline · 1 update
Read the full incident report →
- Detected by Pingoru
- Mar 16, 2026, 09:00 PM UTC
- Resolved
- Mar 16, 2026, 09:00 PM UTC
- Duration
- —
Timeline · 1 update
-
resolved Mar 16, 2026, 09:00 PM UTC
Type: Incident Duration: 50 minutes Affected Components: [WW] Rainbow Hybrid PBX Telephony, [WW] Rainbow Administration & Subscriptions, , [EMEA] Rainbow Hub Voice Services, Global (WW) → Mar 16, 21:00:22 GMT+0 - Identified - We are continuing to work on a fix for this incident. Mar 16, 21:50:22 GMT+0 - Resolved - This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Feb 16, 2026, 09:11 AM UTC
- Resolved
- Feb 16, 2026, 09:11 AM UTC
- Duration
- —
Affected: Rainbow
Read the full incident report →
- Detected by Pingoru
- Feb 16, 2026, 09:11 AM UTC
- Resolved
- Feb 16, 2026, 09:11 AM UTC
- Duration
- —
Timeline · 1 update
-
resolved Feb 16, 2026, 09:11 AM UTC
Type: Incident Duration: 40 minutes Affected Components: [WW] Rainbow Hybrid PBX Telephony, [EMEA] Rainbow Hub Voice Services, [WW] Rainbow Administration & Subscriptions, [DE] Rainbow Core Services, [EMEA] Rainbow Core Services, , , Global (WW) → Germany (DE) → Feb 16, 09:11:00 GMT+0 - Identified - We experienced some slowness on the European platform between 10:10 and 10:30 CET, which resulted in degraded service access in certain areas and on some features. This was due to partial congestion caused by an update rollout from our IaaS provider. Service is back to normal. We keep monitoring closely Feb 16, 09:51:15 GMT+0 - Resolved - This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Feb 09, 2026, 07:30 AM UTC
- Resolved
- Feb 09, 2026, 07:30 AM UTC
- Duration
- —
Timeline · 1 update
-
resolved Feb 09, 2026, 07:30 AM UTC
Type: Incident Duration: 1 hour and 25 minutes Feb 9, 07:30:00 GMT+0 - Investigating - We are currently investigating this incident. Feb 9, 07:45:00 GMT+0 - Identified - We are continuing to work on a fix for this incident. Feb 9, 07:55:00 GMT+0 - Resolved - This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Feb 04, 2026, 08:47 AM UTC
- Resolved
- Feb 04, 2026, 08:47 AM UTC
- Duration
- —
Affected: Rainbow
Read the full incident report →
- Detected by Pingoru
- Feb 04, 2026, 08:47 AM UTC
- Resolved
- Feb 04, 2026, 08:47 AM UTC
- Duration
- —
Timeline · 1 update
Read the full incident report →
