tag:status.universal.nl,2005:/historyUniversal Cloud Status - Incident History2024-03-29T11:43:12+01:00Universal Cloudtag:status.universal.nl,2005:Incident/203955162024-03-29T10:58:01+01:002024-03-29T10:58:01+01:00Network jitter<p><small>Mar <var data-var='date'>29</var>, <var data-var='time'>10:58</var> CET</small><br><strong>Investigating</strong> - We are aware of reports indicating increased network jitter, affecting real-time communications and performance. Our team is actively investigating to resolve this issue promptly.</p>tag:status.universal.nl,2005:Incident/201496032024-03-28T13:33:18+01:002024-03-28T13:33:18+01:00Belangrijke update over de netwerkstabiliteit<p><small>Mar <var data-var='date'>28</var>, <var data-var='time'>13:33</var> CET</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Mar <var data-var='date'> 3</var>, <var data-var='time'>12:50</var> CET</small><br><strong>Identified</strong> - We willen onze klanten en partners informeren over recente gebeurtenissen die de stabiliteit van ons netwerk hebben beïnvloed. In de afgelopen periode hebben we een toename waargenomen in het aantal DDoS-aanvallen gericht op onze DNS-servers. Deze trend is niet uniek voor ons; soortgelijke activiteiten zijn gemeld door andere organisaties. De intensiteit van de recente aanvallen heeft echter geleid tot een korte onderbreking van onze dienstverlening.<br /><br />We hebben onmiddellijk samengewerkt met onze netwerkbeheerders om extra veiligheidsmaatregelen te implementeren, wat heeft geresulteerd in een stabilisatie van het verkeer. We zijn momenteel bezig met het analyseren van de logbestanden en zullen de relevante informatie delen met de officiële overheidsinstellingen om verdere actie te ondernemen.<br /><br />We begrijpen dat betrouwbaarheid van cruciaal belang is voor onze gebruikers en we zijn toegewijd aan het handhaven van de hoogste niveaus van dienstverlening. We zullen blijven werken aan het verbeteren van onze beveiligingsmaatregelen en het actief monitoren van ons netwerk om dergelijke incidenten in de toekomst te voorkomen.<br /><br />We waarderen uw begrip en geduld in deze kwestie en zullen updates blijven verstrekken als er meer informatie beschikbaar komt.</p>tag:status.universal.nl,2005:Incident/203872842024-03-28T13:24:12+01:002024-03-28T13:24:12+01:00Inbound calling issues<p><small>Mar <var data-var='date'>28</var>, <var data-var='time'>13:24</var> CET</small><br><strong>Resolved</strong> - The issue has been resolved</p><p><small>Mar <var data-var='date'>28</var>, <var data-var='time'>12:24</var> CET</small><br><strong>Investigating</strong> - We are currently investigating the issue that phone numbers located at one of our communication providers are not reachable, we are working with our supplier to solve this issue.</p>tag:status.universal.nl,2005:Incident/202627762024-03-15T11:26:47+01:002024-03-15T11:26:47+01:00Portal authentication issues<p><small>Mar <var data-var='date'>15</var>, <var data-var='time'>11:26</var> CET</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Mar <var data-var='date'>15</var>, <var data-var='time'>10:50</var> CET</small><br><strong>Identified</strong> - The issue has been identified and a fix is being implemented.</p><p><small>Mar <var data-var='date'>15</var>, <var data-var='time'>10:50</var> CET</small><br><strong>Investigating</strong> - A certificate renewal is causing authentication issues. Our engineers are aware of the problem and working on a solution.</p>tag:status.universal.nl,2005:Incident/200198942024-02-19T13:45:00+01:002024-02-19T13:45:00+01:00Teams presence status<p><small>Feb <var data-var='date'>19</var>, <var data-var='time'>13:45</var> CET</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Feb <var data-var='date'>19</var>, <var data-var='time'>12:59</var> CET</small><br><strong>Monitoring</strong> - We see signs of recovery, where presence is updated for 10% of the users. We expect full recovery within next 30min.</p><p><small>Feb <var data-var='date'>19</var>, <var data-var='time'>12:40</var> CET</small><br><strong>Identified</strong> - Currently there seems to be an issue with fetching a user’s presence using Microsoft GraphAPI, resulting in an offline status for each user so visitors receive a message that no agent is available.</p>tag:status.universal.nl,2005:Incident/199479732024-02-09T17:25:49+01:002024-02-09T17:25:49+01:00Teams issues<p><small>Feb <var data-var='date'> 9</var>, <var data-var='time'>17:25</var> CET</small><br><strong>Resolved</strong> - Our phone provider confirmed they resolved the issue.</p><p><small>Feb <var data-var='date'> 9</var>, <var data-var='time'>15:07</var> CET</small><br><strong>Monitoring</strong> - We are waiting for the primary route to restore.</p><p><small>Feb <var data-var='date'> 9</var>, <var data-var='time'>14:50</var> CET</small><br><strong>Investigating</strong> - Initial Report [10:51 AM] We identified an issue where callers using Microsoft Teams could be heard by the recipients, but the recipients' responses were not audible to the callers. We began our investigation immediately and have been working diligently to identify the root cause.<br /> <br />Further Analysis [11:11 AM] Our team has confirmed that the issue is present across all versions of Microsoft Teams, including desktop, mobile, and web applications. We have checked the Microsoft 365 Status and other outage reporting platforms, which currently do not show widespread reports of this issue. Additionally, no relevant incidents have been reported in the Microsoft 365 Admin Center, apart from a PSTN issue from two weeks ago, for which the recommended reboot did not resolve our current problem.<br /> <br />We have encountered difficulties updating our Universal Status page due to credentials. We are seeking assistance to update the page and will review our process for handling such updates.<br /> <br />Technical Investigation [11:19 AM] Our technical team has reviewed the infrastructure and conducted traces. The media (audio) streams are being transmitted, which suggests that the issue may lie with Microsoft's services. We have reported the problem to Microsoft.<br /> <br />Signs of Recovery [11:42 AM] Some users are beginning to report successful calls, indicating partial service restoration. However, we have not yet received official confirmation from Microsoft regarding the resolution of the issue.<br /> <br />External Factors [11:58 AM] No changes were made on our side before or after the issue was first reported. Our investigation indicates that similar issues have occurred outside our platform and Microsoft's, affecting calls between various telecom providers, including Vodafone-Ziggo, T-Mobile, and KPN. Notably, there was a spike in outage reports for KPN and Vodafone-Ziggo coinciding with the timing of our service disruptions, pointing to a possible network-related issue.<br /> <br />Communication to Customers [11:59 AM] Please use this information as a preliminary explanation for our customers. We consider the troubleshooting efforts related to this incident to be billable.<br /> <br />IVR Unresponsiveness [12:57 PM] Further investigation has revealed that Interactive Voice Response (IVR) systems are unresponsive when entering numbers. Our support line has become unreachable as a result.<br /> <br />Telephone Provider Service Disruption [13:20 PM] It appears that there is a service disruption with our telephone provider, as indicated by our server logs and the inability to place outbound calls through their network. We have contacted our provider, and they have acknowledged the audio issues from this morning. They are currently not aware of the full extent of the current issues, but we have escalated the matter for urgent investigation.<br /> <br />Alternate Contact Number [14:10 PM] Our secondary support number (026 8080135) is operational and can be used to reach Universal IT support. This line is routed through an alternative route, which confirms that the primary issues are originating from our primary telephone services.</p>tag:status.universal.nl,2005:Incident/198367472024-01-29T11:22:10+01:002024-01-29T11:22:10+01:00Switched Telephone Network (PSTN) calls in the new Microsoft Teams client<p><small>Jan <var data-var='date'>29</var>, <var data-var='time'>11:22</var> CET</small><br><strong>Resolved</strong> - Uses can switch to classic client if they experience call issues.</p><p><small>Jan <var data-var='date'>27</var>, <var data-var='time'>11:53</var> CET</small><br><strong>Monitoring</strong> - Microsoft advises customers to switch to Teams classic client as a workaround</p><p><small>Jan <var data-var='date'>26</var>, <var data-var='time'>11:39</var> CET</small><br><strong>Identified</strong> - Title: Users may be unable to make outbound Public Switched Telephone Network (PSTN) calls in the new Microsoft Teams client<br /><br />Issue origin: Microsoft<br /><br />User impact: Users may be unable to make outbound PSTN calls in the new Microsoft Teams client.<br /><br />Root cause: An API code compatibility issue between the classic Microsoft Teams desktop client and the new Microsoft Teams desktop client that is preventing PSTN call functionality from working as expected when making calls from the People App or Live Person card.<br /><br />More details: See TM710083, in MS 365 Tenant admin</p>tag:status.universal.nl,2005:Incident/192015652023-11-24T08:55:29+01:002023-11-24T08:55:29+01:00Amsterdam Internet Exchange issues<p><small>Nov <var data-var='date'>24</var>, <var data-var='time'>08:55</var> CET</small><br><strong>Resolved</strong> - It’s still not officially confirmed by the AMS-IX that the issue has revolved. Many providers have taken action to re-route traffic via other exchanges. We have not received any more reports from our customers, so we close the case for now.</p><p><small>Nov <var data-var='date'>23</var>, <var data-var='time'>18:24</var> CET</small><br><strong>Monitoring</strong> - A fix has been implemented and we are monitoring the results.</p><p><small>Nov <var data-var='date'>23</var>, <var data-var='time'>11:41</var> CET</small><br><strong>Identified</strong> - We are writing to inform you about a service disruption that has impacted some of our cloud services. This interruption is linked to a recent incident at the Amsterdam Internet Exchange (AMS-IX).<br /><br />Incident Overview:<br /><br />• Incident at AMS-IX: On November 22, from 19:08 to 23:04 CET, AMS-IX experienced a platform incident that affected their customers in Amsterdam.<br /><br />• Current Status: The issue resulted in an outage on their peering platform in Amsterdam. They are actively working to resolve the issue and investigate the root cause.<br /><br />Impact on Our Services:<br />• Some of our services experienced disruptions due to this incident.<br />• We are actively working to ensure all services return to normal operation as traffic stabilizes.<br /><br />Our Actions:<br />• We are in close contact with our network partners to monitor the situation.<br />• Our technical teams are working diligently to mitigate any ongoing impact and to expedite the restoration of full service.<br /><br />What to Expect:<br />• We anticipate intermittent service fluctuations until the AMS-IX platform fully stabilizes.<br />• We will provide updates as more information becomes available or if there are significant changes.<br /><br />Support:<br />• If you have any concerns or need assistance, please reach out to our support team.<br />• We are committed to providing you with the necessary support during this period.<br /><br />More info: <br />https://www.ams-ix.net/ams/outage-on-amsterdam-peering-platform</p>tag:status.universal.nl,2005:Incident/192007252023-11-23T11:13:13+01:002023-11-23T11:13:13+01:00uWallboard Queues<p><small>Nov <var data-var='date'>23</var>, <var data-var='time'>11:13</var> CET</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Nov <var data-var='date'>23</var>, <var data-var='time'>11:12</var> CET</small><br><strong>Update</strong> - We are continuing to investigate this issue.</p><p><small>Nov <var data-var='date'>23</var>, <var data-var='time'>09:55</var> CET</small><br><strong>Investigating</strong> - De queues are currently not loading on the wallboard</p>tag:status.universal.nl,2005:Incident/191955982023-11-22T16:18:22+01:002023-11-22T16:18:22+01:00Unexpected reboot<p><small>Nov <var data-var='date'>22</var>, <var data-var='time'>16:18</var> CET</small><br><strong>Resolved</strong> - All services are running fine again</p><p><small>Nov <var data-var='date'>22</var>, <var data-var='time'>16:17</var> CET</small><br><strong>Update</strong> - We are continuing to work on a fix for this issue.</p><p><small>Nov <var data-var='date'>22</var>, <var data-var='time'>16:16</var> CET</small><br><strong>Identified</strong> - Virtual Machines will automatically failover</p>tag:status.universal.nl,2005:Incident/191359522023-11-16T15:13:13+01:002023-11-16T15:13:13+01:00Users can't access Microsoft Power Apps<p><small>Nov <var data-var='date'>16</var>, <var data-var='time'>15:13</var> CET</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Nov <var data-var='date'>16</var>, <var data-var='time'>11:24</var> CET</small><br><strong>Identified</strong> - Microsoft 365 Incident:<br /><br />Title: Users can't access Microsoft Power Apps<br /><br />User impact: Users may be unable to access Microsoft Power Apps.<br /><br />Current status: We're monitoring the rollback as it propagates through the environment. We can see from telemetry that the service availability is improving as the rollback is progressing.<br /><br />Scope of impact: All users may experience impact.<br /><br />Start time: Thursday, November 16, 2023 at 5:05 AM GMT+1<br /><br />Next update by: Thursday, November 16, 2023 at 12:00 PM GMT+1</p>tag:status.universal.nl,2005:Incident/188390712023-10-19T14:45:24+02:002023-10-19T14:45:24+02:00Teams presence issue<p><small>Oct <var data-var='date'>19</var>, <var data-var='time'>14:45</var> CEST</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Oct <var data-var='date'>18</var>, <var data-var='time'>17:01</var> CEST</small><br><strong>Monitoring</strong> - Our telemetry shows that the presence is stabilizing</p><p><small>Oct <var data-var='date'>18</var>, <var data-var='time'>15:54</var> CEST</small><br><strong>Identified</strong> - We see that for some users the Teams-presence cannot be fetch correctly using the Microsoft GraphAPI. We have openend a ticket at Microsoft.</p><p><small>Oct <var data-var='date'>18</var>, <var data-var='time'>13:35</var> CEST</small><br><strong>Investigating</strong> - We are currently investigating this issue.</p>tag:status.universal.nl,2005:Incident/187775922023-10-18T13:34:26+02:002023-10-18T13:34:26+02:00Network hickup<p><small>Oct <var data-var='date'>18</var>, <var data-var='time'>13:34</var> CEST</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Oct <var data-var='date'>13</var>, <var data-var='time'>12:38</var> CEST</small><br><strong>Monitoring</strong> - Message from our network partner:<br /><br />Packetloss is resolved, we suffered a major outage on one of our main upstreams. Due to the abrupt disconnect, all ongoing concerned sessions were dropped. Our failover kicked in automatically and rerouted traffic. At the moment we deem this upstream unresponsive and have shut it down manually, we will send out an update when the upstream is fixed. For the moment all services should work as intended without ANY issues. If you are currently experiencing any issues please contact us.</p>tag:status.universal.nl,2005:Incident/187457172023-10-11T09:00:55+02:002023-10-11T09:00:55+02:00Network issues<p><small>Oct <var data-var='date'>11</var>, <var data-var='time'>09:00</var> CEST</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Oct <var data-var='date'>10</var>, <var data-var='time'>19:36</var> CEST</small><br><strong>Monitoring</strong> - A fix has been implemented and we are monitoring the results.</p><p><small>Oct <var data-var='date'>10</var>, <var data-var='time'>19:29</var> CEST</small><br><strong>Investigating</strong> - We are currently investigating this issue.</p>tag:status.universal.nl,2005:Incident/186812682023-10-03T23:00:45+02:002023-10-03T23:00:45+02:00Testing DDOS prevention<p><small>Oct <var data-var='date'> 3</var>, <var data-var='time'>23:00</var> CEST</small><br><strong>Completed</strong> - The scheduled maintenance has been completed.</p><p><small>Oct <var data-var='date'> 3</var>, <var data-var='time'>22:02</var> CEST</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Oct <var data-var='date'> 3</var>, <var data-var='time'>21:55</var> CEST</small><br><strong>Scheduled</strong> - We will be testing new DDOS prevention during this planned Window.</p>tag:status.universal.nl,2005:Incident/186750852023-10-03T11:59:02+02:002023-10-04T10:08:44+02:00DDOS attack on our DNS infrastructure.<p><small>Oct <var data-var='date'> 3</var>, <var data-var='time'>11:59</var> CEST</small><br><strong>Resolved</strong> - The log files captured during the attack will be thoroughly analyzed to bolster our defenses against similar threats in the future.</p><p><small>Oct <var data-var='date'> 3</var>, <var data-var='time'>10:55</var> CEST</small><br><strong>Update</strong> - We are continuing to monitor for any further issues.</p><p><small>Oct <var data-var='date'> 3</var>, <var data-var='time'>10:54</var> CEST</small><br><strong>Monitoring</strong> - A fix has been implemented and we are monitoring the results.</p><p><small>Oct <var data-var='date'> 3</var>, <var data-var='time'>09:36</var> CEST</small><br><strong>Investigating</strong> - We are currently experiencing a DDOS attack on our DNS infrastructure.</p>tag:status.universal.nl,2005:Incident/186496292023-09-30T14:58:58+02:002023-09-30T14:58:58+02:00Network connectivity timeouts<p><small>Sep <var data-var='date'>30</var>, <var data-var='time'>14:58</var> CEST</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Sep <var data-var='date'>30</var>, <var data-var='time'>12:33</var> CEST</small><br><strong>Monitoring</strong> - The IP address being attacked by a large number of sessions has been identified and measurements have been taken to reduce traffic.</p><p><small>Sep <var data-var='date'>30</var>, <var data-var='time'>11:24</var> CEST</small><br><strong>Investigating</strong> - We are experiencing network connectivity issues to our datacenter. Existing connections keep working, but new sessions cannot be setup.</p>tag:status.universal.nl,2005:Incident/185982202023-09-25T12:35:51+02:002023-09-25T12:35:51+02:00Teams presence issue<p><small>Sep <var data-var='date'>25</var>, <var data-var='time'>12:35</var> CEST</small><br><strong>Resolved</strong> - TM676996: Microsoft Teams Service Health Notification<br />posted in Universal Standby / Office 365 Service health on September 25, 2023 2:46 AM<br /><br />Issues this morning seems related to above. We have seen recovery of presence in the new Teams client, so closing this incident.</p><p><small>Sep <var data-var='date'>25</var>, <var data-var='time'>09:28</var> CEST</small><br><strong>Investigating</strong> - We have observed potential presence update issues with MS Teams. While these are yet to be officially confirmed by Microsoft, they may impact the functionality of uWebChat/uCallManager's agent hunting feature. Rest assured, we are monitoring the situation closely and will keep you updated as soon as we receive any official communication on this matter.</p>tag:status.universal.nl,2005:Incident/185545402023-09-22T10:00:33+02:002023-09-22T10:00:33+02:00New version publishing<p><small>Sep <var data-var='date'>22</var>, <var data-var='time'>10:00</var> CEST</small><br><strong>Completed</strong> - The current version is updated to: 1.9.5.1<br />https://uwebchat.com/uwebchat-transfer-now-available/</p><p><small>Sep <var data-var='date'>20</var>, <var data-var='time'>12:34</var> CEST</small><br><strong>Scheduled</strong> - https://uwebchat.com/transfer-uwebchat/</p>tag:status.universal.nl,2005:Incident/185337672023-09-21T20:00:33+02:002023-09-21T20:00:33+02:00DNS upgrade<p><small>Sep <var data-var='date'>21</var>, <var data-var='time'>20:00</var> CEST</small><br><strong>Completed</strong> - The scheduled maintenance has been completed.</p><p><small>Sep <var data-var='date'>21</var>, <var data-var='time'>19:01</var> CEST</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Sep <var data-var='date'>18</var>, <var data-var='time'>12:35</var> CEST</small><br><strong>Scheduled</strong> - We announce a planned upgrade to our DNS software, aimed at further enhancing security and performance.<br /><br />Thanks to our high availability infrastructure, we will be upgrading servers sequentially, one by one, to ensure a smooth transition with no expected downtime</p>tag:status.universal.nl,2005:Incident/184575852023-09-10T16:28:57+02:002023-09-10T16:28:57+02:00Internet connectivity<p><small>Sep <var data-var='date'>10</var>, <var data-var='time'>16:28</var> CEST</small><br><strong>Resolved</strong> - Firmware upgrade completed.</p><p><small>Sep <var data-var='date'>10</var>, <var data-var='time'>16:14</var> CEST</small><br><strong>Monitoring</strong> - A fix has been implemented and we are monitoring the results.</p><p><small>Sep <var data-var='date'>10</var>, <var data-var='time'>14:38</var> CEST</small><br><strong>Investigating</strong> - We are currently investigating this issue.</p>tag:status.universal.nl,2005:Incident/184060432023-09-06T12:47:49+02:002023-09-06T12:47:49+02:00MS Teams calling<p><small>Sep <var data-var='date'> 6</var>, <var data-var='time'>12:47</var> CEST</small><br><strong>Resolved</strong> - Customer feedback confirms Microsoft has resolved the issue.</p><p><small>Sep <var data-var='date'> 6</var>, <var data-var='time'>11:12</var> CEST</small><br><strong>Identified</strong> - UPDATE FROM Microsoft: Title: Users may be unable to make or receive Public Switched Telephone Network (PSTN) calls in Microsoft Teams<br /><br />User impact: Users may be unable to make or receive PSTN calls in Microsoft Teams.<br /><br />Current status: We're reviewing service monitoring telemetry to isolate the source of the issue and establish a fix.<br /><br />Scope of impact: Impact is specific to some users who are served through the Europe, Middle East, and Africa region.<br /><br />Next update by: Wednesday, September 6, 2023 at 1:00 PM GMT+2</p><p><small>Sep <var data-var='date'> 6</var>, <var data-var='time'>11:06</var> CEST</small><br><strong>Investigating</strong> - We have been notified by several users experiencing difficulties accepting Teams calls via uCallManager. At this moment, there are no known issues on our platform. However, we have observed nationwide reports related to Teams. We are currently awaiting official communication from Microsoft on the matter</p>tag:status.universal.nl,2005:Incident/183795652023-09-04T17:02:14+02:002023-09-21T10:08:49+02:00Network timeouts<p><small>Sep <var data-var='date'> 4</var>, <var data-var='time'>17:02</var> CEST</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Sep <var data-var='date'> 4</var>, <var data-var='time'>12:27</var> CEST</small><br><strong>Monitoring</strong> - We will analyze logfiles and publish RCA when available.</p><p><small>Sep <var data-var='date'> 4</var>, <var data-var='time'>09:09</var> CEST</small><br><strong>Update</strong> - We are continuing to investigate this issue.</p><p><small>Sep <var data-var='date'> 4</var>, <var data-var='time'>09:05</var> CEST</small><br><strong>Update</strong> - We are continuing to investigate this issue.</p><p><small>Sep <var data-var='date'> 4</var>, <var data-var='time'>09:04</var> CEST</small><br><strong>Investigating</strong> - We experienced a network issue that might have impacted your services. Our monitoring systems detected packet-loss between 05:05am - 06:25am.<br /><br />Please note that we prioritize the quality and reliability of our services, and we're actively working with our network partner to ascertain the root cause of this occurrence. We have requested further clarification and will update you as soon as we have more information.</p>tag:status.universal.nl,2005:Incident/177714172023-07-05T21:43:32+02:002023-07-05T21:43:32+02:00Azure - Networking - West Europe -Applying Mitigation<p><small>Jul <var data-var='date'> 5</var>, <var data-var='time'>21:43</var> CEST</small><br><strong>Resolved</strong> - Microsoft confirmed that network has recovered</p><p><small>Jul <var data-var='date'> 5</var>, <var data-var='time'>17:44</var> CEST</small><br><strong>Monitoring</strong> - A fix has been implemented and we are monitoring the results.</p><p><small>Jul <var data-var='date'> 5</var>, <var data-var='time'>16:47</var> CEST</small><br><strong>Investigating</strong> - https://azure.status.microsoft/nl-nl/status</p>tag:status.universal.nl,2005:Incident/172537762023-05-15T14:44:21+02:002023-05-15T14:44:21+02:00Cluster failover<p><small>May <var data-var='date'>15</var>, <var data-var='time'>14:44</var> CEST</small><br><strong>Resolved</strong> - VM's will return to their original host in the next few hours</p><p><small>May <var data-var='date'>15</var>, <var data-var='time'>13:19</var> CEST</small><br><strong>Monitoring</strong> - A fix has been implemented and we are monitoring the results.</p><p><small>May <var data-var='date'>15</var>, <var data-var='time'>13:19</var> CEST</small><br><strong>Identified</strong> - An unplanned failover of one of the cluster nodes, caused some VM’s to failover.</p>