Rainbow HDS Status - Incident history https://status.openrainbow.health Rainbow HDS Thu, 9 Apr 2026 19:00:00 +0000 [WW] OVH Scheduled Major Maintenance on Apr 9th Type: Maintenance Duration: 1 hour Affected Components: Rainbow Media Relays, Rainbow Conferencing, Rainbow Core Services, Rainbow Hybrid PBX Telephony, Rainbow Administration & Subscriptions, Rainbow ProSanteConnect Authentication Apr 9, 19:00:01 GMT+0 - Identified - Maintenance is now in progress Apr 9, 20:00:00 GMT+0 - Completed - Maintenance has completed successfully Apr 9, 19:00:00 GMT+0 - Identified - OVH, our underlying IaaS provider, will conduct an exceptional infrastructure maintenance on **April 9, 2026 at 21:00 CEST**. This operation targets core platform components and may result in **temporary service degradation or brief interruptions** across our systems. The potential impact is **global (WW)**. We have implemented preventive safeguards to **minimize any operational impact** during the maintenance window. Our team will supervise the event end‑to‑end and respond immediately to any anomaly. Thank you for your understanding. Type: Maintenance

Duration: 1 hour

Affected Components: , , , , ,

<p><small>Apr <var data-var='date'> 9</var>, <var data-var='time'>19:00:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Apr <var data-var='date'> 9</var>, <var data-var='time'>20:00:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully.</p> <p><small>Apr <var data-var='date'> 9</var>, <var data-var='time'>19:00:00</var> GMT+0</small><br><strong>Identified</strong> - OVH, our underlying IaaS provider, will conduct an exceptional infrastructure maintenance on **April 9, 2026 at 21:00 CEST**. This operation targets core platform components and may result in **temporary service degradation or brief interruptions** across our systems. The potential impact is **global (WW)**. We have implemented preventive safeguards to **minimize any operational impact** during the maintenance window. Our team will supervise the event end‑to‑end and respond immediately to any anomaly. Thank you for your understanding..</p> ]]> Thu, 9 Apr 2026 19:00:00 +0000 https://status.openrainbow.health/maintenance/cmn7axgo806f2h889ad7nxoq7 https://status.openrainbow.health/maintenance/cmn7axgo806f2h889ad7nxoq7 Infrastructure slowness issues Type: Incident Affected Components: Rainbow Core Services, Rainbow Hybrid PBX Telephony, Rainbow Administration & Subscriptions Feb 16, 09:10:00 GMT+0 - Resolved - Nous avons observé des ralentissements sur notre plateforme HDS ce jour, entre 10h10 et 10h30 CET. Cet incident a entraîné une dégradation de l'accès au service pour certains établissements de santé et pourcertaines fonctionnalités.Cette situation a été causée par une congestion partielle liée au déploiement d'une mise à jour par notre fournisseur d'infrastructure (IaaS).Le service est désormais rétabli et fonctionne normalement. Nous maintenons toutefois une surveillance accrue de l'infrastructure. Feb 16, 10:05:56 GMT+0 - Resolved - This incident has been resolved. Nous avons observé des ralentissements sur notre plateforme HDS ce jour, entre 10h10 et 10h30 CET. Cet incident a entraîné une dégradation de l'accès au service pour certains établissements de santé et pourcertaines fonctionnalités.Cette situation a été causée par une congestion partielle liée au déploiement d'une mise à jour par notre fournisseur d'infrastructure (IaaS).Le service est désormais rétabli et fonctionne normalement. Nous maintenons toutefois une surveillance accrue de l'infrastructure. Type: Incident

Affected Components: , ,

<p><small>Feb <var data-var='date'> 16</var>, <var data-var='time'>09:10:00</var> GMT+0</small><br><strong>Resolved</strong> - Nous avons observé des ralentissements sur notre plateforme HDS ce jour, entre 10h10 et 10h30 CET. Cet incident a entraîné une dégradation de l'accès au service pour certains établissements de santé et pourcertaines fonctionnalités.Cette situation a été causée par une congestion partielle liée au déploiement d'une mise à jour par notre fournisseur d'infrastructure (IaaS).Le service est désormais rétabli et fonctionne normalement. Nous maintenons toutefois une surveillance accrue de l'infrastructure..</p> <p><small>Feb <var data-var='date'> 16</var>, <var data-var='time'>10:05:56</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved. Nous avons observé des ralentissements sur notre plateforme HDS ce jour, entre 10h10 et 10h30 CET. Cet incident a entraîné une dégradation de l'accès au service pour certains établissements de santé et pourcertaines fonctionnalités.Cette situation a été causée par une congestion partielle liée au déploiement d'une mise à jour par notre fournisseur d'infrastructure (IaaS).Le service est désormais rétabli et fonctionne normalement. Nous maintenons toutefois une surveillance accrue de l'infrastructure..</p> ]]> Mon, 16 Feb 2026 09:10:00 +0000 https://status.openrainbow.health/incident/cmlp1kai51cm713j8i5xytxtt https://status.openrainbow.health/incident/cmlp1kai51cm713j8i5xytxtt Issue on Rainbow hybrid telephony / API portals Type: Incident Duration: 1 hour and 16 minutes Affected Components: Rainbow Core Services, Rainbow Hybrid PBX Telephony Oct 20, 16:46:00 GMT+0 - Investigating - We are currently investigating this incident. Oct 20, 17:10:00 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Oct 20, 18:02:10 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 1 hour and 16 minutes

Affected Components: ,

<p><small>Oct <var data-var='date'> 20</var>, <var data-var='time'>16:46:00</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Oct <var data-var='date'> 20</var>, <var data-var='time'>17:10:00</var> GMT+0</small><br><strong>Monitoring</strong> - We implemented a fix and are currently monitoring the result..</p> <p><small>Oct <var data-var='date'> 20</var>, <var data-var='time'>18:02:10</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Mon, 20 Oct 2025 16:46:00 +0000 https://status.openrainbow.health/incident/cmgze8wrt02gfz7ue6euw5twm https://status.openrainbow.health/incident/cmgze8wrt02gfz7ue6euw5twm Rainbow disconnections Type: Incident Duration: 2 hours and 15 minutes Affected Components: Rainbow Hybrid PBX Telephony, Rainbow Core Services May 22, 11:47:00 GMT+0 - Investigating - We are currently investigating disconnections and slowness impacting end users and webRTC gateways. May 22, 14:02:00 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 2 hours and 15 minutes

Affected Components: ,

<p><small>May <var data-var='date'> 22</var>, <var data-var='time'>11:47:00</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating disconnections and slowness impacting end users and webRTC gateways..</p> <p><small>May <var data-var='date'> 22</var>, <var data-var='time'>14:02:00</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved. .</p> ]]> Thu, 22 May 2025 11:47:00 +0000 https://status.openrainbow.health/incident/cmb0o0wzm002ctldr0bb04tvx https://status.openrainbow.health/incident/cmb0o0wzm002ctldr0bb04tvx Ranbow incident Type: Incident Duration: 1 hour and 5 minutes Affected Components: Rainbow Hybrid PBX Telephony, Rainbow Conferencing, Rainbow Core Services, Rainbow Administration & Subscriptions, Rainbow Media Relays Apr 26, 05:30:00 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Apr 26, 05:25:00 GMT+0 - Identified - Apr 26, 05:35:00 GMT+0 - Resolved - This incident has been resolved. Apr 26, 05:08:00 GMT+0 - Investigating - We are currently investigating this incident. Type: Incident

Duration: 1 hour and 5 minutes

Affected Components: , , , ,

<p><small>Apr <var data-var='date'> 26</var>, <var data-var='time'>05:30:00</var> GMT+0</small><br><strong>Monitoring</strong> - We implemented a fix and are currently monitoring the result..</p> <p><small>Apr <var data-var='date'> 26</var>, <var data-var='time'>05:25:00</var> GMT+0</small><br><strong>Identified</strong> - .</p> <p><small>Apr <var data-var='date'> 26</var>, <var data-var='time'>05:35:00</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Apr <var data-var='date'> 26</var>, <var data-var='time'>05:08:00</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> ]]> Sat, 26 Apr 2025 05:08:00 +0000 https://status.openrainbow.health/incident/cm9xtnqex0079bi72rbpanj9o https://status.openrainbow.health/incident/cm9xtnqex0079bi72rbpanj9o Rainbow service impaired Type: Incident Duration: 1 hour Affected Components: Rainbow Core Services, Rainbow ProSanteConnect Authentication, Rainbow Hybrid PBX Telephony Mar 16, 02:16:00 GMT+0 - Resolved - This incident has been resolved. Mar 16, 01:16:00 GMT+0 - Investigating - We are currently investigating this incident. Type: Incident

Duration: 1 hour

Affected Components: , ,

<p><small>Mar <var data-var='date'> 16</var>, <var data-var='time'>02:16:00</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Mar <var data-var='date'> 16</var>, <var data-var='time'>01:16:00</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> ]]> Sun, 16 Mar 2025 01:16:00 +0000 https://status.openrainbow.health/incident/cm8azni2i001xybom7396b1q0 https://status.openrainbow.health/incident/cm8azni2i001xybom7396b1q0 Rainbow HDS : degraded performance for a few minutes Type: Incident Duration: 14 minutes Affected Components: Rainbow Core Services Feb 26, 09:36:00 GMT+0 - Investigating - We detected an issue with one of our core network equipment. Users may experience degraded performance. We are currently investigating this incident. Feb 26, 09:40:00 GMT+0 - Identified - We identified the server in fault and we are currently monitoring and investigating the equipment. We are continuing to work on a fix for this incident. Impact should be minimal for users Feb 26, 09:47:00 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Feb 26, 09:50:00 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 14 minutes

Affected Components:

<p><small>Feb <var data-var='date'> 26</var>, <var data-var='time'>09:36:00</var> GMT+0</small><br><strong>Investigating</strong> - We detected an issue with one of our core network equipment. Users may experience degraded performance. We are currently investigating this incident..</p> <p><small>Feb <var data-var='date'> 26</var>, <var data-var='time'>09:40:00</var> GMT+0</small><br><strong>Identified</strong> - We identified the server in fault and we are currently monitoring and investigating the equipment. We are continuing to work on a fix for this incident. Impact should be minimal for users.</p> <p><small>Feb <var data-var='date'> 26</var>, <var data-var='time'>09:47:00</var> GMT+0</small><br><strong>Monitoring</strong> - We implemented a fix and are currently monitoring the result..</p> <p><small>Feb <var data-var='date'> 26</var>, <var data-var='time'>09:50:00</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Wed, 26 Feb 2025 09:36:00 +0000 https://status.openrainbow.health/incident/cm7lqv8ss0031usq5gyj8syar https://status.openrainbow.health/incident/cm7lqv8ss0031usq5gyj8syar Rainbow connection issues Type: Incident Duration: 20 minutes Affected Components: Rainbow Media Relays, Rainbow Core Services, Rainbow Administration & Subscriptions, Rainbow ProSanteConnect Authentication, Rainbow Conferencing, Rainbow Hybrid PBX Telephony Oct 30, 13:29:38 GMT+0 - Investigating - We are currently investigating this incident. Oct 30, 13:45:04 GMT+0 - Identified - The issue has been identified as global peering issues on our main cloud provider. Work is under progress to mitigate the issue. Oct 30, 13:50:00 GMT+0 - Resolved - This incident has been resolved. Oct 30, 13:47:00 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Type: Incident

Duration: 20 minutes

Affected Components: , , , , ,

<p><small>Oct <var data-var='date'> 30</var>, <var data-var='time'>13:29:38</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Oct <var data-var='date'> 30</var>, <var data-var='time'>13:45:04</var> GMT+0</small><br><strong>Identified</strong> - The issue has been identified as global peering issues on our main cloud provider. Work is under progress to mitigate the issue..</p> <p><small>Oct <var data-var='date'> 30</var>, <var data-var='time'>13:50:00</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Oct <var data-var='date'> 30</var>, <var data-var='time'>13:47:00</var> GMT+0</small><br><strong>Monitoring</strong> - We implemented a fix and are currently monitoring the result..</p> ]]> Wed, 30 Oct 2024 13:29:38 +0000 https://status.openrainbow.health/incident/cm2vwyepi002tk4xra4st6rfu https://status.openrainbow.health/incident/cm2vwyepi002tk4xra4st6rfu Rainbow degraded performance Type: Incident Duration: 3 days and 13 hours Affected Components: Rainbow Core Services Oct 1, 11:19:00 GMT+0 - Investigating - We experienced trouble with one server in backend. Some users may experience degraded performance during their usage. We are currently investigating this incident. Oct 1, 12:44:00 GMT+0 - Resolved - Type: Incident

Duration: 3 days and 13 hours

Affected Components:

<p><small>Oct <var data-var='date'> 1</var>, <var data-var='time'>11:19:00</var> GMT+0</small><br><strong>Investigating</strong> - We experienced trouble with one server in backend. Some users may experience degraded performance during their usage. We are currently investigating this incident..</p> <p><small>Oct <var data-var='date'> 1</var>, <var data-var='time'>12:44:00</var> GMT+0</small><br><strong>Resolved</strong> - .</p> ]]> Tue, 1 Oct 2024 11:19:00 +0000 https://status.openrainbow.health/incident/cm1qd2mmv0007y90k3heysn4d https://status.openrainbow.health/incident/cm1qd2mmv0007y90k3heysn4d Rainbow degraded performance Type: Incident Duration: 5 minutes Affected Components: Rainbow Core Services, Rainbow Hybrid PBX Telephony Jul 28, 12:48:00 GMT+0 - Identified - We have identified the issue and are working on a fix Jul 28, 12:50:00 GMT+0 - Resolved - This incident has been resolved. Jul 28, 12:45:00 GMT+0 - Investigating - We are currently investigating this incident. Type: Incident

Duration: 5 minutes

Affected Components: ,

<p><small>Jul <var data-var='date'> 28</var>, <var data-var='time'>12:48:00</var> GMT+0</small><br><strong>Identified</strong> - We have identified the issue and are working on a fix.</p> <p><small>Jul <var data-var='date'> 28</var>, <var data-var='time'>12:50:00</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Jul <var data-var='date'> 28</var>, <var data-var='time'>12:45:00</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> ]]> Sun, 28 Jul 2024 12:45:00 +0000 https://status.openrainbow.health/incident/clz5m5fhe230901j0od6pvmmo19 https://status.openrainbow.health/incident/clz5m5fhe230901j0od6pvmmo19 Rainbow slowness Type: Incident Duration: 2 hours and 17 minutes Affected Components: Rainbow Core Services Dec 15, 09:17:00 GMT+0 - Resolved - Our monitoring shows the different issues are now closed! The root cause analysis is now under progress. Dec 15, 07:00:00 GMT+0 - Investigating - We are currently investigating an incident impacting rainbow core usages. You may experience errors when performing some operations. Dec 15, 08:18:00 GMT+0 - Identified - We identified the root cause and are actively working on a mitigation for this incident. Dec 15, 08:50:00 GMT+0 - Monitoring - A worldwide rollback of the web client has been performed to version 112 to mitigate slownesses and errors in EMEA region. We are currently monitoring the solution. Type: Incident

Duration: 2 hours and 17 minutes

Affected Components:

<p><small>Dec <var data-var='date'> 15</var>, <var data-var='time'>09:17:00</var> GMT+0</small><br><strong>Resolved</strong> - Our monitoring shows the different issues are now closed! The root cause analysis is now under progress..</p> <p><small>Dec <var data-var='date'> 15</var>, <var data-var='time'>07:00:00</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating an incident impacting rainbow core usages. You may experience errors when performing some operations..</p> <p><small>Dec <var data-var='date'> 15</var>, <var data-var='time'>08:18:00</var> GMT+0</small><br><strong>Identified</strong> - We identified the root cause and are actively working on a mitigation for this incident..</p> <p><small>Dec <var data-var='date'> 15</var>, <var data-var='time'>08:50:00</var> GMT+0</small><br><strong>Monitoring</strong> - A worldwide rollback of the web client has been performed to version 112 to mitigate slownesses and errors in EMEA region. We are currently monitoring the solution. .</p> ]]> Thu, 15 Dec 2022 07:00:00 +0000 https://status.openrainbow.health/incident/clc7j35h726826hkofl4ftmsem https://status.openrainbow.health/incident/clc7j35h726826hkofl4ftmsem Service failover Type: Incident Duration: 50 minutes Affected Components: Rainbow Conferencing Oct 20, 14:20:00 GMT+0 - Investigating - A hardware incident occurred and triggered an automatic failover to secondary servers. Some users may have been disconnected from their webRTC conference and had to reconnect. Oct 20, 14:25:00 GMT+0 - Monitoring - The failover has been done automatically. Analysis on hardware failure is under progress Oct 20, 15:10:00 GMT+0 - Resolved - We just resolved the issue! Type: Incident

Duration: 50 minutes

Affected Components:

<p><small>Oct <var data-var='date'> 20</var>, <var data-var='time'>14:20:00</var> GMT+0</small><br><strong>Investigating</strong> - A hardware incident occurred and triggered an automatic failover to secondary servers. Some users may have been disconnected from their webRTC conference and had to reconnect..</p> <p><small>Oct <var data-var='date'> 20</var>, <var data-var='time'>14:25:00</var> GMT+0</small><br><strong>Monitoring</strong> - The failover has been done automatically. Analysis on hardware failure is under progress.</p> <p><small>Oct <var data-var='date'> 20</var>, <var data-var='time'>15:10:00</var> GMT+0</small><br><strong>Resolved</strong> - We just resolved the issue!.</p> ]]> Thu, 20 Oct 2022 14:20:00 +0000 https://status.openrainbow.health/incident/cl9h60o2z146720xeog9fpjqme2 https://status.openrainbow.health/incident/cl9h60o2z146720xeog9fpjqme2 Core systems degradation Type: Incident Duration: 43 minutes Affected Components: Rainbow Conferencing, Rainbow ProSanteConnect Authentication, Rainbow Hybrid PBX Telephony, Rainbow Administration & Subscriptions, Rainbow Media Relays, Rainbow Core Services Sep 20, 11:37:00 GMT+0 - Investigating - We are currently investigating this incident. Sep 20, 12:06:11 GMT+0 - Identified - We are continuing to work on a fix for this incident. We see impacts on several components. We are currently restarting services Sep 20, 12:15:00 GMT+0 - Monitoring - We implemented a fix and currently monitoring the result. Sep 20, 12:20:00 GMT+0 - Resolved - We just resolved the issue! Type: Incident

Duration: 43 minutes

Affected Components: , , , , ,

<p><small>Sep <var data-var='date'> 20</var>, <var data-var='time'>11:37:00</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Sep <var data-var='date'> 20</var>, <var data-var='time'>12:06:11</var> GMT+0</small><br><strong>Identified</strong> - We are continuing to work on a fix for this incident. We see impacts on several components. We are currently restarting services.</p> <p><small>Sep <var data-var='date'> 20</var>, <var data-var='time'>12:15:00</var> GMT+0</small><br><strong>Monitoring</strong> - We implemented a fix and currently monitoring the result..</p> <p><small>Sep <var data-var='date'> 20</var>, <var data-var='time'>12:20:00</var> GMT+0</small><br><strong>Resolved</strong> - We just resolved the issue!.</p> ]]> Tue, 20 Sep 2022 11:37:00 +0000 https://status.openrainbow.health/incident/cl8a5f8xr23425hxn088e06fna https://status.openrainbow.health/incident/cl8a5f8xr23425hxn088e06fna WebRTC conferences start errors Type: Incident Duration: 1 hour and 5 minutes Affected Components: Rainbow Conferencing Jun 17, 06:55:00 GMT+0 - Identified - Some users where not able to start or join a webRTC conferences Jun 17, 07:32:00 GMT+0 - Monitoring - We implemented a fix and currently monitoring the result. Jun 17, 08:00:00 GMT+0 - Resolved - We just resolved the issue! Type: Incident

Duration: 1 hour and 5 minutes

Affected Components:

<p><small>Jun <var data-var='date'> 17</var>, <var data-var='time'>06:55:00</var> GMT+0</small><br><strong>Identified</strong> - Some users where not able to start or join a webRTC conferences.</p> <p><small>Jun <var data-var='date'> 17</var>, <var data-var='time'>07:32:00</var> GMT+0</small><br><strong>Monitoring</strong> - We implemented a fix and currently monitoring the result..</p> <p><small>Jun <var data-var='date'> 17</var>, <var data-var='time'>08:00:00</var> GMT+0</small><br><strong>Resolved</strong> - We just resolved the issue!.</p> ]]> Fri, 17 Jun 2022 06:55:00 +0000 https://status.openrainbow.health/incident/cl4i5nd86109669bsohfs17bs65 https://status.openrainbow.health/incident/cl4i5nd86109669bsohfs17bs65 Global Rainbow slowness and disconnection Type: Incident Duration: 1 hour and 16 minutes Affected Components: Rainbow Core Services Jun 1, 10:35:33 GMT+0 - Resolved - Situation is back to normal Jun 1, 09:20:00 GMT+0 - Investigating - We are currently investigating this incident. Jun 1, 10:19:22 GMT+0 - Monitoring - We implemented a fix and currently monitoring the result. Type: Incident

Duration: 1 hour and 16 minutes

Affected Components:

<p><small>Jun <var data-var='date'> 1</var>, <var data-var='time'>10:35:33</var> GMT+0</small><br><strong>Resolved</strong> - Situation is back to normal.</p> <p><small>Jun <var data-var='date'> 1</var>, <var data-var='time'>09:20:00</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Jun <var data-var='date'> 1</var>, <var data-var='time'>10:19:22</var> GMT+0</small><br><strong>Monitoring</strong> - We implemented a fix and currently monitoring the result..</p> ]]> Wed, 1 Jun 2022 09:20:00 +0000 https://status.openrainbow.health/incident/cl3vez9q00904kwna0ncfa16g https://status.openrainbow.health/incident/cl3vez9q00904kwna0ncfa16g Ranbow incident Type: Incident Duration: 1 hour and 10 minutes Affected Components: Rainbow Core Services May 3, 11:30:00 GMT+0 - Investigating - We are currently investigating this incident. May 3, 12:20:00 GMT+0 - Identified - We are continuing to work on a fix for this incident. May 3, 12:30:00 GMT+0 - Identified - Rainbow client can now connect, use IM and use conferencing. But Rainbow telephony is still down. We are continuing to work on a fix for this incident. May 3, 12:40:00 GMT+0 - Resolved - We just resolved the issue! May 3, 12:36:00 GMT+0 - Monitoring - We implemented a fix and currently monitoring the result. Type: Incident

Duration: 1 hour and 10 minutes

Affected Components:

<p><small>May <var data-var='date'> 3</var>, <var data-var='time'>11:30:00</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>May <var data-var='date'> 3</var>, <var data-var='time'>12:20:00</var> GMT+0</small><br><strong>Identified</strong> - We are continuing to work on a fix for this incident..</p> <p><small>May <var data-var='date'> 3</var>, <var data-var='time'>12:30:00</var> GMT+0</small><br><strong>Identified</strong> - Rainbow client can now connect, use IM and use conferencing. But Rainbow telephony is still down. We are continuing to work on a fix for this incident. .</p> <p><small>May <var data-var='date'> 3</var>, <var data-var='time'>12:40:00</var> GMT+0</small><br><strong>Resolved</strong> - We just resolved the issue!.</p> <p><small>May <var data-var='date'> 3</var>, <var data-var='time'>12:36:00</var> GMT+0</small><br><strong>Monitoring</strong> - We implemented a fix and currently monitoring the result..</p> ]]> Tue, 3 May 2022 11:30:00 +0000 https://status.openrainbow.health/incident/cl2q2kq0166014i4n8cl7srm4g https://status.openrainbow.health/incident/cl2q2kq0166014i4n8cl7srm4g Rainbow issues Type: Incident Duration: 30 minutes Affected Components: Rainbow Core Services Apr 20, 05:10:00 GMT+0 - Investigating - We have received an alert. We are currently investigating this incident. Apr 20, 05:40:00 GMT+0 - Resolved - We just resolved the issue! Impact on end users must have been very limited thanks to redundant services (Now services all running on active nodes, issues only located on passive nodes) Type: Incident

Duration: 30 minutes

Affected Components:

<p><small>Apr <var data-var='date'> 20</var>, <var data-var='time'>05:10:00</var> GMT+0</small><br><strong>Investigating</strong> - We have received an alert. We are currently investigating this incident..</p> <p><small>Apr <var data-var='date'> 20</var>, <var data-var='time'>05:40:00</var> GMT+0</small><br><strong>Resolved</strong> - We just resolved the issue! Impact on end users must have been very limited thanks to redundant services (Now services all running on active nodes, issues only located on passive nodes).</p> ]]> Wed, 20 Apr 2022 05:10:00 +0000 https://status.openrainbow.health/incident/cl27dcpom330631e2mz0vvsfijj https://status.openrainbow.health/incident/cl27dcpom330631e2mz0vvsfijj Rainbow issues Type: Incident Duration: 1 day and 4 hours Affected Components: Rainbow Core Services Apr 19, 22:11:00 GMT+0 - Resolved - We just resolved the issue! Impact on end users must have been very limited thanks to redundant services (Now services all running on active nodes, issues only located on passive nodes) Apr 19, 21:43:00 GMT+0 - Investigating - We have received an alert. We are currently investigating this incident. Type: Incident

Duration: 1 day and 4 hours

Affected Components:

<p><small>Apr <var data-var='date'> 19</var>, <var data-var='time'>22:11:00</var> GMT+0</small><br><strong>Resolved</strong> - We just resolved the issue! Impact on end users must have been very limited thanks to redundant services (Now services all running on active nodes, issues only located on passive nodes).</p> <p><small>Apr <var data-var='date'> 19</var>, <var data-var='time'>21:43:00</var> GMT+0</small><br><strong>Investigating</strong> - We have received an alert. We are currently investigating this incident..</p> ]]> Tue, 19 Apr 2022 21:43:00 +0000 https://status.openrainbow.health/incident/cl278muli177677e2mzy46nf73s https://status.openrainbow.health/incident/cl278muli177677e2mzy46nf73s Intermittent issues on HDS Type: Incident Duration: 1 minute Affected Components: Rainbow Conferencing, Rainbow Core Services Nov 18, 13:51:00 GMT+0 - Resolved - We just resolved the issue! Nov 18, 13:50:00 GMT+0 - Resolved - We just resolved the issue! Type: Incident

Duration: 1 minute

Affected Components: ,

<p><small>Nov <var data-var='date'> 18</var>, <var data-var='time'>13:51:00</var> GMT+0</small><br><strong>Resolved</strong> - We just resolved the issue!.</p> <p><small>Nov <var data-var='date'> 18</var>, <var data-var='time'>13:50:00</var> GMT+0</small><br><strong>Resolved</strong> - We just resolved the issue!.</p> ]]> Thu, 18 Nov 2021 13:50:00 +0000 https://status.openrainbow.health/incident/ckw513kog207008kn2hp5obsa6 https://status.openrainbow.health/incident/ckw513kog207008kn2hp5obsa6 Rainbow incident Type: Incident Duration: 3 days and 3 hours Affected Components: Rainbow Media Relays, Rainbow Hybrid PBX Telephony, Rainbow Conferencing, Rainbow Administration & Subscriptions, Rainbow Core Services Oct 13, 08:22:00 GMT+0 - Resolved - We just resolved the issue! Please find more information on rainbow [help center](https://support.openrainbow.com/hc/en-us/articles/4408104836626-Incident-on-Wednesday-October-13-2021) Oct 13, 07:24:00 GMT+0 - Investigating - We are currently investigating this incident. Type: Incident

Duration: 3 days and 3 hours

Affected Components: , , , ,

<p><small>Oct <var data-var='date'> 13</var>, <var data-var='time'>08:22:00</var> GMT+0</small><br><strong>Resolved</strong> - We just resolved the issue! Please find more information on rainbow [help center](https://support.openrainbow.com/hc/en-us/articles/4408104836626-Incident-on-Wednesday-October-13-2021).</p> <p><small>Oct <var data-var='date'> 13</var>, <var data-var='time'>07:24:00</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> ]]> Wed, 13 Oct 2021 07:24:00 +0000 https://status.openrainbow.health/incident/ckupc34tu309900gjo35bb0z96m https://status.openrainbow.health/incident/ckupc34tu309900gjo35bb0z96m Improved High-Availability Type: Maintenance Duration: 14 minutes Affected Components: Rainbow Core Services, Rainbow Media Relays, Rainbow Administration & Subscriptions, Rainbow Conferencing, Rainbow Hybrid PBX Telephony Jul 7, 10:20:00 GMT+0 - Identified - The Rainbow HDS service is put in maintenance for a few minutes, as to extend high-availability and disaster recovery mechanisms using active/passive failover mechanisms. Jul 7, 10:33:49 GMT+0 - Completed - Maintenance is now complete. Type: Maintenance

Duration: 14 minutes

Affected Components: , , , ,

<p><small>Jul <var data-var='date'> 7</var>, <var data-var='time'>10:20:00</var> GMT+0</small><br><strong>Identified</strong> - The Rainbow HDS service is put in maintenance for a few minutes, as to extend high-availability and disaster recovery mechanisms using active/passive failover mechanisms..</p> <p><small>Jul <var data-var='date'> 7</var>, <var data-var='time'>10:33:49</var> GMT+0</small><br><strong>Completed</strong> - Maintenance is now complete..</p> ]]> Wed, 7 Jul 2021 10:20:00 +0000 https://status.openrainbow.health/maintenance/ckqtcb3p3111811a7om8vh4jgie https://status.openrainbow.health/maintenance/ckqtcb3p3111811a7om8vh4jgie [Major Incident] Datacenter connectivity lost (Fire in Strasbourg DC) Type: Incident Duration: 11 days and 10 hours Affected Components: Rainbow Core Services, Rainbow Media Relays, Rainbow Administration & Subscriptions, Rainbow Conferencing, Rainbow Hybrid PBX Telephony Mar 10, 01:50:00 GMT+0 - Monitoring - Our IaaS provider, OVH, suffered from a major fire disaster on March 10th in Strasbourg (FR) data-center. Events and root cause related to this tragedy are related by <a href="https://www.ovh.com/world/news/press/cpl1787.fire-our-strasbourg-site">OVH</a>. The Rainbow HDS service was unfortunately hosted in SBG3 data-center, currently unavailable and pending electrical restart for service resumption. A complete plan is on-going on ALE side to provide an extra level of resilience complete with geographical redundancy. Apr 1, 14:00:00 GMT+0 - Resolved - Following OVH's electrical and network restoration, all systems and Rainbow HDS services have been restored. Type: Incident

Duration: 11 days and 10 hours

Affected Components: , , , ,

<p><small>Mar <var data-var='date'> 10</var>, <var data-var='time'>01:50:00</var> GMT+0</small><br><strong>Monitoring</strong> - Our IaaS provider, OVH, suffered from a major fire disaster on March 10th in Strasbourg (FR) data-center. Events and root cause related to this tragedy are related by <a href="https://www.ovh.com/world/news/press/cpl1787.fire-our-strasbourg-site">OVH</a>. The Rainbow HDS service was unfortunately hosted in SBG3 data-center, currently unavailable and pending electrical restart for service resumption. A complete plan is on-going on ALE side to provide an extra level of resilience complete with geographical redundancy. .</p> <p><small>Apr <var data-var='date'> 1</var>, <var data-var='time'>14:00:00</var> GMT+0</small><br><strong>Resolved</strong> - Following OVH's electrical and network restoration, all systems and Rainbow HDS services have been restored..</p> ]]> Wed, 10 Mar 2021 01:50:00 +0000 https://status.openrainbow.health/incident/ckmc3jj76145283xoofjjxegnaz https://status.openrainbow.health/incident/ckmc3jj76145283xoofjjxegnaz Uptime Demystified ? Type: Incident Affected Components: Rainbow Core Services Nov 30, 23:00:00 GMT+0 - Resolved - Rainbow HDS (stands for 'Hébergement des Données de Santé' or Healthcare-related data hosting) is a France-located Rainbow service instance, compliant for local and European healthcare sensitive data hosting directives. Services are filtered in multiple categories: - "**Core**" services, representing all day-to-day basic features of Rainbow (Login, Instant Messaging, WebRTC P2P calls, presence, search & contacts management, file sharing ...) - "**Conferencing**" services, including Bubbles, Channels, PSTN-based and WebRTC multi-parties audio/video conferences. - "**Media Relays**" services, featuring all WebRTC traffic relays available in our various points of presence (PoP), allowing low-latency high-quality communications. - "**Hybrid PBX Telephony**" services, gathering PBX and DeskPhones connectivity to Cloud with presence and 3PCC services. - "**Admin & Subscriptions**" services, related to compagnies administration features, including mass provisioning, license enablement, subscription, billing and invoicing. Each service figures its very own uptime, according to our contractual Service Level Agreement (SLA). Only non-planned incidents are reflected on this service. Planned production rollouts are out of the scope. Should incidents occur, they are categorized as: - **Degraded**: services remaining operational but are slower to respond than usual and may slightly decrease the overall user experience. Such events do not reflect our uptime calculation. - **Minor**: some abnormal systems behavior has occured and may impact quite a few customers being a bit of nuisance with not much consequences. - **Partial**: our systems have suffered from a more consequent issue, preventing a larger subset of our users to use our service. - **Major**: that shouldn't happen but unfortunately so is life. A severe incident likely lead to a service disruption to a large majority of our users, preventing most if not all access to our services. For each category of service, our displayed uptime is calculated using the following formulae over the last period (90 days): > **Uptime** = (Total minutes over the period – **Total Incidents minutes** over the period) x 100 / Total minutes over the period where: > **Total Incidents minutes** = sum("**Major**" incident minutes) + 30% * sum("**Partial**" incidents minutes) + 30% * sum("**Minor**" incidents minutes) For each incident, duration is expressed by the delta between the time of occurence (as reported or most commonly diagnosed by our monitoring systems) and the moment where the incident has been mitigated and considered as resolved, all services being restored to a nominal state. We also provide a human-friendly daily representation of our systems daily life, through our color-code chronogram representation where: - **Green** is for a happy day, with less than 1 minute of cumulated incidents leading to downtime. - **Yellow** represents less than 20 minutes of downtime - **Orange** stands for 20 to 40 minutes of cumulated downtime. - **Red** calls for more than 40 minutes of cumulated downtime in a given day. *(degraded state being once again, out of the scope of uptime calculation)* *January 2021* Type: Incident

Affected Components:

<p><small>Nov <var data-var='date'> 30</var>, <var data-var='time'>23:00:00</var> GMT+0</small><br><strong>Resolved</strong> - Rainbow HDS (stands for 'Hébergement des Données de Santé' or Healthcare-related data hosting) is a France-located Rainbow service instance, compliant for local and European healthcare sensitive data hosting directives. Services are filtered in multiple categories: - "**Core**" services, representing all day-to-day basic features of Rainbow (Login, Instant Messaging, WebRTC P2P calls, presence, search & contacts management, file sharing ...) - "**Conferencing**" services, including Bubbles, Channels, PSTN-based and WebRTC multi-parties audio/video conferences. - "**Media Relays**" services, featuring all WebRTC traffic relays available in our various points of presence (PoP), allowing low-latency high-quality communications. - "**Hybrid PBX Telephony**" services, gathering PBX and DeskPhones connectivity to Cloud with presence and 3PCC services. - "**Admin & Subscriptions**" services, related to compagnies administration features, including mass provisioning, license enablement, subscription, billing and invoicing. Each service figures its very own uptime, according to our contractual Service Level Agreement (SLA). Only non-planned incidents are reflected on this service. Planned production rollouts are out of the scope. Should incidents occur, they are categorized as: - **Degraded**: services remaining operational but are slower to respond than usual and may slightly decrease the overall user experience. Such events do not reflect our uptime calculation. - **Minor**: some abnormal systems behavior has occured and may impact quite a few customers being a bit of nuisance with not much consequences. - **Partial**: our systems have suffered from a more consequent issue, preventing a larger subset of our users to use our service. - **Major**: that shouldn't happen but unfortunately so is life. A severe incident likely lead to a service disruption to a large majority of our users, preventing most if not all access to our services. For each category of service, our displayed uptime is calculated using the following formulae over the last period (90 days): > **Uptime** = (Total minutes over the period – **Total Incidents minutes** over the period) x 100 / Total minutes over the period where: > **Total Incidents minutes** = sum("**Major**" incident minutes) + 30% * sum("**Partial**" incidents minutes) + 30% * sum("**Minor**" incidents minutes) For each incident, duration is expressed by the delta between the time of occurence (as reported or most commonly diagnosed by our monitoring systems) and the moment where the incident has been mitigated and considered as resolved, all services being restored to a nominal state. We also provide a human-friendly daily representation of our systems daily life, through our color-code chronogram representation where: - **Green** is for a happy day, with less than 1 minute of cumulated incidents leading to downtime. - **Yellow** represents less than 20 minutes of downtime - **Orange** stands for 20 to 40 minutes of cumulated downtime. - **Red** calls for more than 40 minutes of cumulated downtime in a given day. *(degraded state being once again, out of the scope of uptime calculation)* *January 2021*.</p> ]]> Mon, 30 Nov 2020 23:00:00 +0000 https://status.openrainbow.health/incident/ckmbwo0r51278812xlodc7ls3frj https://status.openrainbow.health/incident/ckmbwo0r51278812xlodc7ls3frj