Rainbow experienced a minor incident on June 1, 2026, lasting —. The incident has been resolved; the full update timeline is below.
Update timeline
- resolved Jun 01, 2026, 01:58 PM UTC
Type: Incident Duration: 2 hours and 29 minutes Affected Components: [EMEA] Rainbow Hub Voice Services Jun 1, 13:58:11 GMT+0 - Investigating - We are currently investigating this incident. Jun 1, 14:10:55 GMT+0 - Investigating - We’re currently experiencing a loss of telephony for some customers, with intermittent disruptions affecting others. We understand the impact this may have and sincerely apologize for the inconvenience. Our teams are actively investigating and working to restore full service as quickly as possible. Jun 1, 14:58:37 GMT+0 - Identified - **Ongoing investigation** We are observing an intermittent network issue affecting both our data centers in Roubaix and Limburg. We are working closely with our IaaS provider to analyze the situation and identify the root cause. Our teams remain fully engaged to restore full stability as quickly as possible. Jun 1, 15:30:12 GMT+0 - Identified - Our teams remain fully mobilized and are continuing in-depth analysis with our IaaS provider. Work is progressing, and we are focused on restoring full service stability. Jun 1, 15:42:41 GMT+0 - Identified - The network has been stabilized, but the service is still impacted. Our teams are now focusing on the application layer and are fully engaged in restoring full service as quickly as possible. Jun 1, 15:50:58 GMT+0 - Identified - **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. Jun 1, 15:57:38 GMT+0 - Monitoring - **Service restored** Service has now been restored. Our teams are continuing to monitor the situation closely to ensure ongoing stability. If you continue to experience issues, please restart your Rainbow phone or softphone application. Thank you for your patience and understanding throughout this incident. Jun 1, 14:28:55 GMT+0 - Investigating - **Increase in impact** We are currently seeing an increase in the number of customers affected. All European users are impacted. We understand how critical this service is and sincerely apologize for the continued inconvenience. At this time, the root cause has not yet been identified, but our teams are actively investigating and working urgently to resolve the issue. Jun 1, 16:27:05 GMT+0 - Resolved - This incident has been resolved. Jun 2, 08:28:53 GMT+0 - Postmortem - ## Post-Incident Report **Incident Window:** June 1st, 2026 – 15:45 to 18:00 CEST ### Summary On June 1st, 2026, we experienced a network incident that led to **Rainbow Hub service disruption in Europe**, with up to **\~50% traffic loss**. During this period, some users may have experienced **intermittent connectivity issues**, up to **full service disruption** at peak impact. ### Root Cause The incident occurred in the context of our execution of the **Rainbow Infrastructure upgrade plan and the connection of a new data center.** An infrastructure-level network configuration inconsistency resulted in network instability and significant packet loss affecting Rainbow Hub components. ### Resolution Our teams identified the issue and worked in coordination with our infrastructure provider. The misconfigured routes were corrected and the network stabilized. **Packet loss was resolved by 17:20 CEST**, with **full service restoration completed at 18:00 CEST**. ### Preventive Actions To prevent recurrence, we are implementing the following improvements: * Strengthening **configuration validation processes**, including multi-level and cross-DC checks * Adjusting **change scheduling** to reduce user impact while ensuring adequate monitoring * Enhancing **monitoring and alerting**, particularly for routing anomalies, link flapping, and infrastructure changes * The ongoing **infrastructure upgrade plan** will furthermore result in better platform resilience to network instabilities