Is Rainbow down?
Last checked 4m agoNo incidents right now.
Rainbow is operational right now. Last checked 4m ago; the most recent incident resolved 11d ago.
Real-time Rainbow status, recent outages, and incident history — pulled directly from Rainbow's official status page at https://status.openrainbow.com every 5 minutes. Pingoru tracks 35 Rainbow services and has captured 22 incidents in the last 90 days (99.32% uptime). Get email, Slack, Discord, or webhook alerts the moment Rainbow reports a new incident — free for 5 monitors, no credit card.
Recent outages & incidents
Past 90 days- [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
Latest: $16
-
-
Timeline · 1 update
- resolved · Jun 02, 2026, 09:15 AM UTC
Type: Incident Duration: 20 minutes Affected Components: [EMEA] Rainbow Hub Voice Services Jun 2, 09:15:54 GMT+0 - Investigating - 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. Jun 2, 09:26:31 GMT+0 - Identified - 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. Jun 2, 09:32:52 GMT+0 - Monitoring - **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 2, 09:35:38 GMT+0 - Resolved - This incident has been resolved. 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 3, 07:15:16 GMT+0 - Postmortem - # Post-Incident Report Incident Window: June 2, 2026 - 11:09 – 11:30 CEST ### What happened? Yesterday, we experienced a temporary issue affecting one component of our Rainbow Hub infrastructure. A switchover to the backup system was automatically triggered, but it did not start as expected, which led to a short service disruption. ### Impact During this period, Rainbow Hub users in Europe were unable to make calls. ### Resolution Our teams acted immediately to stabilize the affected system and safely restore service. Full service was restored at 11:30 CEST. ### Root cause The issue was linked to an internal database system inconsistency that impacted service availability and prevented the failover mechanism from operating as expected. This type of inconsistency had been observed previously, but only under a very specific and rarely encountered combination of conditions. A correction addressing this class of issue was already in preparation and planned for production update. ### What we’re doing? The fix addressing this issue will be deployed on our European infrastructure on the evening of June 3rd, as part of a more general worldwide fix in all regions. While we have strong confidence this will prevent a recurrence, we are continuing to monitor closely. We sincerely apologize for the inconvenience caused and thank you for your patience and continued trust.
Latest: Type: Incident Duration: 20 minutes Affected Components: [EMEA] Rainbow Hub Voice Services Jun 2, 09:15:54 GMT+0 - Investigating - Some customers have reported issues on Rainbow Hu…
-
- [EMEA] Rainbow Hub Voice Services[NA] Rainbow Core Services[NA] Rainbow Conferencing[NA] Rainbow Media Relays[NA] Rainbow Hub Voices Services[APAC] Rainbow Media Relays
Timeline · 11 updates
- investigating · Jun 01, 2026, 01:58 PM UTC
We are currently investigating this incident.
- investigating · Jun 01, 2026, 02:10 PM UTC
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.
- investigating · Jun 01, 2026, 02:23 PM UTC
**Increase in impact** We are currently seeing an increase in the number of customers affected. 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.
- investigating · Jun 01, 2026, 02:28 PM UTC
**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.
- identified · Jun 01, 2026, 02:58 PM UTC
**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.
- identified · Jun 01, 2026, 03:30 PM UTC
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.
- identified · Jun 01, 2026, 03:42 PM UTC
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.
- identified · Jun 01, 2026, 03:50 PM 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.
- monitoring · Jun 01, 2026, 03:57 PM UTC
**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.
- resolved · Jun 01, 2026, 04:27 PM UTC
This incident has been resolved.
- resolved · Jun 02, 2026, 08:28 AM UTC
$16
Latest: $16
-
-
Timeline · 1 update
- 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
Latest: 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 i…
-
-
Timeline · 1 update
- resolved · May 04, 2026, 09:53 AM UTC
Type: Incident Duration: 2 hours and 44 minutes Affected Components: [EMEA] Rainbow Hub Voice Services May 4, 10:08:19 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. May 4, 12:50:29 GMT+0 - Resolved - The incident has been resolved and all services are operating normally. The root cause analysis will be shared in a forthcoming post‑mortem. May 4, 13:00:11 GMT+0 - Resolved - We have corrected the recorded start time of the service interruption to reflect the exact moment the issue began. This adjustment ensures full accuracy in our incident timeline. Based on updated log analysis, we were able to more precisely determine when the incident started. We now estimate the start of the incident at **11:53 AM CET**. May 5, 08:41:23 GMT+0 - Postmortem - ## Post‑Incident Review ### Summary A short service interruption occurred following a **power loss affecting one server**. The redundancy mechanism was automatically triggered, redirecting traffic to a secondary server. ### Impact Users experienced a service interruption for a few minutes. During this time, making or receiving new calls was not possible, while ongoing calls were not interrupted. No data loss occurred. ### Root Cause The primary cause of the incident was a power loss on the initial server. When failover occurred, the secondary server was unable to instantly synchronize all data due to abnormal behavior in the database system. This resulted in a short delay while the server scaled up and stabilized. ### Resolution The redundancy mechanism functioned as designed. Service was fully restored once the secondary server completed startup, data synchronization, and load handling. ### Next Steps * Improve capacity to ensure faster startup and data synchronization when taking full load during failover * Optimize failover performance to better handle sudden data loads May 4, 09:53:00 GMT+0 - Investigating - May 4, 2026 at 12:06 PM CET Some customers have reported an interruption of Rainbow Hub service. Our technical teams are analyzing the issue to identify the root cause and assess the full impact. We will provide an update shortly.
Latest: Type: Incident Duration: 2 hours and 44 minutes Affected Components: [EMEA] Rainbow Hub Voice Services May 4, 10:08:19 GMT+0 - Monitoring - We implemented a fix and are currently m…
-
See the full Rainbow outage history
9 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.
Browse Rainbow outage history →Or sign up free to get alerts when Rainbow breaks · 10 free monitors · No credit card
- Started Jun 02, 2026, 09:15 AM UTC · Resolved Jun 02, 2026, 09:35 AM UTC · 19m
- Started Jun 02, 2026, 09:15 AM UTC · Resolved Jun 02, 2026, 09:15 AM UTC · —
- Started Jun 01, 2026, 01:58 PM UTC · Resolved Jun 01, 2026, 04:27 PM UTC · 2h 28m
- Started Jun 01, 2026, 01:58 PM UTC · Resolved Jun 01, 2026, 01:58 PM UTC · —
- Started May 04, 2026, 09:53 AM UTC · Resolved May 04, 2026, 09:53 AM UTC · —
- Started May 04, 2026, 09:53 AM UTC · Resolved May 04, 2026, 12:50 PM UTC · 2h 57m
- Started Apr 06, 2026, 11:59 AM UTC · Resolved Apr 06, 2026, 11:59 AM UTC · —
- Started Apr 06, 2026, 11:59 AM UTC · Resolved Apr 06, 2026, 11:59 AM UTC · —