Snapshot 320038

Document
Registry listing
URL
https://status.luware.com/history.rss
Fetched
HTTP status
200
Content type
text/xml
Fetch mode
api
Size
150398 bytes
SHA-256 (raw)
eb01c8ddcba31afb44f80c0f641656510b6cc8c437833283d41095eb8316d7cc
SHA-256 (normalized text)
8ffcbce8ed4ceb9139c4d9e07cb60ed7920d8c3993bedc439c18abf2de388acf

Raw (normalized text)

Scripts and page chrome removed; this is what change detection compares.

<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
<title>Luware Status - Incident history</title>
<link>https://status.luware.com</link>
<description>Luware</description>
<pubDate>Sun, 13 Dec 2026 06:00:00 +0000</pubDate>
<item>
<title>Nimbus DE-01 Scheduled Maintenance</title>
<description>
Type: Maintenance
Affected Components: Nimbus App, User Portal, Microsoft Service Health, Call Handling, User Availability, Attendant Console, Admin Portal, Historical Reports via PowerBI
Nov 16, 15:13:06 GMT+0 - Identified - As part of our continuous commitment to providing high-quality service, we will be performing **upgrade maintenance** on the **DE-01 cluster**.
**Expected Impact:**
We do **not** anticipate any downtime during this activity. You can continue using your Nimbus services as normal.
**Questions or Assistance?**
Please contact us via our Helpdesk: &lt;https://helpdesk.luware.cloud&gt;
**Post-Maintenance Details:**
A full rundown of the changes will be published on our Knowledge Base after completion:
&lt;https://help.luware.com&gt;
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Maintenance</p>
<p><strong>Affected Components:</strong> </p>
<p><small>Nov <var data-var='date'> 16</var>, <var data-var='time'>15:13:06</var> GMT+0</small><br><strong>Identified</strong> -
As part of our continuous commitment to providing high-quality service, we will be performing **upgrade maintenance** on the **DE-01 cluster**.
**Expected Impact:**
We do **not** anticipate any downtime during this activity. You can continue using your Nimbus services as normal.
**Questions or Assistance?**
Please contact us via our Helpdesk: &lt;https://helpdesk.luware.cloud&gt;
**Post-Maintenance Details:**
A full rundown of the changes will be published on our Knowledge Base after completion:
&lt;https://help.luware.com&gt;.</p>
]]>
</content:encoded>
<pubDate>Sun, 13 Dec 2026 06:00:00 +0000</pubDate>
<link>https://status.luware.com/maintenance/cmwjeks9q009t13qq8mm26jjr</link>
<guid>https://status.luware.com/maintenance/cmwjeks9q009t13qq8mm26jjr</guid>
</item>
<item>
<title>Nimbus EU-01 Scheduled Maintenance</title>
<description>
Type: Maintenance
Affected Components: Historical Reports via PowerBI, Nimbus App, Admin Portal, User Availability, Attendant Console, Microsoft Service Health, Call Handling
Nov 16, 15:12:00 GMT+0 - Identified - As part of our continuous commitment to providing high-quality service, we will be performing **upgrade maintenance** on the **EU-01 cluster**.
**Expected Impact:**
We do **not** anticipate any downtime during this activity. You can continue using your Nimbus services as normal.
**Questions or Assistance?**
Please contact us via our Helpdesk: &lt;https://helpdesk.luware.cloud&gt;
**Post-Maintenance Details:**
A full rundown of the changes will be published on our Knowledge Base after completion:
&lt;https://help.luware.com&gt;
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Maintenance</p>
<p><strong>Affected Components:</strong> </p>
<p><small>Nov <var data-var='date'> 16</var>, <var data-var='time'>15:12:00</var> GMT+0</small><br><strong>Identified</strong> -
As part of our continuous commitment to providing high-quality service, we will be performing **upgrade maintenance** on the **EU-01 cluster**.
**Expected Impact:**
We do **not** anticipate any downtime during this activity. You can continue using your Nimbus services as normal.
**Questions or Assistance?**
Please contact us via our Helpdesk: &lt;https://helpdesk.luware.cloud&gt;
**Post-Maintenance Details:**
A full rundown of the changes will be published on our Knowledge Base after completion:
&lt;https://help.luware.com&gt;.</p>
]]>
</content:encoded>
<pubDate>Wed, 9 Dec 2026 18:00:00 +0000</pubDate>
<link>https://status.luware.com/maintenance/cmwjejdmy004v13m3cypvn6mv</link>
<guid>https://status.luware.com/maintenance/cmwjejdmy004v13m3cypvn6mv</guid>
</item>
<item>
<title>Nimbus CH-01 Scheduled Maintenance</title>
<description>
Type: Maintenance
Affected Components: Call Handling, Attendant Console, Microsoft Service Health, User Portal, Historical Reports via PowerBI, Admin Portal, User Availability, Nimbus App
Nov 16, 15:10:12 GMT+0 - Identified - As part of our continuous commitment to providing high-quality service, we will be performing **upgrade maintenance** on the **CH-01 cluster**.
**Expected Impact:**
We do **not** anticipate any downtime during this activity. You can continue using your Nimbus services as normal.
**Questions or Assistance?**
Please contact us via our Helpdesk: &lt;https://helpdesk.luware.cloud&gt;
**Post-Maintenance Details:**
A full rundown of the changes will be published on our Knowledge Base after completion:
&lt;https://help.luware.com&gt;
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Maintenance</p>
<p><strong>Affected Components:</strong> </p>
<p><small>Nov <var data-var='date'> 16</var>, <var data-var='time'>15:10:12</var> GMT+0</small><br><strong>Identified</strong> -
As part of our continuous commitment to providing high-quality service, we will be performing **upgrade maintenance** on the **CH-01 cluster**.
**Expected Impact:**
We do **not** anticipate any downtime during this activity. You can continue using your Nimbus services as normal.
**Questions or Assistance?**
Please contact us via our Helpdesk: &lt;https://helpdesk.luware.cloud&gt;
**Post-Maintenance Details:**
A full rundown of the changes will be published on our Knowledge Base after completion:
&lt;https://help.luware.com&gt;.</p>
]]>
</content:encoded>
<pubDate>Sun, 6 Dec 2026 06:00:00 +0000</pubDate>
<link>https://status.luware.com/maintenance/cmwjeh286008a13qqgv73nt8p</link>
<guid>https://status.luware.com/maintenance/cmwjeh286008a13qqgv73nt8p</guid>
</item>
<item>
<title>Nimbus CH-02 and DE-02 Scheduled Maintenance</title>
<description>
Type: Maintenance
Affected Components: Call Handling, User Portal, Admin Portal, Historical Reports via PowerBI, Microsoft Service Health, User Availability, User Availability, Historical Reports via PowerBI, Nimbus App, Attendant Console, Call Handling, Nimbus App, Attendant Console, Admin Portal, Microsoft Service Health
Nov 16, 15:09:13 GMT+0 - Identified - As part of our continuous commitment to providing high-quality service, we will be performing **upgrade maintenance** on the **CH-02 and DE-02 clusters**.
**Expected Impact:**
We do **not** anticipate any downtime during this activity. You can continue using your Nimbus services as normal.
**Questions or Assistance?**
Please contact us via our Helpdesk: &lt;https://helpdesk.luware.cloud&gt;
**Post-Maintenance Details:**
A full rundown of the changes will be published on our Knowledge Base after completion:
&lt;https://help.luware.com&gt;
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Maintenance</p>
<p><strong>Affected Components:</strong> </p>
<p><small>Nov <var data-var='date'> 16</var>, <var data-var='time'>15:09:13</var> GMT+0</small><br><strong>Identified</strong> -
As part of our continuous commitment to providing high-quality service, we will be performing **upgrade maintenance** on the **CH-02 and DE-02 clusters**.
**Expected Impact:**
We do **not** anticipate any downtime during this activity. You can continue using your Nimbus services as normal.
**Questions or Assistance?**
Please contact us via our Helpdesk: &lt;https://helpdesk.luware.cloud&gt;
**Post-Maintenance Details:**
A full rundown of the changes will be published on our Knowledge Base after completion:
&lt;https://help.luware.com&gt;.</p>
]]>
</content:encoded>
<pubDate>Thu, 3 Dec 2026 18:00:00 +0000</pubDate>
<link>https://status.luware.com/maintenance/cmwjefscv00570wqqefuxw3c7</link>
<guid>https://status.luware.com/maintenance/cmwjefscv00570wqqefuxw3c7</guid>
</item>
<item>
<title>Nimbus UK-01 Scheduled Maintenance</title>
<description>
Type: Maintenance
Affected Components: User Availability, Attendant Console, Historical Reports via PowerBI, Call Handling, Nimbus App, Microsoft Service Health, Admin Portal
Nov 16, 15:07:33 GMT+0 - Identified - As part of our continuous commitment to providing high-quality service, we will be performing **upgrade maintenance** on the **UK-01 cluster**.
**Expected Impact:**
We do **not** anticipate any downtime during this activity. You can continue using your Nimbus services as normal.
**Questions or Assistance?**
Please contact us via our Helpdesk: &lt;https://helpdesk.luware.cloud&gt;
**Post-Maintenance Details:**
A full rundown of the changes will be published on our Knowledge Base after completion:
&lt;https://help.luware.com&gt;
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Maintenance</p>
<p><strong>Affected Components:</strong> </p>
<p><small>Nov <var data-var='date'> 16</var>, <var data-var='time'>15:07:33</var> GMT+0</small><br><strong>Identified</strong> -
As part of our continuous commitment to providing high-quality service, we will be performing **upgrade maintenance** on the **UK-01 cluster**.
**Expected Impact:**
We do **not** anticipate any downtime during this activity. You can continue using your Nimbus services as normal.
**Questions or Assistance?**
Please contact us via our Helpdesk: &lt;https://helpdesk.luware.cloud&gt;
**Post-Maintenance Details:**
A full rundown of the changes will be published on our Knowledge Base after completion:
&lt;https://help.luware.com&gt;.</p>
]]>
</content:encoded>
<pubDate>Tue, 1 Dec 2026 18:00:00 +0000</pubDate>
<link>https://status.luware.com/maintenance/cmwjedn4t003m13m3f30khcn3</link>
<guid>https://status.luware.com/maintenance/cmwjedn4t003m13m3f30khcn3</guid>
</item>
<item>
<title>Nimbus AU-01 Scheduled Maintenance</title>
<description>
Type: Maintenance
Affected Components: Attendant Console, Nimbus App, Call Handling, Historical Reports via PowerBI, Microsoft Service Health, Admin Portal, User Availability, User Portal
Nov 16, 15:06:18 GMT+0 - Identified - As part of our continuous commitment to providing high-quality service, we will be performing **upgrade maintenance** on the **AU-01 cluster**.
**Expected Impact:**
We do **not** anticipate any downtime during this activity. You can continue using your Nimbus services as normal.
**Questions or Assistance?**
Please contact us via our Helpdesk: &lt;https://helpdesk.luware.cloud&gt;
**Post-Maintenance Details:**
A full rundown of the changes will be published on our Knowledge Base after completion:
&lt;https://help.luware.com&gt;
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Maintenance</p>
<p><strong>Affected Components:</strong> </p>
<p><small>Nov <var data-var='date'> 16</var>, <var data-var='time'>15:06:18</var> GMT+0</small><br><strong>Identified</strong> -
As part of our continuous commitment to providing high-quality service, we will be performing **upgrade maintenance** on the **AU-01 cluster**.
**Expected Impact:**
We do **not** anticipate any downtime during this activity. You can continue using your Nimbus services as normal.
**Questions or Assistance?**
Please contact us via our Helpdesk: &lt;https://helpdesk.luware.cloud&gt;
**Post-Maintenance Details:**
A full rundown of the changes will be published on our Knowledge Base after completion:
&lt;https://help.luware.com&gt;.</p>
]]>
</content:encoded>
<pubDate>Thu, 26 Nov 2026 12:00:00 +0000</pubDate>
<link>https://status.luware.com/maintenance/cmwjec1f500gj0wt0a47zsb32</link>
<guid>https://status.luware.com/maintenance/cmwjec1f500gj0wt0a47zsb32</guid>
</item>
<item>
<title>Nimbus US-01 Scheduled Maintenance</title>
<description>
Type: Maintenance
Affected Components: Historical Reports via PowerBI, Call Handling, Nimbus App, Attendant Console, User Availability, User Availability, Admin Portal, Microsoft Service Health
Nov 16, 15:03:00 GMT+0 - Identified - As part of our continuous commitment to providing high-quality service, we will be performing **upgrade maintenance** on the **US-01 cluster**.
**Expected Impact:**
We do **not** anticipate any downtime during this activity. You can continue using your Nimbus services as normal.
**Questions or Assistance?**
Please contact us via our Helpdesk: &lt;https://helpdesk.luware.cloud&gt;
**Post-Maintenance Details:**
A full rundown of the changes will be published on our Knowledge Base after completion:
&lt;https://help.luware.com&gt;
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Maintenance</p>
<p><strong>Affected Components:</strong> </p>
<p><small>Nov <var data-var='date'> 16</var>, <var data-var='time'>15:03:00</var> GMT+0</small><br><strong>Identified</strong> -
As part of our continuous commitment to providing high-quality service, we will be performing **upgrade maintenance** on the **US-01 cluster**.
**Expected Impact:**
We do **not** anticipate any downtime during this activity. You can continue using your Nimbus services as normal.
**Questions or Assistance?**
Please contact us via our Helpdesk: &lt;https://helpdesk.luware.cloud&gt;
**Post-Maintenance Details:**
A full rundown of the changes will be published on our Knowledge Base after completion:
&lt;https://help.luware.com&gt;.</p>
]]>
</content:encoded>
<pubDate>Wed, 25 Nov 2026 09:00:00 +0000</pubDate>
<link>https://status.luware.com/maintenance/cmwje7stn00aj13t0g0rhnoe6</link>
<guid>https://status.luware.com/maintenance/cmwje7stn00aj13t0g0rhnoe6</guid>
</item>
<item>
<title>Nimbus DE-01 Scheduled Maintenance</title>
<description>
Type: Maintenance
Affected Components: Nimbus App, User Portal, Call Handling, Microsoft Service Health, User Availability, Attendant Console, Admin Portal, Historical Reports via PowerBI
Oct 26, 13:32:51 GMT+0 - Identified - As part of our continuous commitment to providing high-quality service, we will be performing **upgrade maintenance** on the **DE-01 cluster**.
**Expected Impact:**
We do **not** anticipate any downtime during this activity. You can continue using your Nimbus services as normal.
**Questions or Assistance?**
Please contact us via our Helpdesk: &lt;https://helpdesk.luware.cloud&gt;
**Post-Maintenance Details:**
A full rundown of the changes will be published on our Knowledge Base after completion:
&lt;https://help.luware.com&gt;
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Maintenance</p>
<p><strong>Affected Components:</strong> </p>
<p><small>Oct <var data-var='date'> 26</var>, <var data-var='time'>13:32:51</var> GMT+0</small><br><strong>Identified</strong> -
As part of our continuous commitment to providing high-quality service, we will be performing **upgrade maintenance** on the **DE-01 cluster**.
**Expected Impact:**
We do **not** anticipate any downtime during this activity. You can continue using your Nimbus services as normal.
**Questions or Assistance?**
Please contact us via our Helpdesk: &lt;https://helpdesk.luware.cloud&gt;
**Post-Maintenance Details:**
A full rundown of the changes will be published on our Knowledge Base after completion:
&lt;https://help.luware.com&gt;.</p>
]]>
</content:encoded>
<pubDate>Sun, 22 Nov 2026 06:00:00 +0000</pubDate>
<link>https://status.luware.com/maintenance/cmvpaqyuc01kw1bpcwongzowe</link>
<guid>https://status.luware.com/maintenance/cmvpaqyuc01kw1bpcwongzowe</guid>
</item>
<item>
<title>Luware Recording MTDE Scheduled Maintenance</title>
<description>
Type: Maintenance
Duration: 10 hours
Affected Components: Microsoft Service Health, Speech Analytics, Storage Services, Web applications, Media Playback, Call Recording, Search &amp; Retrieval
Nov 21, 17:00:00 GMT+0 - Completed - Maintenance has completed successfully Nov 21, 07:00:01 GMT+0 - Identified - Maintenance is now in progress Oct 29, 14:27:19 GMT+0 - Identified - As part of our continuous commitment to providing high-quality service, we will be performing **upgrade maintenance** on the **Luware Recording MTDE cluster** on **Sat 21st Nov 2026.**
**Expected Impact:**
We do **not** anticipate any downtime during this activity. You can continue using your Luware Recording services as normal.
**Questions or Assistance?**
Please contact us via our Helpdesk: &lt;https://helpdesk.luware.cloud&gt;
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Maintenance</p>
<p><strong>Duration:</strong> 10 hours</p>
<p><strong>Affected Components:</strong> </p>
<p><small>Nov <var data-var='date'> 21</var>, <var data-var='time'>17:00:00</var> GMT+0</small><br><strong>Completed</strong> -
Maintenance has completed successfully.</p>
<p><small>Nov <var data-var='date'> 21</var>, <var data-var='time'>07:00:01</var> GMT+0</small><br><strong>Identified</strong> -
Maintenance is now in progress.</p>
<p><small>Oct <var data-var='date'> 29</var>, <var data-var='time'>14:27:19</var> GMT+0</small><br><strong>Identified</strong> -
As part of our continuous commitment to providing high-quality service, we will be performing **upgrade maintenance** on the **Luware Recording MTDE cluster** on **Sat 21st Nov 2026.**
**Expected Impact:**
We do **not** anticipate any downtime during this activity. You can continue using your Luware Recording services as normal.
**Questions or Assistance?**
Please contact us via our Helpdesk: &lt;https://helpdesk.luware.cloud&gt;.</p>
]]>
</content:encoded>
<pubDate>Sat, 21 Nov 2026 07:00:00 +0000</pubDate>
<link>https://status.luware.com/maintenance/cmvtn0k8x00jw13phhe6o0ptc</link>
<guid>https://status.luware.com/maintenance/cmvtn0k8x00jw13phhe6o0ptc</guid>
</item>
<item>
<title>Nimbus EU-01 Scheduled Maintenance</title>
<description>
Type: Maintenance
Duration: 3 hours
Affected Components: Historical Reports via PowerBI, Nimbus App, Admin Portal, User Availability, Attendant Console, Microsoft Service Health, Call Handling
Nov 18, 21:00:00 GMT+0 - Completed - Maintenance has completed successfully Nov 18, 18:00:01 GMT+0 - Identified - Maintenance is now in progress Oct 26, 13:31:30 GMT+0 - Identified - As part of our continuous commitment to providing high-quality service, we will be performing **upgrade maintenance** on the **EU-01 cluster**.
**Expected Impact:**
We do **not** anticipate any downtime during this activity. You can continue using your Nimbus services as normal.
**Questions or Assistance?**
Please contact us via our Helpdesk: &lt;https://helpdesk.luware.cloud&gt;
**Post-Maintenance Details:**
A full rundown of the changes will be published on our Knowledge Base after completion:
&lt;https://help.luware.com&gt;
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Maintenance</p>
<p><strong>Duration:</strong> 3 hours</p>
<p><strong>Affected Components:</strong> </p>
<p><small>Nov <var data-var='date'> 18</var>, <var data-var='time'>21:00:00</var> GMT+0</small><br><strong>Completed</strong> -
Maintenance has completed successfully.</p>
<p><small>Nov <var data-var='date'> 18</var>, <var data-var='time'>18:00:01</var> GMT+0</small><br><strong>Identified</strong> -
Maintenance is now in progress.</p>
<p><small>Oct <var data-var='date'> 26</var>, <var data-var='time'>13:31:30</var> GMT+0</small><br><strong>Identified</strong> -
As part of our continuous commitment to providing high-quality service, we will be performing **upgrade maintenance** on the **EU-01 cluster**.
**Expected Impact:**
We do **not** anticipate any downtime during this activity. You can continue using your Nimbus services as normal.
**Questions or Assistance?**
Please contact us via our Helpdesk: &lt;https://helpdesk.luware.cloud&gt;
**Post-Maintenance Details:**
A full rundown of the changes will be published on our Knowledge Base after completion:
&lt;https://help.luware.com&gt;.</p>
]]>
</content:encoded>
<pubDate>Wed, 18 Nov 2026 18:00:00 +0000</pubDate>
<link>https://status.luware.com/maintenance/cmvpap8a001qf1mpc7wdy1byy</link>
<guid>https://status.luware.com/maintenance/cmvpap8a001qf1mpc7wdy1byy</guid>
</item>
<item>
<title>Nimbus EU-01 Scheduled Maintenance</title>
<description>
Type: Maintenance
Duration: 2 hours
Affected Components: Historical Reports via PowerBI, Nimbus App, Admin Portal, User Availability, Attendant Console, Microsoft Service Health, Call Handling
Nov 14, 11:00:00 GMT+0 - Completed - Maintenance has completed successfully Nov 14, 09:00:01 GMT+0 - Identified - Maintenance is now in progress Nov 11, 18:30:20 GMT+0 - Identified - As part of our continuous commitment to providing high-quality service, we will be performing **upgrade maintenance** on the **EU-01 cluster**.
**Expected Impact:**
We do **not** anticipate any downtime during this activity. You can continue using your Nimbus services as normal.
**Questions or Assistance?**
Please contact us via our Helpdesk: &lt;https://helpdesk.luware.cloud&gt;
**Post-Maintenance Details:**
A full rundown of the changes will be published on our Knowledge Base after completion:
&lt;https://help.luware.com&gt;
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Maintenance</p>
<p><strong>Duration:</strong> 2 hours</p>
<p><strong>Affected Components:</strong> </p>
<p><small>Nov <var data-var='date'> 14</var>, <var data-var='time'>11:00:00</var> GMT+0</small><br><strong>Completed</strong> -
Maintenance has completed successfully.</p>
<p><small>Nov <var data-var='date'> 14</var>, <var data-var='time'>09:00:01</var> GMT+0</small><br><strong>Identified</strong> -
Maintenance is now in progress.</p>
<p><small>Nov <var data-var='date'> 11</var>, <var data-var='time'>18:30:20</var> GMT+0</small><br><strong>Identified</strong> -
As part of our continuous commitment to providing high-quality service, we will be performing **upgrade maintenance** on the **EU-01 cluster**.
**Expected Impact:**
We do **not** anticipate any downtime during this activity. You can continue using your Nimbus services as normal.
**Questions or Assistance?**
Please contact us via our Helpdesk: &lt;https://helpdesk.luware.cloud&gt;
**Post-Maintenance Details:**
A full rundown of the changes will be published on our Knowledge Base after completion:
&lt;https://help.luware.com&gt;.</p>
]]>
</content:encoded>
<pubDate>Sat, 14 Nov 2026 09:00:00 +0000</pubDate>
<link>https://status.luware.com/maintenance/cmwcgf5ox038b1bp67kb1mbrn</link>
<guid>https://status.luware.com/maintenance/cmwcgf5ox038b1bp67kb1mbrn</guid>
</item>
<item>
<title>Nimbus DE-01 Scheduled Maintenance</title>
<description>
Type: Maintenance
Duration: 2 hours
Affected Components: Nimbus App, User Portal, Microsoft Service Health, Call Handling, User Availability, Attendant Console, Admin Portal, Historical Reports via PowerBI
Nov 14, 09:00:00 GMT+0 - Completed - Maintenance has completed successfully Nov 14, 07:00:01 GMT+0 - Identified - Maintenance is now in progress Nov 11, 18:28:03 GMT+0 - Identified - As part of our continuous commitment to providing high-quality service, we will be performing **upgrade maintenance** on the **DE-01 cluster**.
**Expected Impact:**
We do **not** anticipate any downtime during this activity. You can continue using your Nimbus services as normal.
**Questions or Assistance?**
Please contact us via our Helpdesk: &lt;https://helpdesk.luware.cloud&gt;
**Post-Maintenance Details:**
A full rundown of the changes will be published on our Knowledge Base after completion:
&lt;https://help.luware.com&gt;
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Maintenance</p>
<p><strong>Duration:</strong> 2 hours</p>
<p><strong>Affected Components:</strong> </p>
<p><small>Nov <var data-var='date'> 14</var>, <var data-var='time'>09:00:00</var> GMT+0</small><br><strong>Completed</strong> -
Maintenance has completed successfully.</p>
<p><small>Nov <var data-var='date'> 14</var>, <var data-var='time'>07:00:01</var> GMT+0</small><br><strong>Identified</strong> -
Maintenance is now in progress.</p>
<p><small>Nov <var data-var='date'> 11</var>, <var data-var='time'>18:28:03</var> GMT+0</small><br><strong>Identified</strong> -
As part of our continuous commitment to providing high-quality service, we will be performing **upgrade maintenance** on the **DE-01 cluster**.
**Expected Impact:**
We do **not** anticipate any downtime during this activity. You can continue using your Nimbus services as normal.
**Questions or Assistance?**
Please contact us via our Helpdesk: &lt;https://helpdesk.luware.cloud&gt;
**Post-Maintenance Details:**
A full rundown of the changes will be published on our Knowledge Base after completion:
&lt;https://help.luware.com&gt;.</p>
]]>
</content:encoded>
<pubDate>Sat, 14 Nov 2026 07:00:00 +0000</pubDate>
<link>https://status.luware.com/maintenance/cmwcgc81x02b10wjyqbs4dk8v</link>
<guid>https://status.luware.com/maintenance/cmwcgc81x02b10wjyqbs4dk8v</guid>
</item>
<item>
<title>Nimbus UK-01 Scheduled Maintenance</title>
<description>
Type: Maintenance
Duration: 2 hours
Affected Components: User Availability, Attendant Console, Historical Reports via PowerBI, Call Handling, Nimbus App, Microsoft Service Health, Admin Portal
Nov 14, 09:00:00 GMT+0 - Completed - Maintenance has completed successfully Nov 14, 07:00:01 GMT+0 - Identified - Maintenance is now in progress Nov 12, 17:47:29 GMT+0 - Identified - As part of our continuous commitment to providing high-quality service, we will be performing **upgrade maintenance** on the **UK-01 cluster**.
**Expected Impact:**
We do **not** anticipate any downtime during this activity. You can continue using your Nimbus services as normal.
**Questions or Assistance?**
Please contact us via our Helpdesk: &lt;https://helpdesk.luware.cloud&gt;
**Post-Maintenance Details:**
A full rundown of the changes will be published on our Knowledge Base after completion:
&lt;https://help.luware.com&gt;
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Maintenance</p>
<p><strong>Duration:</strong> 2 hours</p>
<p><strong>Affected Components:</strong> </p>
<p><small>Nov <var data-var='date'> 14</var>, <var data-var='time'>09:00:00</var> GMT+0</small><br><strong>Completed</strong> -
Maintenance has completed successfully.</p>
<p><small>Nov <var data-var='date'> 14</var>, <var data-var='time'>07:00:01</var> GMT+0</small><br><strong>Identified</strong> -
Maintenance is now in progress.</p>
<p><small>Nov <var data-var='date'> 12</var>, <var data-var='time'>17:47:29</var> GMT+0</small><br><strong>Identified</strong> -
As part of our continuous commitment to providing high-quality service, we will be performing **upgrade maintenance** on the **UK-01 cluster**.
**Expected Impact:**
We do **not** anticipate any downtime during this activity. You can continue using your Nimbus services as normal.
**Questions or Assistance?**
Please contact us via our Helpdesk: &lt;https://helpdesk.luware.cloud&gt;
**Post-Maintenance Details:**
A full rundown of the changes will be published on our Knowledge Base after completion:
&lt;https://help.luware.com&gt;.</p>
]]>
</content:encoded>
<pubDate>Sat, 14 Nov 2026 07:00:00 +0000</pubDate>
<link>https://status.luware.com/maintenance/cmwdubwjd00sg0wn415s5rq3j</link>
<guid>https://status.luware.com/maintenance/cmwdubwjd00sg0wn415s5rq3j</guid>
</item>
<item>
<title>Luware Recording MTCH Critical Maintenance</title>
<description>
Type: Maintenance
Duration: 10 hours
Affected Components: Web Applications, Speech Analytics, Search &amp; Playback, Media Playback, Call Recording, Storage Services, Microsoft Service Health
Nov 14, 17:00:00 GMT+0 - Completed - Maintenance has completed successfully Nov 14, 07:00:01 GMT+0 - Identified - Maintenance is now in progress Oct 29, 14:34:49 GMT+0 - Identified - As part of our continuous commitment to providing high-quality service, we will be performing **upgrade maintenance** on the **Luware Recording MTCH cluster** on **Sat 14th Nov 2026.**
**Expected Impact:**
We do **not** anticipate any downtime during this activity. You can continue using your Luware Recording services as normal.
**Questions or Assistance?**
Please contact us via our Helpdesk: &lt;https://helpdesk.luware.cloud&gt;
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Maintenance</p>
<p><strong>Duration:</strong> 10 hours</p>
<p><strong>Affected Components:</strong> </p>
<p><small>Nov <var data-var='date'> 14</var>, <var data-var='time'>17:00:00</var> GMT+0</small><br><strong>Completed</strong> -
Maintenance has completed successfully.</p>
<p><small>Nov <var data-var='date'> 14</var>, <var data-var='time'>07:00:01</var> GMT+0</small><br><strong>Identified</strong> -
Maintenance is now in progress.</p>
<p><small>Oct <var data-var='date'> 29</var>, <var data-var='time'>14:34:49</var> GMT+0</small><br><strong>Identified</strong> -
As part of our continuous commitment to providing high-quality service, we will be performing **upgrade maintenance** on the **Luware Recording MTCH cluster** on **Sat 14th Nov 2026.**
**Expected Impact:**
We do **not** anticipate any downtime during this activity. You can continue using your Luware Recording services as normal.
**Questions or Assistance?**
Please contact us via our Helpdesk: &lt;https://helpdesk.luware.cloud&gt;.</p>
]]>
</content:encoded>
<pubDate>Sat, 14 Nov 2026 07:00:00 +0000</pubDate>
<link>https://status.luware.com/maintenance/cmvtna7uh00kf0wpbfebgkuei</link>
<guid>https://status.luware.com/maintenance/cmvtna7uh00kf0wpbfebgkuei</guid>
</item>
<item>
<title>Nimbus CH-01 Scheduled Maintenance</title>
<description>
Type: Maintenance
Duration: 3 hours
Affected Components: Call Handling, Attendant Console, Microsoft Service Health, User Portal, Historical Reports via PowerBI, Admin Portal, User Availability, Nimbus App
Nov 13, 23:00:00 GMT+0 - Completed - Maintenance has completed successfully Nov 13, 20:00:01 GMT+0 - Identified - Maintenance is now in progress Oct 26, 13:30:42 GMT+0 - Identified - As part of our continuous commitment to providing high-quality service, we will be performing **upgrade maintenance** on the **CH-01 cluster**.
**Expected Impact:**
We do **not** anticipate any downtime during this activity. You can continue using your Nimbus services as normal.
**Questions or Assistance?**
Please contact us via our Helpdesk: &lt;https://helpdesk.luware.cloud&gt;
**Post-Maintenance Details:**
A full rundown of the changes will be published on our Knowledge Base after completion:
&lt;https://help.luware.com&gt;
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Maintenance</p>
<p><strong>Duration:</strong> 3 hours</p>
<p><strong>Affected Components:</strong> </p>
<p><small>Nov <var data-var='date'> 13</var>, <var data-var='time'>23:00:00</var> GMT+0</small><br><strong>Completed</strong> -
Maintenance has completed successfully.</p>
<p><small>Nov <var data-var='date'> 13</var>, <var data-var='time'>20:00:01</var> GMT+0</small><br><strong>Identified</strong> -
Maintenance is now in progress.</p>
<p><small>Oct <var data-var='date'> 26</var>, <var data-var='time'>13:30:42</var> GMT+0</small><br><strong>Identified</strong> -
As part of our continuous commitment to providing high-quality service, we will be performing **upgrade maintenance** on the **CH-01 cluster**.
**Expected Impact:**
We do **not** anticipate any downtime during this activity. You can continue using your Nimbus services as normal.
**Questions or Assistance?**
Please contact us via our Helpdesk: &lt;https://helpdesk.luware.cloud&gt;
**Post-Maintenance Details:**
A full rundown of the changes will be published on our Knowledge Base after completion:
&lt;https://help.luware.com&gt;.</p>
]]>
</content:encoded>
<pubDate>Fri, 13 Nov 2026 20:00:00 +0000</pubDate>
<link>https://status.luware.com/maintenance/cmvpao74f01d613rvhaenpf7x</link>
<guid>https://status.luware.com/maintenance/cmvpao74f01d613rvhaenpf7x</guid>
</item>
<item>
<title>Delays in Instant Messaging (IM) due to Microsoft outage</title>
<description>
Type: Incident
Duration: 6 hours and 40 minutes
Affected Components: Call Recording, Call Recording
Nov 13, 17:26:01 GMT+0 - Resolved - We are no longer seeing alerts relating to Microsoft Teams IM exports and we are recieving exports regularly now so we are regarding this incident as resolved.
If you required any further information please raise a case through our support desk. Nov 13, 10:46:18 GMT+0 - Identified - We have identified that the current Microsoft issues are having an effect on Instant Messaging (IM) export and there may be delays in seeing these in the platform. Our team is actively monitoring the situation and awaiting upstream resolution from Microsoft.
For customers recording Instant Messaging, those can be retrospectively retrieved once the outage is resolved.
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Incident</p>
<p><strong>Duration:</strong> 6 hours and 40 minutes</p>
<p><strong>Affected Components:</strong> </p>
<p><small>Nov <var data-var='date'> 13</var>, <var data-var='time'>17:26:01</var> GMT+0</small><br><strong>Resolved</strong> -
We are no longer seeing alerts relating to Microsoft Teams IM exports and we are recieving exports regularly now so we are regarding this incident as resolved.
If you required any further information please raise a case through our support desk..</p>
<p><small>Nov <var data-var='date'> 13</var>, <var data-var='time'>10:46:18</var> GMT+0</small><br><strong>Identified</strong> -
We have identified that the current Microsoft issues are having an effect on Instant Messaging (IM) export and there may be delays in seeing these in the platform. Our team is actively monitoring the situation and awaiting upstream resolution from Microsoft.
For customers recording Instant Messaging, those can be retrospectively retrieved once the outage is resolved..</p>
]]>
</content:encoded>
<pubDate>Fri, 13 Nov 2026 10:46:18 +0000</pubDate>
<link>https://status.luware.com/incident/cmweuq5rt0fg113mm31t9ng2f</link>
<guid>https://status.luware.com/incident/cmweuq5rt0fg113mm31t9ng2f</guid>
</item>
<item>
<title>Service Status: Impact of the Global Microsoft Outage</title>
<description>
Type: Incident
Duration: 4 days, 1 hour and 16 minutes
Affected Components: Call Handling, Microsoft Service Health, Nimbus App, Call Handling, User Portal, Admin Portal, Historical Reports via PowerBI, Historical Reports via PowerBI, User Portal, Microsoft Service Health, User Availability, User Availability, User Availability, Attendant Console, Microsoft Service Health, Microsoft Service Health, Historical Reports via PowerBI, User Availability, Microsoft Service Health, User Portal, Call Handling, Web Applications, User Portal, Nimbus App, Nimbus App, Nimbus App, Admin Portal, User Availability, Attendant Console, Call Handling, Admin Portal, Historical Reports via PowerBI, Admin Portal, Attendant Console, Historical Reports via PowerBI, Speech Analytics, Attendant Console, User Availability, Attendant Console, Speech Analytics, Admin Portal, User Availability, Call Handling, Historical Reports via PowerBI, Web applications, Media Playback, Storage Services, Call Handling, Nimbus App, Historical Reports via PowerBI, Attendant Console, Nimbus App, Attendant Console, Microsoft Service Health, Call Handling, Search &amp; Playback, Attendant Console, User Availability, Attendant Console, Nimbus App, Call Handling, User Availability, Admin Portal, Admin Portal, Historical Reports via PowerBI, Nimbus App, Call Recording, Call Handling, Nimbus App, Microsoft Service Health, Historical Reports via PowerBI, Media Playback, Call Recording, Storage Services, Microsoft Service Health, Admin Portal, User Availability, User Portal, Admin Portal, Search &amp; Retrieval, Microsoft Service Health, Microsoft Service Health, Microsoft Service Health
Nov 17, 10:21:22 GMT+0 - Resolved - No adverse effects have been observed following Microsoft&#039;s resolution of this issue. If you have any questions about this incident, please contact us by raising a ticket at &lt;https://helpdesk.luware.cloud&gt; Nov 13, 17:08:57 GMT+0 - Monitoring - Luware services have remained stable since our previous update, and we have not observed any unexpected behaviour or service impact. Our teams have been monitoring closely throughout the day.
Microsoft is now reporting that its services are beginning to come back online. We will keep this post open over the weekend and will share further updates here if needed.
Thank you for your patience and understanding. Nov 13, 09:04:56 GMT+0 - Monitoring - We are aware of the ongoing global Microsoft outage and are actively monitoring its impact on Luware services. Our core services remain fully operational. A summary of the current impact is below.
**Nimbus**
* Call handling is unaffected. All Nimbus clusters are fully operational and healthy.
* Some non-critical features may be intermittent, such as loading contact images for internal users via the Microsoft Graph API.
* Some customers have reported that the Nimbus app is missing from the Teams client. If this affects you, please access Nimbus in your browser at &lt;https://portal.luware.cloud&gt;.
**Luware Recording**
* Recording functionality is unaffected. All Recording clusters are running healthily.
* Scheduled reports may fail due to the disruption to Microsoft Outlook. Failed reports will not be retried automatically, but you can view them at any time by logging into the Luware Recording portal.
**Luware Support**
* Our ticketing system does not depend on Microsoft cloud services. However, creating new tickets by email and receiving ticket updates rely on Microsoft Outlook and are currently affected.
* To raise a new ticket or check for updates, please use the Helpdesk portal at &lt;https://helpdesk.luware.cloud&gt;.
We will continue to monitor the situation and post updates as it develops. Thank you for your patience.
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Incident</p>
<p><strong>Duration:</strong> 4 days, 1 hour and 16 minutes</p>
<p><strong>Affected Components:</strong> </p>
<p><small>Nov <var data-var='date'> 17</var>, <var data-var='time'>10:21:22</var> GMT+0</small><br><strong>Resolved</strong> -
No adverse effects have been observed following Microsoft&#039;s resolution of this issue. If you have any questions about this incident, please contact us by raising a ticket at &lt;https://helpdesk.luware.cloud&gt; .</p>
<p><small>Nov <var data-var='date'> 13</var>, <var data-var='time'>17:08:57</var> GMT+0</small><br><strong>Monitoring</strong> -
Luware services have remained stable since our previous update, and we have not observed any unexpected behaviour or service impact. Our teams have been monitoring closely throughout the day.
Microsoft is now reporting that its services are beginning to come back online. We will keep this post open over the weekend and will share further updates here if needed.
Thank you for your patience and understanding..</p>
<p><small>Nov <var data-var='date'> 13</var>, <var data-var='time'>09:04:56</var> GMT+0</small><br><strong>Monitoring</strong> -
We are aware of the ongoing global Microsoft outage and are actively monitoring its impact on Luware services. Our core services remain fully operational. A summary of the current impact is below.
**Nimbus**
* Call handling is unaffected. All Nimbus clusters are fully operational and healthy.
* Some non-critical features may be intermittent, such as loading contact images for internal users via the Microsoft Graph API.
* Some customers have reported that the Nimbus app is missing from the Teams client. If this affects you, please access Nimbus in your browser at &lt;https://portal.luware.cloud&gt;.
**Luware Recording**
* Recording functionality is unaffected. All Recording clusters are running healthily.
* Scheduled reports may fail due to the disruption to Microsoft Outlook. Failed reports will not be retried automatically, but you can view them at any time by logging into the Luware Recording portal.
**Luware Support**
* Our ticketing system does not depend on Microsoft cloud services. However, creating new tickets by email and receiving ticket updates rely on Microsoft Outlook and are currently affected.
* To raise a new ticket or check for updates, please use the Helpdesk portal at &lt;https://helpdesk.luware.cloud&gt;.
We will continue to monitor the situation and post updates as it develops. Thank you for your patience..</p>
]]>
</content:encoded>
<pubDate>Fri, 13 Nov 2026 09:04:56 +0000</pubDate>
<link>https://status.luware.com/incident/cmwer3rlg0dbv1mp9j8vgnz2k</link>
<guid>https://status.luware.com/incident/cmwer3rlg0dbv1mp9j8vgnz2k</guid>
</item>
<item>
<title>Nimbus CH-02 and DE-02 Scheduled Maintenance</title>
<description>
Type: Maintenance
Duration: 4 hours
Affected Components: Call Handling, User Portal, Admin Portal, Historical Reports via PowerBI, Microsoft Service Health, User Availability, User Availability, Historical Reports via PowerBI, Nimbus App, Attendant Console, Call Handling, Nimbus App, Attendant Console, Admin Portal, Microsoft Service Health
Nov 12, 23:00:00 GMT+0 - Completed - Maintenance has completed successfully Nov 12, 19:00:01 GMT+0 - Identified - Maintenance is now in progress Nov 12, 17:45:54 GMT+0 - Identified - As part of our continuous commitment to providing high-quality service, we will be performing **upgrade maintenance** on the **CH-02 and DE-02 clusters**.
**Expected Impact:**
We do **not** anticipate any downtime during this activity. You can continue using your Nimbus services as normal.
**Questions or Assistance?**
Please contact us via our Helpdesk: &lt;https://helpdesk.luware.cloud&gt;
**Post-Maintenance Details:**
A full rundown of the changes will be published on our Knowledge Base after completion:
&lt;https://help.luware.com&gt;
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Maintenance</p>
<p><strong>Duration:</strong> 4 hours</p>
<p><strong>Affected Components:</strong> </p>
<p><small>Nov <var data-var='date'> 12</var>, <var data-var='time'>23:00:00</var> GMT+0</small><br><strong>Completed</strong> -
Maintenance has completed successfully.</p>
<p><small>Nov <var data-var='date'> 12</var>, <var data-var='time'>19:00:01</var> GMT+0</small><br><strong>Identified</strong> -
Maintenance is now in progress.</p>
<p><small>Nov <var data-var='date'> 12</var>, <var data-var='time'>17:45:54</var> GMT+0</small><br><strong>Identified</strong> -
As part of our continuous commitment to providing high-quality service, we will be performing **upgrade maintenance** on the **CH-02 and DE-02 clusters**.
**Expected Impact:**
We do **not** anticipate any downtime during this activity. You can continue using your Nimbus services as normal.
**Questions or Assistance?**
Please contact us via our Helpdesk: &lt;https://helpdesk.luware.cloud&gt;
**Post-Maintenance Details:**
A full rundown of the changes will be published on our Knowledge Base after completion:
&lt;https://help.luware.com&gt;.</p>
]]>
</content:encoded>
<pubDate>Thu, 12 Nov 2026 19:00:00 +0000</pubDate>
<link>https://status.luware.com/maintenance/cmwdu9vea00v11rn4ouy7pfch</link>
<guid>https://status.luware.com/maintenance/cmwdu9vea00v11rn4ouy7pfch</guid>
</item>
<item>
<title>Nimbus CH-02 and DE-02 Scheduled Maintenance</title>
<description>
Type: Maintenance
Duration: 4 hours
Affected Components: Call Handling, User Availability, Historical Reports via PowerBI, Historical Reports via PowerBI, Nimbus App, Attendant Console, Microsoft Service Health, User Portal, Admin Portal, User Availability, Call Handling, Nimbus App, Attendant Console, Admin Portal, Microsoft Service Health
Nov 11, 23:00:00 GMT+0 - Completed - Maintenance has completed successfully Nov 11, 19:00:01 GMT+0 - Identified - Maintenance is now in progress Oct 26, 13:30:02 GMT+0 - Identified - As part of our continuous commitment to providing high-quality service, we will be performing **upgrade maintenance** on the **CH-02 and DE-02 clusters**.
**Expected Impact:**
We do **not** anticipate any downtime during this activity. You can continue using your Nimbus services as normal.
**Questions or Assistance?**
Please contact us via our Helpdesk: &lt;https://helpdesk.luware.cloud&gt;
**Post-Maintenance Details:**
A full rundown of the changes will be published on our Knowledge Base after completion:
&lt;https://help.luware.com&gt;
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Maintenance</p>
<p><strong>Duration:</strong> 4 hours</p>
<p><strong>Affected Components:</strong> </p>
<p><small>Nov <var data-var='date'> 11</var>, <var data-var='time'>23:00:00</var> GMT+0</small><br><strong>Completed</strong> -
Maintenance has completed successfully.</p>
<p><small>Nov <var data-var='date'> 11</var>, <var data-var='time'>19:00:01</var> GMT+0</small><br><strong>Identified</strong> -
Maintenance is now in progress.</p>
<p><small>Oct <var data-var='date'> 26</var>, <var data-var='time'>13:30:02</var> GMT+0</small><br><strong>Identified</strong> -
As part of our continuous commitment to providing high-quality service, we will be performing **upgrade maintenance** on the **CH-02 and DE-02 clusters**.
**Expected Impact:**
We do **not** anticipate any downtime during this activity. You can continue using your Nimbus services as normal.
**Questions or Assistance?**
Please contact us via our Helpdesk: &lt;https://helpdesk.luware.cloud&gt;
**Post-Maintenance Details:**
A full rundown of the changes will be published on our Knowledge Base after completion:
&lt;https://help.luware.com&gt;.</p>
]]>
</content:encoded>
<pubDate>Wed, 11 Nov 2026 19:00:00 +0000</pubDate>
<link>https://status.luware.com/maintenance/cmvpancam01ir13pcjnd2nzkn</link>
<guid>https://status.luware.com/maintenance/cmvpancam01ir13pcjnd2nzkn</guid>
</item>
<item>
<title>Nimbus CH-01 Service Alerts</title>
<description>
Type: Incident
Duration: 16 hours and 53 minutes
Affected Components: Call Handling, User Availability
Nov 12, 07:30:23 GMT+0 - Resolved - This incident has been resolved following a period of monitoring overnight with no further instances noted. Nov 11, 15:56:20 GMT+0 - Monitoring - All clean-up tasks have been concluded. Additional checks have confirmed normal operations. Our engineers are continuing to monitor the situation. Nov 11, 14:52:56 GMT+0 - Identified - Our engineers have taken mitigation actions following an alarm related to how Nimbus components communicated with each other internally. Services are restored but customers may see some tasks in a stale or stuck state, we are working to remove those systematically. Nov 11, 14:37:06 GMT+0 - Investigating - We are currently investigating system alerts in the Nimbus CH-01 cluster. More information will be added once it becomes available.
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Incident</p>
<p><strong>Duration:</strong> 16 hours and 53 minutes</p>
<p><strong>Affected Components:</strong> </p>
<p><small>Nov <var data-var='date'> 12</var>, <var data-var='time'>07:30:23</var> GMT+0</small><br><strong>Resolved</strong> -
This incident has been resolved following a period of monitoring overnight with no further instances noted..</p>
<p><small>Nov <var data-var='date'> 11</var>, <var data-var='time'>15:56:20</var> GMT+0</small><br><strong>Monitoring</strong> -
All clean-up tasks have been concluded. Additional checks have confirmed normal operations. Our engineers are continuing to monitor the situation..</p>
<p><small>Nov <var data-var='date'> 11</var>, <var data-var='time'>14:52:56</var> GMT+0</small><br><strong>Identified</strong> -
Our engineers have taken mitigation actions following an alarm related to how Nimbus components communicated with each other internally. Services are restored but customers may see some tasks in a stale or stuck state, we are working to remove those systematically..</p>
<p><small>Nov <var data-var='date'> 11</var>, <var data-var='time'>14:37:06</var> GMT+0</small><br><strong>Investigating</strong> -
We are currently investigating system alerts in the Nimbus CH-01 cluster. More information will be added once it becomes available..</p>
]]>
</content:encoded>
<pubDate>Wed, 11 Nov 2026 14:37:06 +0000</pubDate>
<link>https://status.luware.com/incident/cmwc8398e05m50wmi7da4vs7g</link>
<guid>https://status.luware.com/incident/cmwc8398e05m50wmi7da4vs7g</guid>
</item>
<item>
<title>Nimbus UK-01 Scheduled Maintenance</title>
<description>
Type: Maintenance
Duration: 3 hours
Affected Components: Attendant Console, Historical Reports via PowerBI, Call Handling, Nimbus App, User Availability, Microsoft Service Health, Admin Portal
Nov 10, 21:00:00 GMT+0 - Completed - Maintenance has completed successfully Nov 10, 18:00:01 GMT+0 - Identified - Maintenance is now in progress Oct 26, 13:29:07 GMT+0 - Identified - As part of our continuous commitment to providing high-quality service, we will be performing **upgrade maintenance** on the **UK-01 cluster**.
**Expected Impact:**
We do **not** anticipate any downtime during this activity. You can continue using your Nimbus services as normal.
**Questions or Assistance?**
Please contact us via our Helpdesk: &lt;https://helpdesk.luware.cloud&gt;
**Post-Maintenance Details:**
A full rundown of the changes will be published on our Knowledge Base after completion:
&lt;https://help.luware.com&gt;
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Maintenance</p>
<p><strong>Duration:</strong> 3 hours</p>
<p><strong>Affected Components:</strong> </p>
<p><small>Nov <var data-var='date'> 10</var>, <var data-var='time'>21:00:00</var> GMT+0</small><br><strong>Completed</strong> -
Maintenance has completed successfully.</p>
<p><small>Nov <var data-var='date'> 10</var>, <var data-var='time'>18:00:01</var> GMT+0</small><br><strong>Identified</strong> -
Maintenance is now in progress.</p>
<p><small>Oct <var data-var='date'> 26</var>, <var data-var='time'>13:29:07</var> GMT+0</small><br><strong>Identified</strong> -
As part of our continuous commitment to providing high-quality service, we will be performing **upgrade maintenance** on the **UK-01 cluster**.
**Expected Impact:**
We do **not** anticipate any downtime during this activity. You can continue using your Nimbus services as normal.
**Questions or Assistance?**
Please contact us via our Helpdesk: &lt;https://helpdesk.luware.cloud&gt;
**Post-Maintenance Details:**
A full rundown of the changes will be published on our Knowledge Base after completion:
&lt;https://help.luware.com&gt;.</p>
]]>
</content:encoded>
<pubDate>Tue, 10 Nov 2026 18:00:00 +0000</pubDate>
<link>https://status.luware.com/maintenance/cmvpam6f401qj1mrvru8t49bv</link>
<guid>https://status.luware.com/maintenance/cmvpam6f401qj1mrvru8t49bv</guid>
</item>
<item>
<title>Nimbus Portal Access from Germany</title>
<description>
Type: Incident
Duration: 5 days, 16 hours and 20 minutes
Affected Components: User Portal
Nov 16, 07:58:01 GMT+0 - Resolved - Our monitoring showed no further issues. DNS responses do not appear to include stale data anymore. Nov 12, 13:43:57 GMT+0 - Monitoring - Our engineers have implemented a DNS workaround that appears to allow previously impacted clients to resolve the URLs correctly again. Note that in special cases, cached responses from upstream DNS providers may still interfere until they expire. We will continue to monitor the situation and investigate the root cause. Nov 11, 16:30:19 GMT+0 - Monitoring - Following a detailed investigation with affected customers and Microsoft Support, we have narrowed the cause of this issue down to DNS resolvers which are used by Deutsche Telekom and some affiliates in Germany.
These DNS resolvers are responding with an incorrect host for the portal.de-01.luware.cloud domain, leading to a failure to access the resources.
We recommend affected customers contact the support team of their network providers for further troubleshooting. Nov 10, 15:37:43 GMT+0 - Monitoring - A subset of customers geographically located in Germany have reported problems access the Nimbus Portal ([portal.de-01.luware.cloud](http://portal.de-01.luware.cloud)).
Luware&#039;s investigations indicate this may be localised to a small number of Internet Service Providers in Germany.
Users may see:
\- The portal fails to load
\- Certificate Errors
\- An Azure Front Door error page
All Nimbus services are healthy and call handling is functioning normally. If you are experiencing this issue, we recommend contacting your Internet Service Provider and if possible switching your internet connection to an alternative (e.g. mobile tethering).
Clearing the browser cache and/or clearing the DNS cache (run &#039;ipconfig /flushdns&#039; in a command prompt) may help to restore access.
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Incident</p>
<p><strong>Duration:</strong> 5 days, 16 hours and 20 minutes</p>
<p><strong>Affected Components:</strong> </p>
<p><small>Nov <var data-var='date'> 16</var>, <var data-var='time'>07:58:01</var> GMT+0</small><br><strong>Resolved</strong> -
Our monitoring showed no further issues. DNS responses do not appear to include stale data anymore..</p>
<p><small>Nov <var data-var='date'> 12</var>, <var data-var='time'>13:43:57</var> GMT+0</small><br><strong>Monitoring</strong> -
Our engineers have implemented a DNS workaround that appears to allow previously impacted clients to resolve the URLs correctly again. Note that in special cases, cached responses from upstream DNS providers may still interfere until they expire. We will continue to monitor the situation and investigate the root cause..</p>
<p><small>Nov <var data-var='date'> 11</var>, <var data-var='time'>16:30:19</var> GMT+0</small><br><strong>Monitoring</strong> -
Following a detailed investigation with affected customers and Microsoft Support, we have narrowed the cause of this issue down to DNS resolvers which are used by Deutsche Telekom and some affiliates in Germany.
These DNS resolvers are responding with an incorrect host for the portal.de-01.luware.cloud domain, leading to a failure to access the resources.
We recommend affected customers contact the support team of their network providers for further troubleshooting..</p>
<p><small>Nov <var data-var='date'> 10</var>, <var data-var='time'>15:37:43</var> GMT+0</small><br><strong>Monitoring</strong> -
A subset of customers geographically located in Germany have reported problems access the Nimbus Portal ([portal.de-01.luware.cloud](http://portal.de-01.luware.cloud)).
Luware&#039;s investigations indicate this may be localised to a small number of Internet Service Providers in Germany.
Users may see:
\- The portal fails to load
\- Certificate Errors
\- An Azure Front Door error page
All Nimbus services are healthy and call handling is functioning normally. If you are experiencing this issue, we recommend contacting your Internet Service Provider and if possible switching your internet connection to an alternative (e.g. mobile tethering).
Clearing the browser cache and/or clearing the DNS cache (run &#039;ipconfig /flushdns&#039; in a command prompt) may help to restore access..</p>
]]>
</content:encoded>
<pubDate>Tue, 10 Nov 2026 15:37:43 +0000</pubDate>
<link>https://status.luware.com/incident/cmwautbyz0iaw0wpiy9f1kbe5</link>
<guid>https://status.luware.com/incident/cmwautbyz0iaw0wpiy9f1kbe5</guid>
</item>
<item>
<title>MTDE - Luware Recording - Unexpected Call Termination Alert</title>
<description>
Type: Incident
Duration: 7 hours and 2 minutes
Affected Components: Call Recording
Nov 6, 17:02:45 GMT+0 - Resolved - This incident has been resolved. Nov 6, 15:42:15 GMT+0 - Monitoring - There have been no further occurrences but we are continuing to monitor until the end of the day. Nov 6, 10:01:00 GMT+0 - Monitoring - We have noticed an unusually high number of unexpected call termination alerts coming on our recording platforms from Microsoft Teams, starting from 06/11 at 10:01 UTC. Our Luware Recording platforms are stable and we are seeing the errors come from Microsoft Teams. We are conducting some further investigations to find the true root cause. Some users may experience their Microsoft Teams call end unexpectedly. We will update you with any further information.
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Incident</p>
<p><strong>Duration:</strong> 7 hours and 2 minutes</p>
<p><strong>Affected Components:</strong> </p>
<p><small>Nov <var data-var='date'> 6</var>, <var data-var='time'>17:02:45</var> GMT+0</small><br><strong>Resolved</strong> -
This incident has been resolved..</p>
<p><small>Nov <var data-var='date'> 6</var>, <var data-var='time'>15:42:15</var> GMT+0</small><br><strong>Monitoring</strong> -
There have been no further occurrences but we are continuing to monitor until the end of the day..</p>
<p><small>Nov <var data-var='date'> 6</var>, <var data-var='time'>10:01:00</var> GMT+0</small><br><strong>Monitoring</strong> -
We have noticed an unusually high number of unexpected call termination alerts coming on our recording platforms from Microsoft Teams, starting from 06/11 at 10:01 UTC. Our Luware Recording platforms are stable and we are seeing the errors come from Microsoft Teams. We are conducting some further investigations to find the true root cause. Some users may experience their Microsoft Teams call end unexpectedly. We will update you with any further information..</p>
]]>
</content:encoded>
<pubDate>Fri, 6 Nov 2026 10:01:00 +0000</pubDate>
<link>https://status.luware.com/incident/cmw4y5rfz0dj01bs0kd326rrt</link>
<guid>https://status.luware.com/incident/cmw4y5rfz0dj01bs0kd326rrt</guid>
</item>
<item>
<title>Nimbus AU-01 Scheduled Maintenance</title>
<description>
Type: Maintenance
Duration: 2 hours
Affected Components: Attendant Console, Nimbus App, Call Handling, Historical Reports via PowerBI, Microsoft Service Health, Admin Portal, User Availability, User Portal
Nov 5, 14:00:00 GMT+0 - Completed - Maintenance has completed successfully Nov 5, 12:00:01 GMT+0 - Identified - Maintenance is now in progress Oct 26, 13:27:51 GMT+0 - Identified - As part of our continuous commitment to providing high-quality service, we will be performing **upgrade maintenance** on the **AU-01 cluster**.
**Expected Impact:**
We do **not** anticipate any downtime during this activity. You can continue using your Nimbus services as normal.
**Questions or Assistance?**
Please contact us via our Helpdesk: &lt;https://helpdesk.luware.cloud&gt;
**Post-Maintenance Details:**
A full rundown of the changes will be published on our Knowledge Base after completion:
&lt;https://help.luware.com&gt;
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Maintenance</p>
<p><strong>Duration:</strong> 2 hours</p>
<p><strong>Affected Components:</strong> </p>
<p><small>Nov <var data-var='date'> 5</var>, <var data-var='time'>14:00:00</var> GMT+0</small><br><strong>Completed</strong> -
Maintenance has completed successfully.</p>
<p><small>Nov <var data-var='date'> 5</var>, <var data-var='time'>12:00:01</var> GMT+0</small><br><strong>Identified</strong> -
Maintenance is now in progress.</p>
<p><small>Oct <var data-var='date'> 26</var>, <var data-var='time'>13:27:51</var> GMT+0</small><br><strong>Identified</strong> -
As part of our continuous commitment to providing high-quality service, we will be performing **upgrade maintenance** on the **AU-01 cluster**.
**Expected Impact:**
We do **not** anticipate any downtime during this activity. You can continue using your Nimbus services as normal.
**Questions or Assistance?**
Please contact us via our Helpdesk: &lt;https://helpdesk.luware.cloud&gt;
**Post-Maintenance Details:**
A full rundown of the changes will be published on our Knowledge Base after completion:
&lt;https://help.luware.com&gt;.</p>
]]>
</content:encoded>
<pubDate>Thu, 5 Nov 2026 12:00:00 +0000</pubDate>
<link>https://status.luware.com/maintenance/cmvpakjqv01q01mrvn976vrrg</link>
<guid>https://status.luware.com/maintenance/cmvpakjqv01q01mrvn976vrrg</guid>
</item>
<item>
<title>Nimbus US-01 Scheduled Maintenance</title>
<description>
Type: Maintenance
Duration: 2 hours
Affected Components: Historical Reports via PowerBI, Call Handling, Nimbus App, Attendant Console, User Availability, User Availability, Admin Portal, Microsoft Service Health
Nov 4, 11:00:00 GMT+0 - Completed - Maintenance has completed successfully Nov 4, 09:00:01 GMT+0 - Identified - Maintenance is now in progress Oct 26, 13:27:02 GMT+0 - Identified - As part of our continuous commitment to providing high-quality service, we will be performing **upgrade maintenance** on the **US-01 cluster**.
**Expected Impact:**
We do **not** anticipate any downtime during this activity. You can continue using your Nimbus services as normal.
**Questions or Assistance?**
Please contact us via our Helpdesk: &lt;https://helpdesk.luware.cloud&gt;
**Post-Maintenance Details:**
A full rundown of the changes will be published on our Knowledge Base after completion:
&lt;https://help.luware.com&gt;
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Maintenance</p>
<p><strong>Duration:</strong> 2 hours</p>
<p><strong>Affected Components:</strong> </p>
<p><small>Nov <var data-var='date'> 4</var>, <var data-var='time'>11:00:00</var> GMT+0</small><br><strong>Completed</strong> -
Maintenance has completed successfully.</p>
<p><small>Nov <var data-var='date'> 4</var>, <var data-var='time'>09:00:01</var> GMT+0</small><br><strong>Identified</strong> -
Maintenance is now in progress.</p>
<p><small>Oct <var data-var='date'> 26</var>, <var data-var='time'>13:27:02</var> GMT+0</small><br><strong>Identified</strong> -
As part of our continuous commitment to providing high-quality service, we will be performing **upgrade maintenance** on the **US-01 cluster**.
**Expected Impact:**
We do **not** anticipate any downtime during this activity. You can continue using your Nimbus services as normal.
**Questions or Assistance?**
Please contact us via our Helpdesk: &lt;https://helpdesk.luware.cloud&gt;
**Post-Maintenance Details:**
A full rundown of the changes will be published on our Knowledge Base after completion:
&lt;https://help.luware.com&gt;.</p>
]]>
</content:encoded>
<pubDate>Wed, 4 Nov 2026 09:00:00 +0000</pubDate>
<link>https://status.luware.com/maintenance/cmvpajhja01in13rp3588kaj3</link>
<guid>https://status.luware.com/maintenance/cmvpajhja01in13rp3588kaj3</guid>
</item>
<item>
<title>Nimbus DE-01 - Task Distribution Issues</title>
<description>
Type: Incident
Duration: 4 hours and 8 minutes
Affected Components: Call Handling, User Availability
Nov 3, 15:00:00 GMT+0 - Resolved - Monitoring showed no further issues. We apologize for the inconvenience. Nov 3, 12:19:44 GMT+0 - Monitoring - The impacted services have recovered. Our team is performing follow-up checks and continues to closely monitor the situation. Nov 3, 12:15:08 GMT+0 - Identified - Our engineers have taken steps to mitigate the identified issue. Services are recovering but may still experience issues until this is fully completed. Nov 3, 10:52:00 GMT+0 - Identified - We have identified an issue with task distribution in the Nimbus DE-01 cluster. Our engineers are currently working on restoring functionality.
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Incident</p>
<p><strong>Duration:</strong> 4 hours and 8 minutes</p>
<p><strong>Affected Components:</strong> </p>
<p><small>Nov <var data-var='date'> 3</var>, <var data-var='time'>15:00:00</var> GMT+0</small><br><strong>Resolved</strong> -
Monitoring showed no further issues. We apologize for the inconvenience..</p>
<p><small>Nov <var data-var='date'> 3</var>, <var data-var='time'>12:19:44</var> GMT+0</small><br><strong>Monitoring</strong> -
The impacted services have recovered. Our team is performing follow-up checks and continues to closely monitor the situation..</p>
<p><small>Nov <var data-var='date'> 3</var>, <var data-var='time'>12:15:08</var> GMT+0</small><br><strong>Identified</strong> -
Our engineers have taken steps to mitigate the identified issue. Services are recovering but may still experience issues until this is fully completed..</p>
<p><small>Nov <var data-var='date'> 3</var>, <var data-var='time'>10:52:00</var> GMT+0</small><br><strong>Identified</strong> -
We have identified an issue with task distribution in the Nimbus DE-01 cluster. Our engineers are currently working on restoring functionality..</p>
]]>
</content:encoded>
<pubDate>Tue, 3 Nov 2026 10:52:00 +0000</pubDate>
<link>https://status.luware.com/incident/cmw0m3e4m0ch00wphvx0wmgrm</link>
<guid>https://status.luware.com/incident/cmw0m3e4m0ch00wphvx0wmgrm</guid>
</item>
<item>
<title>Nimbus DE-01 Scheduled Maintenance</title>
<description>
Type: Maintenance
Duration: 3 hours
Affected Components: Nimbus App, User Portal, Call Handling, User Availability, Attendant Console, Admin Portal, Historical Reports via PowerBI, Microsoft Service Health
Nov 1, 09:00:00 GMT+0 - Completed - Maintenance has completed successfully Nov 1, 06:00:01 GMT+0 - Identified - Maintenance is now in progress Oct 6, 10:55:07 GMT+0 - Identified - As part of our continuous commitment to providing high-quality service, we will be performing **upgrade maintenance** on the **DE-01 cluster**.
**Expected Impact:**
We do **not** anticipate any downtime during this activity. You can continue using your Nimbus services as normal.
**Questions or Assistance?**
Please contact us via our Helpdesk: &lt;https://helpdesk.luware.cloud&gt;
**Post-Maintenance Details:**
A full rundown of the changes will be published on our Knowledge Base after completion:
&lt;https://help.luware.com&gt;
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Maintenance</p>
<p><strong>Duration:</strong> 3 hours</p>
<p><strong>Affected Components:</strong> </p>
<p><small>Nov <var data-var='date'> 1</var>, <var data-var='time'>09:00:00</var> GMT+0</small><br><strong>Completed</strong> -
Maintenance has completed successfully.</p>
<p><small>Nov <var data-var='date'> 1</var>, <var data-var='time'>06:00:01</var> GMT+0</small><br><strong>Identified</strong> -
Maintenance is now in progress.</p>
<p><small>Oct <var data-var='date'> 6</var>, <var data-var='time'>10:55:07</var> GMT+0</small><br><strong>Identified</strong> -
As part of our continuous commitment to providing high-quality service, we will be performing **upgrade maintenance** on the **DE-01 cluster**.
**Expected Impact:**
We do **not** anticipate any downtime during this activity. You can continue using your Nimbus services as normal.
**Questions or Assistance?**
Please contact us via our Helpdesk: &lt;https://helpdesk.luware.cloud&gt;
**Post-Maintenance Details:**
A full rundown of the changes will be published on our Knowledge Base after completion:
&lt;https://help.luware.com&gt;.</p>
]]>
</content:encoded>
<pubDate>Sun, 1 Nov 2026 06:00:00 +0000</pubDate>
<link>https://status.luware.com/maintenance/cmuwkb3450a1r13l4ywo4u2qg</link>
<guid>https://status.luware.com/maintenance/cmuwkb3450a1r13l4ywo4u2qg</guid>
</item>
<item>
<title>Luware Recording Scheduled Maintenance</title>
<description>
Type: Maintenance
Duration: 9 hours
Affected Components: Web applications, Web Applications, Storage Services, Search &amp; Playback, Call Recording, Media Playback, Media Playback, Call Recording, Storage Services, Search &amp; Retrieval
Oct 31, 15:00:00 GMT+0 - Completed - Maintenance has completed successfully Oct 31, 06:00:01 GMT+0 - Identified - Maintenance is now in progress Oct 21, 15:50:35 GMT+0 - Identified - As part of our continuous commitment to providing high-quality service, we will be performing routine **security patching** on all **Luware Recording clusters**.
**Expected Impact:**
We do **not** anticipate any downtime during this activity. You can continue using your Luware Recording services as normal.
**Questions or Assistance?**
Please contact us via our Helpdesk: &lt;https://helpdesk.luware.cloud&gt;
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Maintenance</p>
<p><strong>Duration:</strong> 9 hours</p>
<p><strong>Affected Components:</strong> </p>
<p><small>Oct <var data-var='date'> 31</var>, <var data-var='time'>15:00:00</var> GMT+0</small><br><strong>Completed</strong> -
Maintenance has completed successfully.</p>
<p><small>Oct <var data-var='date'> 31</var>, <var data-var='time'>06:00:01</var> GMT+0</small><br><strong>Identified</strong> -
Maintenance is now in progress.</p>
<p><small>Oct <var data-var='date'> 21</var>, <var data-var='time'>15:50:35</var> GMT+0</small><br><strong>Identified</strong> -
As part of our continuous commitment to providing high-quality service, we will be performing routine **security patching** on all **Luware Recording clusters**.
**Expected Impact:**
We do **not** anticipate any downtime during this activity. You can continue using your Luware Recording services as normal.
**Questions or Assistance?**
Please contact us via our Helpdesk: &lt;https://helpdesk.luware.cloud&gt;.</p>
]]>
</content:encoded>
<pubDate>Sat, 31 Oct 2026 06:00:00 +0000</pubDate>
<link>https://status.luware.com/maintenance/cmviagtws02nw1mmk5sp3sarq</link>
<guid>https://status.luware.com/maintenance/cmviagtws02nw1mmk5sp3sarq</guid>
</item>
<item>
<title>Luware Recording Scheduled Maintenance</title>
<description>
Type: Maintenance
Duration: 9 hours
Affected Components: Web applications, Web Applications, Storage Services, Search &amp; Playback, Call Recording, Media Playback, Media Playback, Call Recording, Storage Services, Search &amp; Retrieval
Oct 31, 03:30:00 GMT+0 - Completed - Maintenance has completed successfully Oct 30, 18:30:01 GMT+0 - Identified - Maintenance is now in progress Oct 21, 15:49:59 GMT+0 - Identified - As part of our continuous commitment to providing high-quality service, we will be performing routine **security patching** on all **Luware Recording clusters**.
**Expected Impact:**
We do **not** anticipate any downtime during this activity. You can continue using your Luware Recording services as normal.
**Questions or Assistance?**
Please contact us via our Helpdesk: &lt;https://helpdesk.luware.cloud&gt;
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Maintenance</p>
<p><strong>Duration:</strong> 9 hours</p>
<p><strong>Affected Components:</strong> </p>
<p><small>Oct <var data-var='date'> 31</var>, <var data-var='time'>03:30:00</var> GMT+0</small><br><strong>Completed</strong> -
Maintenance has completed successfully.</p>
<p><small>Oct <var data-var='date'> 30</var>, <var data-var='time'>18:30:01</var> GMT+0</small><br><strong>Identified</strong> -
Maintenance is now in progress.</p>
<p><small>Oct <var data-var='date'> 21</var>, <var data-var='time'>15:49:59</var> GMT+0</small><br><strong>Identified</strong> -
As part of our continuous commitment to providing high-quality service, we will be performing routine **security patching** on all **Luware Recording clusters**.
**Expected Impact:**
We do **not** anticipate any downtime during this activity. You can continue using your Luware Recording services as normal.
**Questions or Assistance?**
Please contact us via our Helpdesk: &lt;https://helpdesk.luware.cloud&gt;.</p>
]]>
</content:encoded>
<pubDate>Fri, 30 Oct 2026 18:30:00 +0000</pubDate>
<link>https://status.luware.com/maintenance/cmviag2l705f613mkbb52y84k</link>
<guid>https://status.luware.com/maintenance/cmviag2l705f613mkbb52y84k</guid>
</item>
<item>
<title>Luware Recording Scheduled Maintenance</title>
<description>
Type: Maintenance
Duration: 9 hours
Affected Components: Web applications, Web Applications, Storage Services, Search &amp; Playback, Call Recording, Media Playback, Media Playback, Call Recording, Storage Services, Search &amp; Retrieval
Oct 30, 03:30:00 GMT+0 - Completed - Maintenance has completed successfully Oct 29, 18:30:01 GMT+0 - Identified - Maintenance is now in progress Oct 21, 15:49:10 GMT+0 - Identified - As part of our continuous commitment to providing high-quality service, we will be performing routine **security patching** on all **Luware Recording clusters**.
**Expected Impact:**
We do **not** anticipate any downtime during this activity. You can continue using your Luware Recording services as normal.
**Questions or Assistance?**
Please contact us via our Helpdesk: &lt;https://helpdesk.luware.cloud&gt;
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Maintenance</p>
<p><strong>Duration:</strong> 9 hours</p>
<p><strong>Affected Components:</strong> </p>
<p><small>Oct <var data-var='date'> 30</var>, <var data-var='time'>03:30:00</var> GMT+0</small><br><strong>Completed</strong> -
Maintenance has completed successfully.</p>
<p><small>Oct <var data-var='date'> 29</var>, <var data-var='time'>18:30:01</var> GMT+0</small><br><strong>Identified</strong> -
Maintenance is now in progress.</p>
<p><small>Oct <var data-var='date'> 21</var>, <var data-var='time'>15:49:10</var> GMT+0</small><br><strong>Identified</strong> -
As part of our continuous commitment to providing high-quality service, we will be performing routine **security patching** on all **Luware Recording clusters**.
**Expected Impact:**
We do **not** anticipate any downtime during this activity. You can continue using your Luware Recording services as normal.
**Questions or Assistance?**
Please contact us via our Helpdesk: &lt;https://helpdesk.luware.cloud&gt;.</p>
]]>
</content:encoded>
<pubDate>Thu, 29 Oct 2026 18:30:00 +0000</pubDate>
<link>https://status.luware.com/maintenance/cmviaf0qi03661amkw1jmbhbf</link>
<guid>https://status.luware.com/maintenance/cmviaf0qi03661amkw1jmbhbf</guid>
</item>
<item>
<title>Nimbus EU-01 Scheduled Maintenance</title>
<description>
Type: Maintenance
Duration: 3 hours
Affected Components: Nimbus App, Admin Portal, Historical Reports via PowerBI, User Availability, Attendant Console, Microsoft Service Health, Call Handling
Oct 28, 21:00:00 GMT+0 - Completed - Maintenance has completed successfully Oct 28, 18:00:01 GMT+0 - Identified - Maintenance is now in progress Oct 6, 10:53:59 GMT+0 - Identified - As part of our continuous commitment to providing high-quality service, we will be performing **upgrade maintenance** on the **EU-01 cluster**.
**Expected Impact:**
We do **not** anticipate any downtime during this activity. You can continue using your Nimbus services as normal.
**Questions or Assistance?**
Please contact us via our Helpdesk: &lt;https://helpdesk.luware.cloud&gt;
**Post-Maintenance Details:**
A full rundown of the changes will be published on our Knowledge Base after completion:
&lt;https://help.luware.com&gt;
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Maintenance</p>
<p><strong>Duration:</strong> 3 hours</p>
<p><strong>Affected Components:</strong> </p>
<p><small>Oct <var data-var='date'> 28</var>, <var data-var='time'>21:00:00</var> GMT+0</small><br><strong>Completed</strong> -
Maintenance has completed successfully.</p>
<p><small>Oct <var data-var='date'> 28</var>, <var data-var='time'>18:00:01</var> GMT+0</small><br><strong>Identified</strong> -
Maintenance is now in progress.</p>
<p><small>Oct <var data-var='date'> 6</var>, <var data-var='time'>10:53:59</var> GMT+0</small><br><strong>Identified</strong> -
As part of our continuous commitment to providing high-quality service, we will be performing **upgrade maintenance** on the **EU-01 cluster**.
**Expected Impact:**
We do **not** anticipate any downtime during this activity. You can continue using your Nimbus services as normal.
**Questions or Assistance?**
Please contact us via our Helpdesk: &lt;https://helpdesk.luware.cloud&gt;
**Post-Maintenance Details:**
A full rundown of the changes will be published on our Knowledge Base after completion:
&lt;https://help.luware.com&gt;.</p>
]]>
</content:encoded>
<pubDate>Wed, 28 Oct 2026 18:00:00 +0000</pubDate>
<link>https://status.luware.com/maintenance/cmuwk9mgj0hln0wlpcwi872ml</link>
<guid>https://status.luware.com/maintenance/cmuwk9mgj0hln0wlpcwi872ml</guid>
</item>
<item>
<title>US Cluster - One-Way Audio Issues</title>
<description>
Type: Incident
Duration: 14 hours and 48 minutes
Affected Components: Call Handling
Sep 24, 10:30:51 GMT+0 - Resolved - Our monitoring showed no further issues. Sep 23, 20:40:11 GMT+0 - Monitoring - Our analysis shows increased response times coming from Microsoft Graph for some of the incoming calls. We have likewise adjusted our request timing to avoid the issue. We continue to monitor the situation. Sep 23, 19:42:25 GMT+0 - Investigating - We are currently investigating reports of intermittent one-way audio issues occurring after calls have been distributed to Nimbus agents.
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Incident</p>
<p><strong>Duration:</strong> 14 hours and 48 minutes</p>
<p><strong>Affected Components:</strong> </p>
<p><small>Sep <var data-var='date'> 24</var>, <var data-var='time'>10:30:51</var> GMT+0</small><br><strong>Resolved</strong> -
Our monitoring showed no further issues..</p>
<p><small>Sep <var data-var='date'> 23</var>, <var data-var='time'>20:40:11</var> GMT+0</small><br><strong>Monitoring</strong> -
Our analysis shows increased response times coming from Microsoft Graph for some of the incoming calls. We have likewise adjusted our request timing to avoid the issue. We continue to monitor the situation..</p>
<p><small>Sep <var data-var='date'> 23</var>, <var data-var='time'>19:42:25</var> GMT+0</small><br><strong>Investigating</strong> -
We are currently investigating reports of intermittent one-way audio issues occurring after calls have been distributed to Nimbus agents..</p>
]]>
</content:encoded>
<pubDate>Wed, 23 Sep 2026 19:42:25 +0000</pubDate>
<link>https://status.luware.com/incident/cmueif5kt02fj13rg4v5k7f67</link>
<guid>https://status.luware.com/incident/cmueif5kt02fj13rg4v5k7f67</guid>
</item>
<item>
<title>Luware Recording - MTDE recording issues</title>
<description>
Type: Incident
Duration: 18 hours and 50 minutes
Affected Components: Call Recording
Sep 24, 07:13:05 GMT+0 - Resolved - We will now resolve this incident since after monitoring there has been no repeat of the same issue.
If you require any further information regarding this incident, please raise a case with us through Luware Support at &lt;https://helpdesk.luware.cloud/&gt; Sep 23, 15:48:50 GMT+0 - Monitoring - We have identified the issue to be a large influx of Graph API traffic received from Microsoft which has caused our Microsoft Teams recording servers to temporarily overload and not have any capacity to capture and process any additional data. This impact lasted just 4 seconds.
We have been monitoring the impacted cluster for a few hours and we have not noticed a recurrence of the same issue. The platform is back to being fully operational.
Some customers may have noticed that their Microsoft Teams recorded users may have had their conversations forcibly terminated or not allowed to continue, if a fail-close Microsoft Teams type policy was assigned, and some customers may notice a loss of recording within the impacted time window if a Microsoft Teams fail-open type policy is assigned.
If you require further information or a full RCA for this incident, please raise a case with Luware Support by going to our support portal - &lt;https://helpdesk.luware.cloud/&gt;
We sincerely apologize for any inconvenience caused. Sep 23, 15:48:49 GMT+0 - Identified - We are continuing to work on a fix for this incident. Sep 23, 12:23:00 GMT+0 - Monitoring - We are investigating an issue currently with call recording in our Multi-Tenant Germany recording cluster. We are working to understand the impact of the issues and we will update shortly
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Incident</p>
<p><strong>Duration:</strong> 18 hours and 50 minutes</p>
<p><strong>Affected Components:</strong> </p>
<p><small>Sep <var data-var='date'> 24</var>, <var data-var='time'>07:13:05</var> GMT+0</small><br><strong>Resolved</strong> -
We will now resolve this incident since after monitoring there has been no repeat of the same issue.
If you require any further information regarding this incident, please raise a case with us through Luware Support at &lt;https://helpdesk.luware.cloud/&gt;.</p>
<p><small>Sep <var data-var='date'> 23</var>, <var data-var='time'>15:48:50</var> GMT+0</small><br><strong>Monitoring</strong> -
We have identified the issue to be a large influx of Graph API traffic received from Microsoft which has caused our Microsoft Teams recording servers to temporarily overload and not have any capacity to capture and process any additional data. This impact lasted just 4 seconds.
We have been monitoring the impacted cluster for a few hours and we have not noticed a recurrence of the same issue. The platform is back to being fully operational.
Some customers may have noticed that their Microsoft Teams recorded users may have had their conversations forcibly terminated or not allowed to continue, if a fail-close Microsoft Teams type policy was assigned, and some customers may notice a loss of recording within the impacted time window if a Microsoft Teams fail-open type policy is assigned.
If you require further information or a full RCA for this incident, please raise a case with Luware Support by going to our support portal - &lt;https://helpdesk.luware.cloud/&gt;
We sincerely apologize for any inconvenience caused. .</p>
<p><small>Sep <var data-var='date'> 23</var>, <var data-var='time'>15:48:49</var> GMT+0</small><br><strong>Identified</strong> -
We are continuing to work on a fix for this incident..</p>
<p><small>Sep <var data-var='date'> 23</var>, <var data-var='time'>12:23:00</var> GMT+0</small><br><strong>Monitoring</strong> -
We are investigating an issue currently with call recording in our Multi-Tenant Germany recording cluster. We are working to understand the impact of the issues and we will update shortly.</p>
]]>
</content:encoded>
<pubDate>Wed, 23 Sep 2026 12:23:00 +0000</pubDate>
<link>https://status.luware.com/incident/cmue4rzif001112o0gzwk1kfw</link>
<guid>https://status.luware.com/incident/cmue4rzif001112o0gzwk1kfw</guid>
</item>
<item>
<title>Teams Presence Sync Issues</title>
<description>
Type: Incident
Duration: 1 hour and 3 minutes
Affected Components: User Availability
Aug 27, 08:45:45 GMT+0 - Resolved - Monitoring confirmed the issue to be resolved. We apologize for any inconvenience caused. Aug 27, 08:13:19 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Presence synchronization should be restored for all tenants now. There may be slight delays until new presence changes are being picked up as the service fully recovers. Aug 27, 08:01:08 GMT+0 - Identified - We have identified issues with the presence sync service for some Nimbus tenants in the CH-01 environment and are working to resolve them. Aug 27, 07:43:06 GMT+0 - Investigating - We are currently investigating reports of the Microsoft Teams presence status not being correctly synced to Nimbus in the CH-01 environment.
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Incident</p>
<p><strong>Duration:</strong> 1 hour and 3 minutes</p>
<p><strong>Affected Components:</strong> </p>
<p><small>Aug <var data-var='date'> 27</var>, <var data-var='time'>08:45:45</var> GMT+0</small><br><strong>Resolved</strong> -
Monitoring confirmed the issue to be resolved. We apologize for any inconvenience caused. .</p>
<p><small>Aug <var data-var='date'> 27</var>, <var data-var='time'>08:13:19</var> GMT+0</small><br><strong>Monitoring</strong> -
We implemented a fix and are currently monitoring the result. Presence synchronization should be restored for all tenants now. There may be slight delays until new presence changes are being picked up as the service fully recovers..</p>
<p><small>Aug <var data-var='date'> 27</var>, <var data-var='time'>08:01:08</var> GMT+0</small><br><strong>Identified</strong> -
We have identified issues with the presence sync service for some Nimbus tenants in the CH-01 environment and are working to resolve them..</p>
<p><small>Aug <var data-var='date'> 27</var>, <var data-var='time'>07:43:06</var> GMT+0</small><br><strong>Investigating</strong> -
We are currently investigating reports of the Microsoft Teams presence status not being correctly synced to Nimbus in the CH-01 environment..</p>
]]>
</content:encoded>
<pubDate>Thu, 27 Aug 2026 07:43:06 +0000</pubDate>
<link>https://status.luware.com/incident/cmtb7ukrt00040sk3grcrhpoq</link>
<guid>https://status.luware.com/incident/cmtb7ukrt00040sk3grcrhpoq</guid>
</item>
<item>
<title>Nimbus User &quot;Removed from the call&quot;</title>
<description>
Type: Incident
Affected Components: Microsoft Service Health, Microsoft Service Health, Microsoft Service Health, Microsoft Service Health, Microsoft Service Health, Microsoft Service Health, Microsoft Service Health, Microsoft Service Health, Microsoft Service Health
Nov 17, 11:00:19 GMT+0 - Identified - Following our discussions with Microsoft’s product group, a change is currently being gradually rolled out to Microsoft Teams to improve the behavior described in this incident.
Our testing shows that the change already resolves the issue in certain call-flow scenarios. When a call is queued **after a service transfer**, the “Removed from the call” window is no longer displayed when the agent subsequently performs the affected call-handling actions.
However, when a call is queued **directly in the main service**, agents may still see the “Removed from the call” window when performing certain actions in Nimbus, such as transferring or parking the call. This behavior applies to both **Direct Conference** and **Broadcast** distribution.
As before, this is a **Teams client behavior and does not affect Nimbus call handling itself**. We are continuing to test the change as it becomes available and remain in contact with Microsoft regarding the scenarios that are still affected. We will provide another update when further progress is available. Jul 29, 12:19:14 GMT+0 - Identified - Following investigations with Microsoft, they have confirmed that this was a change in behaviour introduced in Teams client build 49/26040401718\. We are continuing to work with them to assess whether this behavioural change is suitable for Contact Centre scenarios and will provide further information as it becomes available. Jul 23, 12:40:42 GMT+0 - Investigating - We are investigating reports of a Microsoft Teams client behavior that occurs in certain scenarios when the Nimbus calling bot removes a user normally from a Nimbus call. In these cases, the Teams call window remains open and displays the message:
&gt; **_Removed from the call_**
&gt; _Someone just removed you from the call. You can try to rejoin._
This can occur when:
* A call is terminated from within Nimbus (Attendant Console or My Sessions).
* A call is transferred using the Attendant Console or Nimbus Assistant.
There is **no functional impact on Nimbus call handling**, and calls continue to be processed correctly. The only effect is that the Teams call window remains open and requires user interaction. Users can either ignore the window, as it will be reused for subsequent calls, or manually close it by selecting **Dismiss**.
This behavior appears to be related to the Microsoft Teams client, we have raised this **with Microsoft** and requested further investigation. We will provide updates as they become available.
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Incident</p>
<p><strong>Affected Components:</strong> </p>
<p><small>Nov <var data-var='date'> 17</var>, <var data-var='time'>11:00:19</var> GMT+0</small><br><strong>Identified</strong> -
Following our discussions with Microsoft’s product group, a change is currently being gradually rolled out to Microsoft Teams to improve the behavior described in this incident.
Our testing shows that the change already resolves the issue in certain call-flow scenarios. When a call is queued **after a service transfer**, the “Removed from the call” window is no longer displayed when the agent subsequently performs the affected call-handling actions.
However, when a call is queued **directly in the main service**, agents may still see the “Removed from the call” window when performing certain actions in Nimbus, such as transferring or parking the call. This behavior applies to both **Direct Conference** and **Broadcast** distribution.
As before, this is a **Teams client behavior and does not affect Nimbus call handling itself**. We are continuing to test the change as it becomes available and remain in contact with Microsoft regarding the scenarios that are still affected. We will provide another update when further progress is available..</p>
<p><small>Jul <var data-var='date'> 29</var>, <var data-var='time'>12:19:14</var> GMT+0</small><br><strong>Identified</strong> -
Following investigations with Microsoft, they have confirmed that this was a change in behaviour introduced in Teams client build 49/26040401718\. We are continuing to work with them to assess whether this behavioural change is suitable for Contact Centre scenarios and will provide further information as it becomes available..</p>
<p><small>Jul <var data-var='date'> 23</var>, <var data-var='time'>12:40:42</var> GMT+0</small><br><strong>Investigating</strong> -
We are investigating reports of a Microsoft Teams client behavior that occurs in certain scenarios when the Nimbus calling bot removes a user normally from a Nimbus call. In these cases, the Teams call window remains open and displays the message:
&gt; **_Removed from the call_**
&gt; _Someone just removed you from the call. You can try to rejoin._
This can occur when:
* A call is terminated from within Nimbus (Attendant Console or My Sessions).
* A call is transferred using the Attendant Console or Nimbus Assistant.
There is **no functional impact on Nimbus call handling**, and calls continue to be processed correctly. The only effect is that the Teams call window remains open and requires user interaction. Users can either ignore the window, as it will be reused for subsequent calls, or manually close it by selecting **Dismiss**.
This behavior appears to be related to the Microsoft Teams client, we have raised this **with Microsoft** and requested further investigation. We will provide updates as they become available..</p>
]]>
</content:encoded>
<pubDate>Thu, 23 Jul 2026 12:40:42 +0000</pubDate>
<link>https://status.luware.com/incident/cmrxi1zcb00vs1bk05c2a2mua</link>
<guid>https://status.luware.com/incident/cmrxi1zcb00vs1bk05c2a2mua</guid>
</item>
<item>
<title>Nimbus Presence Issues</title>
<description>
Type: Incident
Duration: 2 hours and 42 minutes
Affected Components: Microsoft Service Health, User Availability, Microsoft Service Health, User Availability, Microsoft Service Health, Microsoft Service Health, Microsoft Service Health, User Availability, User Availability, User Availability, User Availability, Microsoft Service Health, User Availability, User Availability, Microsoft Service Health, Microsoft Service Health, User Availability, Microsoft Service Health
Jun 17, 11:45:46 GMT+0 - Resolved - Our monitoring showed no further issues. Jun 17, 10:30:11 GMT+0 - Monitoring - Microsoft have identified a Teams traffic routing issue primarily affecting EMEA based users, which they have applied a remediation for. They are monitoring the service to ensure full recovery. Jun 17, 09:56:21 GMT+0 - Identified - Microsoft have posted Issue ID TM1394359 (&quot;Some users may see incorrect presence status information in Microsoft Teams&quot;) as part of their investigation into the issue. At the present time, it appears that only presence related requests against Microsoft Graph were temporarily impacted. The service is recovering, and our engineers are monitoring the ongoing resynchronization of user presence states across all Nimbus environments. Jun 17, 09:04:06 GMT+0 - Investigating - We are investigating reports of customers experiencing issues with the Teams presence state. Further updates to follow.
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Incident</p>
<p><strong>Duration:</strong> 2 hours and 42 minutes</p>
<p><strong>Affected Components:</strong> </p>
<p><small>Jun <var data-var='date'> 17</var>, <var data-var='time'>11:45:46</var> GMT+0</small><br><strong>Resolved</strong> -
Our monitoring showed no further issues..</p>
<p><small>Jun <var data-var='date'> 17</var>, <var data-var='time'>10:30:11</var> GMT+0</small><br><strong>Monitoring</strong> -
Microsoft have identified a Teams traffic routing issue primarily affecting EMEA based users, which they have applied a remediation for. They are monitoring the service to ensure full recovery..</p>
<p><small>Jun <var data-var='date'> 17</var>, <var data-var='time'>09:56:21</var> GMT+0</small><br><strong>Identified</strong> -
Microsoft have posted Issue ID TM1394359 (&quot;Some users may see incorrect presence status information in Microsoft Teams&quot;) as part of their investigation into the issue. At the present time, it appears that only presence related requests against Microsoft Graph were temporarily impacted. The service is recovering, and our engineers are monitoring the ongoing resynchronization of user presence states across all Nimbus environments..</p>
<p><small>Jun <var data-var='date'> 17</var>, <var data-var='time'>09:04:06</var> GMT+0</small><br><strong>Investigating</strong> -
We are investigating reports of customers experiencing issues with the Teams presence state. Further updates to follow..</p>
]]>
</content:encoded>
<pubDate>Wed, 17 Jun 2026 09:04:06 +0000</pubDate>
<link>https://status.luware.com/incident/cmqhugswy01l92jmumzz4gybf</link>
<guid>https://status.luware.com/incident/cmqhugswy01l92jmumzz4gybf</guid>
</item>
<item>
<title>Luware Recording - Unexpected Call Terminations</title>
<description>
Type: Incident
Duration: 2 days, 5 hours and 8 minutes
Affected Components: Microsoft Service Health, Microsoft Service Health
Apr 23, 14:42:32 GMT+0 - Resolved - As per updates in Microsoft incident TM1286773, they have confirmed that a component causing these issues has now been fully rolled back by Microsoft and they have closed their incident. Luware Recording operations teams have been monitoring all clusters and have confirmed that the incident has now been resolved. This incident will now be resolved. Apr 21, 09:35:00 GMT+0 - Monitoring - Our operations team recently identified a number of alerts relating to Unexpected Call Termination errors on all Luware Recording clusters. This could cause some calls and also recordings to terminate early and unexpectedly.
Alerts on all platforms has reduced recently. Microsoft have reported an issue under the reference TM1286773 which we believe is the root cause of this incident.
Our operations team are continuing to monitor all clusters in case of any further incidents.
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Incident</p>
<p><strong>Duration:</strong> 2 days, 5 hours and 8 minutes</p>
<p><strong>Affected Components:</strong> </p>
<p><small>Apr <var data-var='date'> 23</var>, <var data-var='time'>14:42:32</var> GMT+0</small><br><strong>Resolved</strong> -
As per updates in Microsoft incident TM1286773, they have confirmed that a component causing these issues has now been fully rolled back by Microsoft and they have closed their incident. Luware Recording operations teams have been monitoring all clusters and have confirmed that the incident has now been resolved. This incident will now be resolved..</p>
<p><small>Apr <var data-var='date'> 21</var>, <var data-var='time'>09:35:00</var> GMT+0</small><br><strong>Monitoring</strong> -
Our operations team recently identified a number of alerts relating to Unexpected Call Termination errors on all Luware Recording clusters. This could cause some calls and also recordings to terminate early and unexpectedly.
Alerts on all platforms has reduced recently. Microsoft have reported an issue under the reference TM1286773 which we believe is the root cause of this incident.
Our operations team are continuing to monitor all clusters in case of any further incidents..</p>
]]>
</content:encoded>
<pubDate>Tue, 21 Apr 2026 09:35:00 +0000</pubDate>
<link>https://status.luware.com/incident/cmo8huv49002lyyves7qzkc78</link>
<guid>https://status.luware.com/incident/cmo8huv49002lyyves7qzkc78</guid>
</item>
<item>
<title>All Clusters - Elevated Graph Response Times</title>
<description>
Type: Incident
Duration: 2 days, 1 hour and 25 minutes
Affected Components: Microsoft Service Health, Microsoft Service Health, Microsoft Service Health, Microsoft Service Health, Microsoft Service Health, Microsoft Service Health, Microsoft Service Health, Microsoft Service Health, Microsoft Service Health
Apr 23, 10:57:48 GMT+0 - Resolved - Microsoft has completed the rollback. Continued monitoring by Luware confirms that the issue has not reoccurred. Apr 22, 07:35:14 GMT+0 - Monitoring - Microsoft is in the ongoing process of rolling back changes. Luware Engineers are working closely with Microsoft&#039;s support team to ensure a full resolution and will share any related news as they become available. Apr 21, 13:42:56 GMT+0 - Monitoring - Microsoft has reported implementing changes to mitigate the root cause. Nimbus telemetry shows that the situation has improved but is not yet fully back to normal. There has been no impact to the running of Nimbus components, but customers may notice intermittent degraded performance in areas which rely on Microsoft Graph. Luware Engineers are tracking the situation closely and we will share an update when we have further news to share. Apr 21, 09:58:38 GMT+0 - Monitoring - Microsoft has published a related incident in the Azure Portal under reference TM1286773, related to availability of inbound calls in Teams. Our telemetry reports that Graph responsiveness is returning to normal thresholds and our engineers are continuing to monitor the situation. Apr 21, 09:33:01 GMT+0 - Investigating - Our engineering team is currently investigating reports from our telemetry of elevated/extended response times with Microsoft&#039;s Graph integration across all Nimbus Clusters.
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Incident</p>
<p><strong>Duration:</strong> 2 days, 1 hour and 25 minutes</p>
<p><strong>Affected Components:</strong> </p>
<p><small>Apr <var data-var='date'> 23</var>, <var data-var='time'>10:57:48</var> GMT+0</small><br><strong>Resolved</strong> -
Microsoft has completed the rollback. Continued monitoring by Luware confirms that the issue has not reoccurred..</p>
<p><small>Apr <var data-var='date'> 22</var>, <var data-var='time'>07:35:14</var> GMT+0</small><br><strong>Monitoring</strong> -
Microsoft is in the ongoing process of rolling back changes. Luware Engineers are working closely with Microsoft&#039;s support team to ensure a full resolution and will share any related news as they become available..</p>
<p><small>Apr <var data-var='date'> 21</var>, <var data-var='time'>13:42:56</var> GMT+0</small><br><strong>Monitoring</strong> -
Microsoft has reported implementing changes to mitigate the root cause. Nimbus telemetry shows that the situation has improved but is not yet fully back to normal. There has been no impact to the running of Nimbus components, but customers may notice intermittent degraded performance in areas which rely on Microsoft Graph. Luware Engineers are tracking the situation closely and we will share an update when we have further news to share..</p>
<p><small>Apr <var data-var='date'> 21</var>, <var data-var='time'>09:58:38</var> GMT+0</small><br><strong>Monitoring</strong> -
Microsoft has published a related incident in the Azure Portal under reference TM1286773, related to availability of inbound calls in Teams. Our telemetry reports that Graph responsiveness is returning to normal thresholds and our engineers are continuing to monitor the situation..</p>
<p><small>Apr <var data-var='date'> 21</var>, <var data-var='time'>09:33:01</var> GMT+0</small><br><strong>Investigating</strong> -
Our engineering team is currently investigating reports from our telemetry of elevated/extended response times with Microsoft&#039;s Graph integration across all Nimbus Clusters..</p>
]]>
</content:encoded>
<pubDate>Tue, 21 Apr 2026 09:33:01 +0000</pubDate>
<link>https://status.luware.com/incident/cmo8fee2z003ae3op1oeh0tmq</link>
<guid>https://status.luware.com/incident/cmo8fee2z003ae3op1oeh0tmq</guid>
</item>
<item>
<title>Luware Recording - Speech Analytics Delays</title>
<description>
Type: Incident
Duration: 14 days, 18 hours and 21 minutes
Affected Components: Speech Analytics, Speech Analytics
Apr 8, 08:50:35 GMT+0 - Resolved - After careful monitoring the Speech Analytics service has remained stable, therefore we will close this incident.
We sincerely apologize for any inconvenience caused by this outage.
If you have any further questions, please reach out via out HelpDesk at &lt;https://helpdesk.luware.cloud/&gt; Mar 31, 10:18:49 GMT+0 - Monitoring - We have idenitifed the root cause of the delays to Speech Analytics and now records should be transcribed. We will again leave this issue in monitoring to closely monitor any recurrences of the same issue.
Once again we apologize for any inconvenience caused. Mar 30, 08:58:07 GMT+0 - Identified - After close monitoring our operations team are still noticing delays to speech analytics services. We are working to resolve these delays as soon as possible.
Once again, we apologize for any inconvenience caused by these delays. Mar 25, 08:05:05 GMT+0 - Monitoring - We have identified the issue and have implemented a fix to resume processing the data for speech analytics as normal.
If you are still experiencing any issues please raise a case through our help desk - &lt;https://helpdesk.luware.cloud/&gt;
We will continue to monitor the services closely in case of any further problems.
We apologize for any inconvenience caused. Mar 24, 14:30:00 GMT+0 - Investigating - We are currently investigating delays to the Luware Recording Speech Analytics service. Customers may experience delays to recording transcriptions appearing in the web portal and through any export.
We are working to resolve this as soon as possible. We apologise for any inconvenience caused.
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Incident</p>
<p><strong>Duration:</strong> 14 days, 18 hours and 21 minutes</p>
<p><strong>Affected Components:</strong> </p>
<p><small>Apr <var data-var='date'> 8</var>, <var data-var='time'>08:50:35</var> GMT+0</small><br><strong>Resolved</strong> -
After careful monitoring the Speech Analytics service has remained stable, therefore we will close this incident.
We sincerely apologize for any inconvenience caused by this outage.
If you have any further questions, please reach out via out HelpDesk at &lt;https://helpdesk.luware.cloud/&gt;.</p>
<p><small>Mar <var data-var='date'> 31</var>, <var data-var='time'>10:18:49</var> GMT+0</small><br><strong>Monitoring</strong> -
We have idenitifed the root cause of the delays to Speech Analytics and now records should be transcribed. We will again leave this issue in monitoring to closely monitor any recurrences of the same issue.
Once again we apologize for any inconvenience caused..</p>
<p><small>Mar <var data-var='date'> 30</var>, <var data-var='time'>08:58:07</var> GMT+0</small><br><strong>Identified</strong> -
After close monitoring our operations team are still noticing delays to speech analytics services. We are working to resolve these delays as soon as possible.
Once again, we apologize for any inconvenience caused by these delays..</p>
<p><small>Mar <var data-var='date'> 25</var>, <var data-var='time'>08:05:05</var> GMT+0</small><br><strong>Monitoring</strong> -
We have identified the issue and have implemented a fix to resume processing the data for speech analytics as normal.
If you are still experiencing any issues please raise a case through our help desk - &lt;https://helpdesk.luware.cloud/&gt;
We will continue to monitor the services closely in case of any further problems.
We apologize for any inconvenience caused..</p>
<p><small>Mar <var data-var='date'> 24</var>, <var data-var='time'>14:30:00</var> GMT+0</small><br><strong>Investigating</strong> -
We are currently investigating delays to the Luware Recording Speech Analytics service. Customers may experience delays to recording transcriptions appearing in the web portal and through any export.
We are working to resolve this as soon as possible. We apologise for any inconvenience caused..</p>
]]>
</content:encoded>
<pubDate>Tue, 24 Mar 2026 14:30:00 +0000</pubDate>
<link>https://status.luware.com/incident/cmn4x9ond00lhupvc0mtowyxm</link>
<guid>https://status.luware.com/incident/cmn4x9ond00lhupvc0mtowyxm</guid>
</item>
<item>
<title>Luware Recording - MTCH - Nimbus Call Capture Degredation</title>
<description>
Type: Incident
Duration: 5 days, 17 hours and 58 minutes
Affected Components: Call Recording,
Recording Switzerland →
Feb 12, 09:28:27 GMT+0 - Resolved - After close monitoring, and no further issues after the fixes were put into place, we are now closing this incident.
An full RCA can be provided for this incident upon request.
**Please raise a case through our HelpDesk at** [**helpdesk.luware.cloud**](http://helpdesk.luware.cloud) **for any further questions, or to request the RCA.**
We sincerely apologize for any inconvenience caused. Feb 11, 13:30:00 GMT+0 - Monitoring - We remediated the issue and are currently monitoring the issue now. We do not expect there to be any ongoing loss of recording. Feb 6, 15:30:00 GMT+0 - Monitoring - We have identified that there has been an ongoing issue with correctly capturing and recording **Luware Nimbus calls** on Luware Recording in MTCH. A subset of calls may have not been recorded for some Luware Recording MTCH customers due to issue identified on some recording servers.
This issue will only impact customers on **Luware Recording MTCH** cluster, who have only **Contact Center IN/OUT** directions enabled for recording.
The issue has already been **identified and remediated**, we do not expect this now to be an ongoing incident. However this incident status will remain in monitoring phase whilst we conduct investigations.
A full investigation into the issue is underway and we will be able to send a full RCA upon request.
**Please raise a case through our HelpDesk at** [**helpdesk.luware.cloud**](http://helpdesk.luware.cloud) **for any further questions.**
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Incident</p>
<p><strong>Duration:</strong> 5 days, 17 hours and 58 minutes</p>
<p><strong>Affected Components:</strong> </p>
<p><small>Feb <var data-var='date'> 12</var>, <var data-var='time'>09:28:27</var> GMT+0</small><br><strong>Resolved</strong> -
After close monitoring, and no further issues after the fixes were put into place, we are now closing this incident.
An full RCA can be provided for this incident upon request.
**Please raise a case through our HelpDesk at** [**helpdesk.luware.cloud**](http://helpdesk.luware.cloud) **for any further questions, or to request the RCA.**
We sincerely apologize for any inconvenience caused..</p>
<p><small>Feb <var data-var='date'> 11</var>, <var data-var='time'>13:30:00</var> GMT+0</small><br><strong>Monitoring</strong> -
We remediated the issue and are currently monitoring the issue now. We do not expect there to be any ongoing loss of recording. .</p>
<p><small>Feb <var data-var='date'> 6</var>, <var data-var='time'>15:30:00</var> GMT+0</small><br><strong>Monitoring</strong> -
We have identified that there has been an ongoing issue with correctly capturing and recording **Luware Nimbus calls** on Luware Recording in MTCH. A subset of calls may have not been recorded for some Luware Recording MTCH customers due to issue identified on some recording servers.
This issue will only impact customers on **Luware Recording MTCH** cluster, who have only **Contact Center IN/OUT** directions enabled for recording.
The issue has already been **identified and remediated**, we do not expect this now to be an ongoing incident. However this incident status will remain in monitoring phase whilst we conduct investigations.
A full investigation into the issue is underway and we will be able to send a full RCA upon request.
**Please raise a case through our HelpDesk at** [**helpdesk.luware.cloud**](http://helpdesk.luware.cloud) **for any further questions.**.</p>
]]>
</content:encoded>
<pubDate>Fri, 6 Feb 2026 15:30:00 +0000</pubDate>
<link>https://status.luware.com/incident/cmli3g66q03n2if8zhydj9pgy</link>
<guid>https://status.luware.com/incident/cmli3g66q03n2if8zhydj9pgy</guid>
</item>
<item>
<title>Luware Support Portal Unavailable</title>
<description>
Type: Incident
Duration: 14 minutes
Affected Components: Luware Support Hotline
Dec 5, 09:22:18 GMT+0 - Resolved - This incident has been resolved and our helpdesk portal is now fully functional once again. Thank you for your patience during this time. Dec 5, 09:07:59 GMT+0 - Identified - Due to an ongoing issue with Cloudflare, the Luware Support Portal is inaccessible, which means new tickets cannot be created and our agents are unable to progress with existing tickets.
Cloudflare is not used at all in our production systems and all Luware platforms are fully operational with no service impact to Nimbus or Recording functionality.
If you have an urgent support request, our support agents are all online and reachable via our support hotline on the numbers below:
CH: +41 58 404 28 07
UK: +44 20 3300 2751
DE: +49 71 18998 9621
US: +1 646 891 1006
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Incident</p>
<p><strong>Duration:</strong> 14 minutes</p>
<p><strong>Affected Components:</strong> </p>
<p><small>Dec <var data-var='date'> 5</var>, <var data-var='time'>09:22:18</var> GMT+0</small><br><strong>Resolved</strong> -
This incident has been resolved and our helpdesk portal is now fully functional once again. Thank you for your patience during this time..</p>
<p><small>Dec <var data-var='date'> 5</var>, <var data-var='time'>09:07:59</var> GMT+0</small><br><strong>Identified</strong> -
Due to an ongoing issue with Cloudflare, the Luware Support Portal is inaccessible, which means new tickets cannot be created and our agents are unable to progress with existing tickets.
Cloudflare is not used at all in our production systems and all Luware platforms are fully operational with no service impact to Nimbus or Recording functionality.
If you have an urgent support request, our support agents are all online and reachable via our support hotline on the numbers below:
CH: +41 58 404 28 07
UK: +44 20 3300 2751
DE: +49 71 18998 9621
US: +1 646 891 1006.</p>
]]>
</content:encoded>
<pubDate>Fri, 5 Dec 2025 09:07:59 +0000</pubDate>
<link>https://status.luware.com/incident/cmisn6ih607dsvakz6pw5jk7j</link>
<guid>https://status.luware.com/incident/cmisn6ih607dsvakz6pw5jk7j</guid>
</item>
<item>
<title>Luware Recording MS Teams Bot Application Visible in calls</title>
<description>
Type: Incident
Duration: 2 days, 3 hours and 42 minutes
Affected Components: Microsoft Service Health, Microsoft Service Health
Nov 19, 14:41:35 GMT+0 - Resolved - We are now closing this incident following confirmation from Microsoft that the issue has been resolved, as well as verification through Luware monitoring and the absence of any further reported cases.
If you require any further information on this incident, please raise a case through our Luware support desk at &lt;https://helpdesk.luware.cloud&gt; Nov 18, 08:08:09 GMT+0 - Monitoring - We have been advised by Microsoft that this issue should now be resolved. We will monitor the situation to ensure there are no more occurrences of this issue.
During this incident there was no impact to recording, or any change to the behaviour of your recording configuration. The recording bot application shown as a participant in any calls does not cause any over recording.
If you are still experiencing any of the same issues, please report this to us at our support desk at &lt;https://helpdesk.luware.cloud&gt;**.** Nov 17, 16:36:51 GMT+0 - Identified - We understand that Microsoft engineering teams are investigating this issue. We have no further updates from them at this moment but we will post updates here as we have them. Nov 17, 11:00:00 GMT+0 - Identified - We are aware that many users are now seeing the Luware Recording bot application as a participant in their Microsoft teams calls. This is suspected to be a Microsoft related issue, and if you are experiencing this problem yourself, then you should raise a case to Microsoft directly reporting the problem.
If you have any other concerns, please raise a case with Luware at &lt;https://helpdesk.luware.cloud&gt;
We will continue to post updates here as we receive them from Microsoft.
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Incident</p>
<p><strong>Duration:</strong> 2 days, 3 hours and 42 minutes</p>
<p><strong>Affected Components:</strong> </p>
<p><small>Nov <var data-var='date'> 19</var>, <var data-var='time'>14:41:35</var> GMT+0</small><br><strong>Resolved</strong> -
We are now closing this incident following confirmation from Microsoft that the issue has been resolved, as well as verification through Luware monitoring and the absence of any further reported cases.
If you require any further information on this incident, please raise a case through our Luware support desk at &lt;https://helpdesk.luware.cloud&gt;.</p>
<p><small>Nov <var data-var='date'> 18</var>, <var data-var='time'>08:08:09</var> GMT+0</small><br><strong>Monitoring</strong> -
We have been advised by Microsoft that this issue should now be resolved. We will monitor the situation to ensure there are no more occurrences of this issue.
During this incident there was no impact to recording, or any change to the behaviour of your recording configuration. The recording bot application shown as a participant in any calls does not cause any over recording.
If you are still experiencing any of the same issues, please report this to us at our support desk at &lt;https://helpdesk.luware.cloud&gt;**.**.</p>
<p><small>Nov <var data-var='date'> 17</var>, <var data-var='time'>16:36:51</var> GMT+0</small><br><strong>Identified</strong> -
We understand that Microsoft engineering teams are investigating this issue. We have no further updates from them at this moment but we will post updates here as we have them..</p>
<p><small>Nov <var data-var='date'> 17</var>, <var data-var='time'>11:00:00</var> GMT+0</small><br><strong>Identified</strong> -
We are aware that many users are now seeing the Luware Recording bot application as a participant in their Microsoft teams calls. This is suspected to be a Microsoft related issue, and if you are experiencing this problem yourself, then you should raise a case to Microsoft directly reporting the problem.
If you have any other concerns, please raise a case with Luware at &lt;https://helpdesk.luware.cloud&gt;
We will continue to post updates here as we receive them from Microsoft..</p>
]]>
</content:encoded>
<pubDate>Mon, 17 Nov 2025 11:00:00 +0000</pubDate>
<link>https://status.luware.com/incident/cmi3197ig0372jhsgxw6shtsc</link>
<guid>https://status.luware.com/incident/cmi3197ig0372jhsgxw6shtsc</guid>
</item>
<item>
<title>Luware Recording - MTCH Call Recording Degradation</title>
<description>
Type: Incident
Duration: 22 hours and 9 minutes
Affected Components: Call Recording,
Recording Switzerland →
Nov 1, 07:38:35 GMT+0 - Resolved - It has been observed that the Luware Recording MTCH (Switzerland) cluster is stable now after closely monitoring the system.
We&#039;d like to thank you for your patience during this incident. Over the coming days our technical teams will be working on a full review of the situation and we will release a statement. If you would like to receive a copy of this, please contact your Luware Customer Success Representative or create a ticket at &lt;https://helpdesk.luware.cloud&gt; Oct 31, 11:35:29 GMT+0 - Monitoring - We believe the issues with conversation recording should be resolved now and customers should no longer have any issue making or receiving if they are using &quot;Fail-Close&quot; type Microsoft Teams Compliance Recording Policies.
Our metrics are showing that the Luware Recording platform is performing normally now.
If you are still experiencing ongoing issues, please raise a support case with us and an agent will be able to advise: &lt;https://helpdesk.luware.cloud&gt; Oct 31, 11:10:00 GMT+0 - Identified - We have identified an issue and we are now working to recover the services.
Customers should start to see improvements in the recording of their conversations. Oct 31, 09:29:59 GMT+0 - Investigating - We are currently investigating a large number of alerts incoming to our Luware Recording MTCH (Switzerland) cluster from Microsoft Teams relating to recording of conversations.
At this moment, recording is still active on the system, but some customers may be experiencing issues with some conversation recording, or calls terminating prematurely if customers have &quot;Fail Close&quot; type Microsoft Teams Compliance Recording policies assigned.
We will update you with more updates as soon as possible.
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Incident</p>
<p><strong>Duration:</strong> 22 hours and 9 minutes</p>
<p><strong>Affected Components:</strong> </p>
<p><small>Nov <var data-var='date'> 1</var>, <var data-var='time'>07:38:35</var> GMT+0</small><br><strong>Resolved</strong> -
It has been observed that the Luware Recording MTCH (Switzerland) cluster is stable now after closely monitoring the system.
We&#039;d like to thank you for your patience during this incident. Over the coming days our technical teams will be working on a full review of the situation and we will release a statement. If you would like to receive a copy of this, please contact your Luware Customer Success Representative or create a ticket at &lt;https://helpdesk.luware.cloud&gt;.</p>
<p><small>Oct <var data-var='date'> 31</var>, <var data-var='time'>11:35:29</var> GMT+0</small><br><strong>Monitoring</strong> -
We believe the issues with conversation recording should be resolved now and customers should no longer have any issue making or receiving if they are using &quot;Fail-Close&quot; type Microsoft Teams Compliance Recording Policies.
Our metrics are showing that the Luware Recording platform is performing normally now.
If you are still experiencing ongoing issues, please raise a support case with us and an agent will be able to advise: &lt;https://helpdesk.luware.cloud&gt;.</p>
<p><small>Oct <var data-var='date'> 31</var>, <var data-var='time'>11:10:00</var> GMT+0</small><br><strong>Identified</strong> -
We have identified an issue and we are now working to recover the services.
Customers should start to see improvements in the recording of their conversations..</p>
<p><small>Oct <var data-var='date'> 31</var>, <var data-var='time'>09:29:59</var> GMT+0</small><br><strong>Investigating</strong> -
We are currently investigating a large number of alerts incoming to our Luware Recording MTCH (Switzerland) cluster from Microsoft Teams relating to recording of conversations.
At this moment, recording is still active on the system, but some customers may be experiencing issues with some conversation recording, or calls terminating prematurely if customers have &quot;Fail Close&quot; type Microsoft Teams Compliance Recording policies assigned.
We will update you with more updates as soon as possible..</p>
]]>
</content:encoded>
<pubDate>Fri, 31 Oct 2025 09:29:59 +0000</pubDate>
<link>https://status.luware.com/incident/cmhenjzde06m4mlbwjdz8e9mw</link>
<guid>https://status.luware.com/incident/cmhenjzde06m4mlbwjdz8e9mw</guid>
</item>
<item>
<title>Luware Recording - Web Application Access</title>
<description>
Type: Incident
Duration: 16 hours and 15 minutes
Affected Components: Microsoft Service Health, Search &amp; Playback, Media Playback, Web applications, Search &amp; Retrieval, Microsoft Service Health, Media Playback, Call Recording, Storage Services, Web Applications,
Luware Recording →
Recording Switzerland →
Recording Germany →
Oct 30, 08:24:13 GMT+0 - Resolved - It was observed that Luware Recording services were restored on 29/10/25 at 20:00 UTC after Microsoft services began to recover. Subsequently Microsoft announced that their incident was fully resolved on 30/10/25 at 00:05 UTC.
We&#039;d like to thank you for your patience during this incident. Over the coming days our technical teams will be working on a full review of the situation and we will release a statement in the coming days. If you would like to receive a copy of this, please contact your Luware Customer Success Representative or create a ticket at &lt;https://helpdesk.luware.cloud&gt; Oct 29, 22:08:25 GMT+0 - Monitoring - Microsoft services now seem to have recovered and access to web applications have now been restored.
We are still closely monitoring all services.
Unfortunately, during this incident, it now appears that recording services for the MTCH (Switzerland) cluster were impacted, and no recordings will have taken place during this Microsoft service outage. Oct 29, 18:38:26 GMT+0 - Identified - Microsoft are continuing to work on the Azure Front Door side to recover services. Customers can also follow the latest available updates regarding this issue via &lt;https://azure.status.microsoft/&gt;. Oct 29, 16:42:56 GMT+0 - Identified - Microsoft has taken action to address a DNS issue on their end and are expecting this to resolve the issue shortly. Oct 29, 16:09:34 GMT+0 - Investigating - We are currently aware that some customers may not be able to access the Luware Recording web application across all Luware Recording clusters. We currently suspect this is due to an ongoing Azure incident.
At this time we only believe the web application access to be impacted. We do **not** see any impact to ongoing recording of conversations.
Our operations team are investigating the issue and we will update you with any further information as soon as its available.
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Incident</p>
<p><strong>Duration:</strong> 16 hours and 15 minutes</p>
<p><strong>Affected Components:</strong> </p>
<p><small>Oct <var data-var='date'> 30</var>, <var data-var='time'>08:24:13</var> GMT+0</small><br><strong>Resolved</strong> -
It was observed that Luware Recording services were restored on 29/10/25 at 20:00 UTC after Microsoft services began to recover. Subsequently Microsoft announced that their incident was fully resolved on 30/10/25 at 00:05 UTC.
We&#039;d like to thank you for your patience during this incident. Over the coming days our technical teams will be working on a full review of the situation and we will release a statement in the coming days. If you would like to receive a copy of this, please contact your Luware Customer Success Representative or create a ticket at &lt;https://helpdesk.luware.cloud&gt;.</p>
<p><small>Oct <var data-var='date'> 29</var>, <var data-var='time'>22:08:25</var> GMT+0</small><br><strong>Monitoring</strong> -
Microsoft services now seem to have recovered and access to web applications have now been restored.
We are still closely monitoring all services.
Unfortunately, during this incident, it now appears that recording services for the MTCH (Switzerland) cluster were impacted, and no recordings will have taken place during this Microsoft service outage..</p>
<p><small>Oct <var data-var='date'> 29</var>, <var data-var='time'>18:38:26</var> GMT+0</small><br><strong>Identified</strong> -
Microsoft are continuing to work on the Azure Front Door side to recover services. Customers can also follow the latest available updates regarding this issue via &lt;https://azure.status.microsoft/&gt;..</p>
<p><small>Oct <var data-var='date'> 29</var>, <var data-var='time'>16:42:56</var> GMT+0</small><br><strong>Identified</strong> -
Microsoft has taken action to address a DNS issue on their end and are expecting this to resolve the issue shortly..</p>
<p><small>Oct <var data-var='date'> 29</var>, <var data-var='time'>16:09:34</var> GMT+0</small><br><strong>Investigating</strong> -
We are currently aware that some customers may not be able to access the Luware Recording web application across all Luware Recording clusters. We currently suspect this is due to an ongoing Azure incident.
At this time we only believe the web application access to be impacted. We do **not** see any impact to ongoing recording of conversations.
Our operations team are investigating the issue and we will update you with any further information as soon as its available..</p>
]]>
</content:encoded>
<pubDate>Wed, 29 Oct 2025 16:09:34 +0000</pubDate>
<link>https://status.luware.com/incident/cmhc6y4ow003vl0km10rbtpyy</link>
<guid>https://status.luware.com/incident/cmhc6y4ow003vl0km10rbtpyy</guid>
</item>
<item>
<title>Azure Issues</title>
<description>
Type: Incident
Duration: 15 hours and 25 minutes
Affected Components: Microsoft Service Health, Microsoft Service Health, Microsoft Service Health, Microsoft Service Health, Microsoft Service Health, Microsoft Service Health, Microsoft Service Health, Microsoft Service Health, Microsoft Service Health, Microsoft Service Health, Microsoft Service Health
Oct 30, 07:29:56 GMT+0 - Resolved - Following intervention steps by Luware&#039;s Engineering Team, Nimbus services were restored on 29/10/25 at 19:45 UTC. Subsequently Microsoft announced that their incident was resolved on 30/10/25 at 00:05 UTC.
We&#039;d like to thank you for your patience during this incident. Over the coming days our technical teams will be working on a full review of the situation and we will release a statement in the coming days. If you would like to receive a copy of this, please contact your Luware Customer Success Representative or create a ticket at &lt;https://helpdesk.luware.cloud&gt; Oct 29, 19:53:25 GMT+0 - Monitoring - While waiting for Microsoft to fully resolve the incident, our engineering team has implemented a workaround that allows services to recover. Customers may still see the Nimbus application within their Teams client impacted, but access to the admin and user portal pages directly via the browser should now be working. Oct 29, 17:47:21 GMT+0 - Identified - Microsoft are continuing to work on the Azure Front Door side to recover services. Customers can also follow the latest available updates regarding this issue via &lt;https://azure.status.microsoft/&gt;. Oct 29, 16:39:10 GMT+0 - Identified - Microsoft has taken action to address a DNS issue on their end and are expecting results shortly. Oct 29, 16:16:46 GMT+0 - Identified - Microsoft has created service incident MO1181369\. Customers with access to the Azure admin portal can view the resolution progress via the following link:
&lt;https://admin.microsoft.com/Adminportal#/servicehealth/:/alerts/MO1181369&gt; Oct 29, 16:04:45 GMT+0 - Investigating - We are investigating reports of Azure issues impacting services. We will provide more updates as soon as possible.
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Incident</p>
<p><strong>Duration:</strong> 15 hours and 25 minutes</p>
<p><strong>Affected Components:</strong> </p>
<p><small>Oct <var data-var='date'> 30</var>, <var data-var='time'>07:29:56</var> GMT+0</small><br><strong>Resolved</strong> -
Following intervention steps by Luware&#039;s Engineering Team, Nimbus services were restored on 29/10/25 at 19:45 UTC. Subsequently Microsoft announced that their incident was resolved on 30/10/25 at 00:05 UTC.
We&#039;d like to thank you for your patience during this incident. Over the coming days our technical teams will be working on a full review of the situation and we will release a statement in the coming days. If you would like to receive a copy of this, please contact your Luware Customer Success Representative or create a ticket at &lt;https://helpdesk.luware.cloud&gt; .</p>
<p><small>Oct <var data-var='date'> 29</var>, <var data-var='time'>19:53:25</var> GMT+0</small><br><strong>Monitoring</strong> -
While waiting for Microsoft to fully resolve the incident, our engineering team has implemented a workaround that allows services to recover. Customers may still see the Nimbus application within their Teams client impacted, but access to the admin and user portal pages directly via the browser should now be working..</p>
<p><small>Oct <var data-var='date'> 29</var>, <var data-var='time'>17:47:21</var> GMT+0</small><br><strong>Identified</strong> -
Microsoft are continuing to work on the Azure Front Door side to recover services. Customers can also follow the latest available updates regarding this issue via &lt;https://azure.status.microsoft/&gt;..</p>
<p><small>Oct <var data-var='date'> 29</var>, <var data-var='time'>16:39:10</var> GMT+0</small><br><strong>Identified</strong> -
Microsoft has taken action to address a DNS issue on their end and are expecting results shortly..</p>
<p><small>Oct <var data-var='date'> 29</var>, <var data-var='time'>16:16:46</var> GMT+0</small><br><strong>Identified</strong> -
Microsoft has created service incident MO1181369\. Customers with access to the Azure admin portal can view the resolution progress via the following link:
&lt;https://admin.microsoft.com/Adminportal#/servicehealth/:/alerts/MO1181369&gt;.</p>
<p><small>Oct <var data-var='date'> 29</var>, <var data-var='time'>16:04:45</var> GMT+0</small><br><strong>Investigating</strong> -
We are investigating reports of Azure issues impacting services. We will provide more updates as soon as possible..</p>
]]>
</content:encoded>
<pubDate>Wed, 29 Oct 2025 16:04:45 +0000</pubDate>
<link>https://status.luware.com/incident/cmhc6ry5h002i9fzvo9lbzsqz</link>
<guid>https://status.luware.com/incident/cmhc6ry5h002i9fzvo9lbzsqz</guid>
</item>
<item>
<title>Luware Recording - Web Application Access Issue</title>
<description>
Type: Incident
Duration: 7 hours and 38 minutes
Affected Components: Media Playback, Search &amp; Playback, Media Playback, Web applications, Search &amp; Retrieval, Web Applications
Oct 21, 15:44:19 GMT+0 - Resolved - After close monitoring this incident has now been resolved.
We apologise for the inconvenience caused.
A full RCA of the incident will be available upon request by raising a support ticket with Luware Support at &lt;https://helpdesk.luware.cloud&gt; Oct 21, 08:10:05 GMT+0 - Monitoring - Access to the web applications has now been restored.
We are currently monitoring the access in case of any further issues.
Please contact our support if you have any further questions or issues. Oct 21, 08:06:26 GMT+0 - Investigating - You may be experiencing issues with accessing the Luware Recording web application platform, by receiving 502 Bad Gateway errors.
We are currently aware of this and are investigating this as a high priority and will update once we have an update.
Ongoing recording of all conversations is **not** impacted by this issue, only access to the web application.
We apologise for the inconvenience caused.
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Incident</p>
<p><strong>Duration:</strong> 7 hours and 38 minutes</p>
<p><strong>Affected Components:</strong> </p>
<p><small>Oct <var data-var='date'> 21</var>, <var data-var='time'>15:44:19</var> GMT+0</small><br><strong>Resolved</strong> -
After close monitoring this incident has now been resolved.
We apologise for the inconvenience caused.
A full RCA of the incident will be available upon request by raising a support ticket with Luware Support at &lt;https://helpdesk.luware.cloud&gt;.</p>
<p><small>Oct <var data-var='date'> 21</var>, <var data-var='time'>08:10:05</var> GMT+0</small><br><strong>Monitoring</strong> -
Access to the web applications has now been restored.
We are currently monitoring the access in case of any further issues.
Please contact our support if you have any further questions or issues..</p>
<p><small>Oct <var data-var='date'> 21</var>, <var data-var='time'>08:06:26</var> GMT+0</small><br><strong>Investigating</strong> -
You may be experiencing issues with accessing the Luware Recording web application platform, by receiving 502 Bad Gateway errors.
We are currently aware of this and are investigating this as a high priority and will update once we have an update.
Ongoing recording of all conversations is **not** impacted by this issue, only access to the web application.
We apologise for the inconvenience caused..</p>
]]>
</content:encoded>
<pubDate>Tue, 21 Oct 2025 08:06:26 +0000</pubDate>
<link>https://status.luware.com/incident/cmh0a5zup00mhcn0tlwakk706</link>
<guid>https://status.luware.com/incident/cmh0a5zup00mhcn0tlwakk706</guid>
</item>
<item>
<title>Azure Issues</title>
<description>
Type: Incident
Duration: 10 hours and 11 minutes
Affected Components: Microsoft Service Health, Microsoft Service Health, Microsoft Service Health, Microsoft Service Health, Microsoft Service Health, Microsoft Service Health, Microsoft Service Health, Microsoft Service Health, Microsoft Service Health, Microsoft Service Health, Microsoft Service Health
Oct 10, 09:20:18 GMT+0 - Postmortem - Microsoft have released a Post Incident Review (PIR) available at [Azure status history](https://azure.status.microsoft/en-us/status/history/) for the tracking ID **QNBQ-5W8**. Oct 9, 16:00:00 GMT+0 - Resolved - Our monitoring shows that all services are fully back to normal operations. Oct 9, 12:56:29 GMT+0 - Monitoring - We have received updates from several customers indicating that the issue is largely resolved. Microsoft has yet to confirm the complete resolution yet. Meanwhile, our team has already started clean-up operations to ensure that the Azure Front Door issue has no lingering impact on customer services. Oct 9, 11:15:29 GMT+0 - Monitoring - Microsoft is restoring the Azure Front Door services. Our own telemetry is showing signs of recovery, but no full resolution yet.
We will keep monitoring the situation until it is fully resolved. Oct 9, 10:15:55 GMT+0 - Identified - Luware engineers are in active contact with Microsoft&#039;s support team. Microsoft is presently looking into Azure Front Door capacity issues as part of this incident. Oct 9, 09:13:56 GMT+0 - Investigating - Microsoft has received related reports and has started an investigation as well.
Customers with access to the Azure Service Health portal will be able to see more details under the following link:
&lt;https://admin.cloud.microsoft/?#/servicehealth/:/alerts/MO1168665&gt;
You may notice other issues related to solutions that rely on Microsoft Azure and Entra unrelated to Luware. Oct 9, 08:49:02 GMT+0 - Investigating - We are receiving reports about widespread Azure issues impacting the availability of our portal pages and services.
Our team is investigating these and will provide updates as soon as new information becomes available.
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Incident</p>
<p><strong>Duration:</strong> 10 hours and 11 minutes</p>
<p><strong>Affected Components:</strong> </p>
<p><small>Oct <var data-var='date'> 10</var>, <var data-var='time'>09:20:18</var> GMT+0</small><br><strong>Postmortem</strong> -
Microsoft have released a Post Incident Review (PIR) available at [Azure status history](https://azure.status.microsoft/en-us/status/history/) for the tracking ID **QNBQ-5W8**..</p>
<p><small>Oct <var data-var='date'> 9</var>, <var data-var='time'>16:00:00</var> GMT+0</small><br><strong>Resolved</strong> -
Our monitoring shows that all services are fully back to normal operations..</p>
<p><small>Oct <var data-var='date'> 9</var>, <var data-var='time'>12:56:29</var> GMT+0</small><br><strong>Monitoring</strong> -
We have received updates from several customers indicating that the issue is largely resolved. Microsoft has yet to confirm the complete resolution yet. Meanwhile, our team has already started clean-up operations to ensure that the Azure Front Door issue has no lingering impact on customer services..</p>
<p><small>Oct <var data-var='date'> 9</var>, <var data-var='time'>11:15:29</var> GMT+0</small><br><strong>Monitoring</strong> -
Microsoft is restoring the Azure Front Door services. Our own telemetry is showing signs of recovery, but no full resolution yet.
We will keep monitoring the situation until it is fully resolved..</p>
<p><small>Oct <var data-var='date'> 9</var>, <var data-var='time'>10:15:55</var> GMT+0</small><br><strong>Identified</strong> -
Luware engineers are in active contact with Microsoft&#039;s support team. Microsoft is presently looking into Azure Front Door capacity issues as part of this incident..</p>
<p><small>Oct <var data-var='date'> 9</var>, <var data-var='time'>09:13:56</var> GMT+0</small><br><strong>Investigating</strong> -
Microsoft has received related reports and has started an investigation as well.
Customers with access to the Azure Service Health portal will be able to see more details under the following link:
&lt;https://admin.cloud.microsoft/?#/servicehealth/:/alerts/MO1168665&gt;
You may notice other issues related to solutions that rely on Microsoft Azure and Entra unrelated to Luware..</p>
<p><small>Oct <var data-var='date'> 9</var>, <var data-var='time'>08:49:02</var> GMT+0</small><br><strong>Investigating</strong> -
We are receiving reports about widespread Azure issues impacting the availability of our portal pages and services.
Our team is investigating these and will provide updates as soon as new information becomes available..</p>
]]>
</content:encoded>
<pubDate>Thu, 9 Oct 2025 08:49:02 +0000</pubDate>
<link>https://status.luware.com/incident/cmgj6eky502oiz2gqnus1n56h</link>
<guid>https://status.luware.com/incident/cmgj6eky502oiz2gqnus1n56h</guid>
</item>
<item>
<title>Microsoft Azure multi-service impact in Switzerland North</title>
<description>
Type: Incident
Duration: 5 hours and 36 minutes
Affected Components: Microsoft Service Health, Microsoft Service Health, Microsoft Service Health, Microsoft Service Health,
Recording Switzerland →
Nimbus Switzerland 01 →
Sep 27, 05:30:00 GMT+0 - Resolved - Our monitoring showed no further issues with our services.
In addition to the information made available through the Azure Status pages, Microsoft have also published a related incident under issue ID MO1160527 in the service health section of the Azure portal. Sep 27, 04:00:00 GMT+0 - Monitoring - We are seeing services recovering and will continue to monitor the situation. Sep 26, 23:54:00 GMT+0 - Investigating - According to Microsoft, a recent deployment is causing issues with Azure resources in the Switzerland North region, which is impacting the Luware Nimbus and Recording environments in CH-01 as well. Microsoft has pinpointed the deployment error and is expecting the issue to be fully mitigated by 05:30 UTC. Please see &lt;https://portal.azure.com/#view/Microsoft%5FAzure%5FHealth/AzureHealthBrowseBlade/\~/serviceIssues&gt; or &lt;https://azure.status.microsoft/en-us/status&gt; for more details and regular updates.
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Incident</p>
<p><strong>Duration:</strong> 5 hours and 36 minutes</p>
<p><strong>Affected Components:</strong> </p>
<p><small>Sep <var data-var='date'> 27</var>, <var data-var='time'>05:30:00</var> GMT+0</small><br><strong>Resolved</strong> -
Our monitoring showed no further issues with our services.
In addition to the information made available through the Azure Status pages, Microsoft have also published a related incident under issue ID MO1160527 in the service health section of the Azure portal..</p>
<p><small>Sep <var data-var='date'> 27</var>, <var data-var='time'>04:00:00</var> GMT+0</small><br><strong>Monitoring</strong> -
We are seeing services recovering and will continue to monitor the situation..</p>
<p><small>Sep <var data-var='date'> 26</var>, <var data-var='time'>23:54:00</var> GMT+0</small><br><strong>Investigating</strong> -
According to Microsoft, a recent deployment is causing issues with Azure resources in the Switzerland North region, which is impacting the Luware Nimbus and Recording environments in CH-01 as well. Microsoft has pinpointed the deployment error and is expecting the issue to be fully mitigated by 05:30 UTC. Please see &lt;https://portal.azure.com/#view/Microsoft%5FAzure%5FHealth/AzureHealthBrowseBlade/\~/serviceIssues&gt; or &lt;https://azure.status.microsoft/en-us/status&gt; for more details and regular updates..</p>
]]>
</content:encoded>
<pubDate>Fri, 26 Sep 2025 23:54:00 +0000</pubDate>
<link>https://status.luware.com/incident/cmg1rg2cl0085q2qnrlq8yakh</link>
<guid>https://status.luware.com/incident/cmg1rg2cl0085q2qnrlq8yakh</guid>
</item>
<item>
<title>Changes to Teams Call Toast</title>
<description>
Type: Incident
Duration: 6 days and 15 minutes
Affected Components: Microsoft Service Health
Sep 18, 09:37:35 GMT+0 - Resolved - Microsoft has reverted a change which caused this behaviour and multiple Nimbus customers have confirmed full resolution. If you have any further questions, please raise a ticket at &lt;https://helpdesk.luware.cloud&gt; Sep 12, 09:22:21 GMT+0 - Investigating - Our support and engineering teams are currently investigating isolated reports of the Teams call toast changing from a normal call toast, to a meeting invitation for Nimbus calls.
Users have reported that this change renders the &quot;Join&quot; button inoperable, preventing them from being able to accept Nimbus calls.
Luware Support has confirmed that this problem is not present when using the Teams Mobile App or via the Web. If you find that you are affected by this issue, please log into Teams on mobile or via the web to maintain operations.
We are working with Microsoft Support to find the cause and a resolution.
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Incident</p>
<p><strong>Duration:</strong> 6 days and 15 minutes</p>
<p><strong>Affected Components:</strong> </p>
<p><small>Sep <var data-var='date'> 18</var>, <var data-var='time'>09:37:35</var> GMT+0</small><br><strong>Resolved</strong> -
Microsoft has reverted a change which caused this behaviour and multiple Nimbus customers have confirmed full resolution. If you have any further questions, please raise a ticket at &lt;https://helpdesk.luware.cloud&gt; .</p>
<p><small>Sep <var data-var='date'> 12</var>, <var data-var='time'>09:22:21</var> GMT+0</small><br><strong>Investigating</strong> -
Our support and engineering teams are currently investigating isolated reports of the Teams call toast changing from a normal call toast, to a meeting invitation for Nimbus calls.
Users have reported that this change renders the &quot;Join&quot; button inoperable, preventing them from being able to accept Nimbus calls.
Luware Support has confirmed that this problem is not present when using the Teams Mobile App or via the Web. If you find that you are affected by this issue, please log into Teams on mobile or via the web to maintain operations.
We are working with Microsoft Support to find the cause and a resolution..</p>
]]>
</content:encoded>
<pubDate>Fri, 12 Sep 2025 09:22:21 +0000</pubDate>
<link>https://status.luware.com/incident/cmfgmpfdf003p4rat39x5enmt</link>
<guid>https://status.luware.com/incident/cmfgmpfdf003p4rat39x5enmt</guid>
</item>
<item>
<title>Luware Recording MTDE - Login Issues</title>
<description>
Type: Incident
Duration: 6 hours and 5 minutes
Affected Components: Web applications
Sep 8, 17:05:05 GMT+0 - Resolved - This incident is now resolved after closely monitoring the fix that was made to rectify the original issues.
Please reach out to our HelpDesk if you have any further issues or concerns.
An RCA for this incident is available upon request through raising a ticket through our HelpDesk.
Luware sincerely apologies for any inconvenience caused with this incident. Sep 8, 12:07:32 GMT+0 - Monitoring - We have now implemented a fix and we are now monitoring the status of the issue.
Please report via our HelpDesk if you are still experiencing any ongoing problems Sep 8, 11:00:28 GMT+0 - Investigating - We are investigating reports of **login issues** for users attempting to login to our Luware Recording MTDE cluster web application.
**Please not there is no current impact to any recording or capture of conversations**
Further updates will follow detailing the investigations.
Please reach out via our HelpDesk if you have any other concerns relating to this incident.
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Incident</p>
<p><strong>Duration:</strong> 6 hours and 5 minutes</p>
<p><strong>Affected Components:</strong> </p>
<p><small>Sep <var data-var='date'> 8</var>, <var data-var='time'>17:05:05</var> GMT+0</small><br><strong>Resolved</strong> -
This incident is now resolved after closely monitoring the fix that was made to rectify the original issues.
Please reach out to our HelpDesk if you have any further issues or concerns.
An RCA for this incident is available upon request through raising a ticket through our HelpDesk.
Luware sincerely apologies for any inconvenience caused with this incident..</p>
<p><small>Sep <var data-var='date'> 8</var>, <var data-var='time'>12:07:32</var> GMT+0</small><br><strong>Monitoring</strong> -
We have now implemented a fix and we are now monitoring the status of the issue.
Please report via our HelpDesk if you are still experiencing any ongoing problems.</p>
<p><small>Sep <var data-var='date'> 8</var>, <var data-var='time'>11:00:28</var> GMT+0</small><br><strong>Investigating</strong> -
We are investigating reports of **login issues** for users attempting to login to our Luware Recording MTDE cluster web application.
**Please not there is no current impact to any recording or capture of conversations**
Further updates will follow detailing the investigations.
Please reach out via our HelpDesk if you have any other concerns relating to this incident..</p>
]]>
</content:encoded>
<pubDate>Mon, 8 Sep 2025 11:00:28 +0000</pubDate>
<link>https://status.luware.com/incident/cmfb0g6a1000tf0l8o3sf8wv9</link>
<guid>https://status.luware.com/incident/cmfb0g6a1000tf0l8o3sf8wv9</guid>
</item>
</channel>
</rss>