<?xml version="1.0" encoding="UTF-8" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:webfeeds="http://webfeeds.org/rss/1.0" xmlns:media="http://search.yahoo.com/mrss/">
    <channel>
        <title>Lancom Status</title>
        <link>https://status.cloud.lancom.de/rss</link>
        <description><![CDATA[Status Feed]]></description>
        <atom:link href="http://195.201.4.14/" rel="self"></atom:link>
                                                                <language>en</language>
        <lastBuildDate>Fri, 15 May 2026 21:08:42 +0000</lastBuildDate>
                <item>
            <title><![CDATA[Device tunnel in the LMC currently not working]]></title>
                        <link>https://status.cloud.lancom.de/incidents/57/</link>
            <guid isPermaLink="true">https://status.cloud.lancom.de/incidents/57/</guid>
            <description><![CDATA[The device tunnels (WEBconfig and Terminal) in the LMC are currently not working.

We are working on the issue and apologize for the inconvenience.]]></description>
                        <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Lancom Status</dc:creator>
            <pubDate>Mon, 11 May 2026 05:30:00 +0000</pubDate>
                                                                                                        </item>
                <item>
            <title><![CDATA[LMC not reachable via DNS due to disription of DNS resolution when using .de domains]]></title>
                        <link>https://status.cloud.lancom.de/incidents/56/</link>
            <guid isPermaLink="true">https://status.cloud.lancom.de/incidents/56/</guid>
            <description><![CDATA[There was a disruption of DNS resolution when using .de domains (managed by DENIC) on 05.05.2026 from approximately 22:00 CET till 06.05.2026 at approximately 1:45 CET.

As a result, some customers were unable to access the LMC during this period.]]></description>
                        <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Lancom Status</dc:creator>
            <pubDate>Tue, 05 May 2026 20:00:00 +0000</pubDate>
                                                                                                        </item>
                <item>
            <title><![CDATA[Configuration rollouts not possible and monitoring limited]]></title>
                        <link>https://status.cloud.lancom.de/incidents/55/</link>
            <guid isPermaLink="true">https://status.cloud.lancom.de/incidents/55/</guid>
            <description><![CDATA[Due to a disruption in the LMC several functions do not work:
- Configuration rollouts are not possible 
- Device monitoring is limited
- Site, network and security management are not usable

We are currently working on this issue and apologize for the inconvenience.

Update 15:30 CET: The issue has been resolved]]></description>
                        <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Lancom Status</dc:creator>
            <pubDate>Thu, 23 Apr 2026 11:15:00 +0000</pubDate>
                                                                                                        </item>
                <item>
            <title><![CDATA[Switch-Rollout have not been persisted]]></title>
                        <link>https://status.cloud.lancom.de/incidents/58/</link>
            <guid isPermaLink="true">https://status.cloud.lancom.de/incidents/58/</guid>
            <description><![CDATA[Switch configuration rollouts were not saved to persistent memory from the 23rd of April 2026 13:00 German Time. 
Rollouts after the 13th of May 2026 17:00 German Time are save again.
To fix the problem a new configuration rollout will persist the configuration again. ]]></description>
                        <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Lancom Status</dc:creator>
            <pubDate>Thu, 23 Apr 2026 11:00:00 +0000</pubDate>
                                                                                                        </item>
                <item>
            <title><![CDATA[LMC device rollout issues]]></title>
                        <link>https://status.cloud.lancom.de/incidents/54/</link>
            <guid isPermaLink="true">https://status.cloud.lancom.de/incidents/54/</guid>
            <description><![CDATA[It is currently possible, that devices in the LMC are offline. During the offline period, device statistics are not collected in the LMC. Device rollouts are sometimes also not possible.

We are currently working on this issue and apologize for the inconvenience.

Update 2026-03-25 / 03:25 pm CET: The issue has been fixed.]]></description>
                        <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Lancom Status</dc:creator>
            <pubDate>Wed, 25 Mar 2026 10:11:00 +0000</pubDate>
                                                                                                        </item>
                <item>
            <title><![CDATA[Some devices change their online status frequently in the LMC]]></title>
                        <link>https://status.cloud.lancom.de/incidents/53/</link>
            <guid isPermaLink="true">https://status.cloud.lancom.de/incidents/53/</guid>
            <description><![CDATA[It is currently possible, that devices in the LMC frequently change between offline and online status. During the offline period, device statistics are not collected in the LMC.

We are currently working on this issue and apologize for the inconvenience.

Update 2026-03-19 / 01:43 pm CET: The issue has been fixed.]]></description>
                        <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Lancom Status</dc:creator>
            <pubDate>Thu, 19 Mar 2026 12:10:00 +0000</pubDate>
                                                                                                        </item>
                <item>
            <title><![CDATA[Device Reconnection in Public LMC]]></title>
                        <link>https://status.cloud.lancom.de/incidents/52/</link>
            <guid isPermaLink="true">https://status.cloud.lancom.de/incidents/52/</guid>
            <description><![CDATA[Today at 10:15 AM CET, approximately 50% of LMC devices were disconnected from the Public LMC cloud.lancom.de. 

The cause and further service unavailability is currently being investigated. All devices were back online by 10:25 AM CET.]]></description>
                        <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Lancom Status</dc:creator>
            <pubDate>Tue, 10 Mar 2026 09:15:00 +0000</pubDate>
                                                                                                        </item>
                <item>
            <title><![CDATA[LMC down due to datacenter outage]]></title>
                        <link>https://status.cloud.lancom.de/incidents/51/</link>
            <guid isPermaLink="true">https://status.cloud.lancom.de/incidents/51/</guid>
            <description><![CDATA[All LMC services are affected. We are working on a solution and apologise for the inconvenience.

Update: 17:48: All systems are back to normal, still investigationg
Update: 18:12 Incident closed]]></description>
                        <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Lancom Status</dc:creator>
            <pubDate>Thu, 08 Jan 2026 15:50:00 +0000</pubDate>
                                                                                                        </item>
                <item>
            <title><![CDATA[LMC chat currently unavailable]]></title>
                        <link>https://status.cloud.lancom.de/incidents/50/</link>
            <guid isPermaLink="true">https://status.cloud.lancom.de/incidents/50/</guid>
            <description><![CDATA[We are working to resolve the issue and apologize for any inconvenience.]]></description>
                        <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Lancom Status</dc:creator>
            <pubDate>Wed, 10 Dec 2025 11:00:00 +0000</pubDate>
                                                                                                        </item>
                <item>
            <title><![CDATA[Configuration rollouts not possible]]></title>
                        <link>https://status.cloud.lancom.de/incidents/49/</link>
            <guid isPermaLink="true">https://status.cloud.lancom.de/incidents/49/</guid>
            <description><![CDATA[We have investigated and already fixed the issue. 

If a device is stuck in "Updating", this can be fixed by starting another rollout.

]]></description>
                        <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Lancom Status</dc:creator>
            <pubDate>Thu, 04 Dec 2025 08:30:00 +0000</pubDate>
                                                                                                        </item>
                <item>
            <title><![CDATA[Config rollouts, claiming and firmware updates still disrupted]]></title>
                        <link>https://status.cloud.lancom.de/incidents/48/</link>
            <guid isPermaLink="true">https://status.cloud.lancom.de/incidents/48/</guid>
            <description><![CDATA[We are currently in the process of fixing the issue. We will inform you as soon as there are new developments.

Update 11.11.2025 / 3pm CET: We have fixed the issue and the mentioned services are back to normal. We apologise for the inconvenience.]]></description>
                        <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Lancom Status</dc:creator>
            <pubDate>Tue, 11 Nov 2025 14:00:00 +0000</pubDate>
                                                                                                        </item>
                <item>
            <title><![CDATA[Config rollouts, claiming and firmware updates have been disrupted]]></title>
                        <link>https://status.cloud.lancom.de/incidents/47/</link>
            <guid isPermaLink="true">https://status.cloud.lancom.de/incidents/47/</guid>
            <description><![CDATA[We are currently investigating the cause of the interference. Network operation and LTA & cloud-managed hotspots are not affected.]]></description>
                        <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Lancom Status</dc:creator>
            <pubDate>Mon, 10 Nov 2025 10:30:00 +0000</pubDate>
                                                                                                        </item>
                <item>
            <title><![CDATA[Disuption of the monitoring service in the LMC]]></title>
                        <link>https://status.cloud.lancom.de/incidents/46/</link>
            <guid isPermaLink="true">https://status.cloud.lancom.de/incidents/46/</guid>
            <description><![CDATA[In rare cases the monitoring in the WLAN & LAN Dashboard as well as for the Cloud round trip time and CPU load in the Device overview was not shown correctly due to a disruption of the monitoring service in the LMC.

Network operations were not affected from this issue.

We resolved the issue and apologize for any inconvenience caused.]]></description>
                        <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Lancom Status</dc:creator>
            <pubDate>Wed, 15 Oct 2025 10:00:00 +0000</pubDate>
                                                                                                        </item>
                <item>
            <title><![CDATA[Delayed configuration rollout in the LMC]]></title>
                        <link>https://status.cloud.lancom.de/incidents/45/</link>
            <guid isPermaLink="true">https://status.cloud.lancom.de/incidents/45/</guid>
            <description><![CDATA[There was an issue where configuration rollouts took several minutes. We investigated the issue and fixed it. The system is now running normally again.]]></description>
                        <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Lancom Status</dc:creator>
            <pubDate>Wed, 30 Jul 2025 12:53:00 +0000</pubDate>
                                                                                                        </item>
                <item>
            <title><![CDATA[LMC devices were temporarily not connected]]></title>
                        <link>https://status.cloud.lancom.de/incidents/44/</link>
            <guid isPermaLink="true">https://status.cloud.lancom.de/incidents/44/</guid>
            <description><![CDATA[On Monday, 23 June 2025, some devices were not connected to the LMC from 8:15 a.m. to approximately 8:50 a.m. due to a service disruption. Network operations were not affected. We apologise for any inconvenience caused.]]></description>
                        <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Lancom Status</dc:creator>
            <pubDate>Mon, 23 Jun 2025 06:15:00 +0000</pubDate>
                                                                                                        </item>
                <item>
            <title><![CDATA[LMC not accessible due to incident at hoster]]></title>
                        <link>https://status.cloud.lancom.de/incidents/43/</link>
            <guid isPermaLink="true">https://status.cloud.lancom.de/incidents/43/</guid>
            <description><![CDATA[Due to an incident at the hoster, the LMC was not accessible between 12:44 pm & 12:46 pm CEST and again between 13:01 pm & 13:03 pm CEST.

All Lancom devices were reconnected a few minutes after the downtimes. Network operations were not affected.

We apologise for any inconvenience caused.]]></description>
                        <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Lancom Status</dc:creator>
            <pubDate>Tue, 20 May 2025 10:44:00 +0000</pubDate>
                                                                                                        </item>
                <item>
            <title><![CDATA[Irragulations in the Control- and Monitoring services]]></title>
                        <link>https://status.cloud.lancom.de/incidents/42/</link>
            <guid isPermaLink="true">https://status.cloud.lancom.de/incidents/42/</guid>
            <description><![CDATA[Due to the irragulations in the Control- and Monitoring services, some devices may be displayed as “offline” in the LMC and monitoring data may not be displayed for a short period. Networking operations are not affected.

We apologize for the inconvenience.]]></description>
                        <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Lancom Status</dc:creator>
            <pubDate>Wed, 07 May 2025 15:00:00 +0000</pubDate>
                                                                                                        </item>
                <item>
            <title><![CDATA[Disruption in the LMC between 3:35 CEST and 3:46 CEST]]></title>
                        <link>https://status.cloud.lancom.de/incidents/41/</link>
            <guid isPermaLink="true">https://status.cloud.lancom.de/incidents/41/</guid>
            <description><![CDATA[Today the LMC was disturbed from approx. 3:35 CEST to 3:46 CEST. During this time, the LMC could only be used to a limited extent. Some devices were displayed as offline and monitoring was not possible.

The disruption has been fixed. We apologize for the inconvenience.]]></description>
                        <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Lancom Status</dc:creator>
            <pubDate>Mon, 05 May 2025 13:35:00 +0000</pubDate>
                                                                                                        </item>
                <item>
            <title><![CDATA[Disruption in the LMC]]></title>
                        <link>https://status.cloud.lancom.de/incidents/40/</link>
            <guid isPermaLink="true">https://status.cloud.lancom.de/incidents/40/</guid>
            <description><![CDATA[The disruption causes devices to be shown as "offline" and monitoring data not to be transmitted.]]></description>
                        <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Lancom Status</dc:creator>
            <pubDate>Tue, 22 Apr 2025 12:57:00 +0000</pubDate>
                                                                                                        </item>
                <item>
            <title><![CDATA[LMC device service disrupted]]></title>
                        <link>https://status.cloud.lancom.de/incidents/39/</link>
            <guid isPermaLink="true">https://status.cloud.lancom.de/incidents/39/</guid>
            <description><![CDATA[Due to a disruption in the device service, some devices were displayed as offline in the LMC even though they were connected to the LMC.

Network operations were not affected from this issue.

We resolved the issue and apologise for any inconvenience caused.]]></description>
                        <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Lancom Status</dc:creator>
            <pubDate>Thu, 17 Apr 2025 09:00:00 +0000</pubDate>
                                                                                                        </item>
                <item>
            <title><![CDATA[LMC login not possible]]></title>
                        <link>https://status.cloud.lancom.de/incidents/38/</link>
            <guid isPermaLink="true">https://status.cloud.lancom.de/incidents/38/</guid>
            <description><![CDATA[On Tuesday, 25 March 2025, it was not possible to log in to the LMC between 10:51 a.m. and around 11:20 a.m. CET. Network operations were not affected by the issue. The problem has been resolved and we apologise for the inconvenience.]]></description>
                        <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Lancom Status</dc:creator>
            <pubDate>Tue, 25 Mar 2025 09:51:00 +0000</pubDate>
                                                                                                        </item>
                <item>
            <title><![CDATA[Devices lost connection to LMC]]></title>
                        <link>https://status.cloud.lancom.de/incidents/37/</link>
            <guid isPermaLink="true">https://status.cloud.lancom.de/incidents/37/</guid>
            <description><![CDATA[Due to a problem at the hoster, there was an exceptionally high load on a service. This resulted in the devices connected with the LMC marked as "offline" between approx. 5:30 a.m. and 7:15 a.m. CET. This behavior was fixed as quickly as possible.

During this time, no monitoring data was collected from the affected devices and typical cloud services related to the affected devices (config rollout, pairing, public spot, LTA) were partially unavailable.

We will provide additional information, as soon as it is available.

We apologize for the inconvenience.]]></description>
                        <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Lancom Status</dc:creator>
            <pubDate>Tue, 11 Mar 2025 04:30:00 +0000</pubDate>
                                                                                                        </item>
                <item>
            <title><![CDATA[&quot;Device Offline&quot; notifications on cloud.lancom.de]]></title>
                        <link>https://status.cloud.lancom.de/incidents/36/</link>
            <guid isPermaLink="true">https://status.cloud.lancom.de/incidents/36/</guid>
            <description><![CDATA[On March 2nd, between 5:45 a.m. and 08:45 a.m. CET the Public LMC has lost the information about connected LANCOM devices. Almost all devices were marked offline.

Email notifications were sent but in reality all devices were properly connected with the LMC. There should be no gaps in the device monitoring data.]]></description>
                        <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Lancom Status</dc:creator>
            <pubDate>Sun, 02 Mar 2025 04:45:00 +0000</pubDate>
                                                                                                        </item>
                <item>
            <title><![CDATA[Outage of the Cloud-managed Hotspot]]></title>
                        <link>https://status.cloud.lancom.de/incidents/35/</link>
            <guid isPermaLink="true">https://status.cloud.lancom.de/incidents/35/</guid>
            <description><![CDATA[Currently there is an outage of the Cloud-managed Hotspot in the LMC. We apologize for the inconvenience.

The outage can be remedied by restarting all access points used by the Cloud-managed Hotspot.

You can find a guide on how to fix the issue under the following URL:

https://knowledgebase.lancom-systems.de/x/JgLiD]]></description>
                        <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Lancom Status</dc:creator>
            <pubDate>Tue, 21 Jan 2025 12:34:00 +0000</pubDate>
                                                                                                        </item>
                <item>
            <title><![CDATA[Issues with LMC Dashboards and LMC Main menu]]></title>
                        <link>https://status.cloud.lancom.de/incidents/34/</link>
            <guid isPermaLink="true">https://status.cloud.lancom.de/incidents/34/</guid>
            <description><![CDATA[Due to a problem with some LMC services, no data was displayed on the LMC dashboards from around 11:35 p.m. on December 1st to around 12:28 a.m. on December 2nd, and the menu on the left side of the configuration interface could not be used.

The problems have been resolved. We apologize for the inconvenience.]]></description>
                        <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Lancom Status</dc:creator>
            <pubDate>Sun, 01 Dec 2024 22:35:00 +0000</pubDate>
                                                                                                        </item>
                <item>
            <title><![CDATA[Monitoring data of devices newly connected with the LMC was not shown in the LMC]]></title>
                        <link>https://status.cloud.lancom.de/incidents/33/</link>
            <guid isPermaLink="true">https://status.cloud.lancom.de/incidents/33/</guid>
            <description><![CDATA[Monitoring data of devices newly connected with the LMC (between 13.11 approximately 08:00 CET and 15.11.2024 17:00 CET) was not shown in the LMC.

If the monotoring data of your device is still not shown in the LMC, LANCOM Systems recommends to perform a restart of the device, so that the monitoring service of the device is reinitialized,

LANCOM Systems will also implement a new feature, which will reinitialize the monitoring service of all devices. In this case, the restart is not necessary. This feature is expected to be released this week (calendar week 47).]]></description>
                        <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Lancom Status</dc:creator>
            <pubDate>Mon, 18 Nov 2024 14:34:00 +0000</pubDate>
                                                                                                        </item>
                <item>
            <title><![CDATA[Gaps in monitoring data]]></title>
                        <link>https://status.cloud.lancom.de/incidents/32/</link>
            <guid isPermaLink="true">https://status.cloud.lancom.de/incidents/32/</guid>
            <description><![CDATA[During the LMC maintenance on November 12, 2024, technical difficulties occurred. As a result, there were gaps in the monitoring data from 00:00 a.m. to about 07:30 a.m. on November 13, 2024, which unfortunately cannot be restored.

We apologize for the inconvenience.]]></description>
                        <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Lancom Status</dc:creator>
            <pubDate>Tue, 12 Nov 2024 23:00:00 +0000</pubDate>
                                                                                                        </item>
                <item>
            <title><![CDATA[Floor plans are not displayed in LMC]]></title>
                        <link>https://status.cloud.lancom.de/incidents/31/</link>
            <guid isPermaLink="true">https://status.cloud.lancom.de/incidents/31/</guid>
            <description><![CDATA[We are currently working on a solution for this issue and apologise for any inconvenience caused.

2024-10-04 / 12PM: The issue has been fixed.]]></description>
                        <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Lancom Status</dc:creator>
            <pubDate>Fri, 04 Oct 2024 06:00:00 +0000</pubDate>
                                                                                                        </item>
                <item>
            <title><![CDATA[Issues with LMC Monitoring on Public LMC]]></title>
                        <link>https://status.cloud.lancom.de/incidents/30/</link>
            <guid isPermaLink="true">https://status.cloud.lancom.de/incidents/30/</guid>
            <description><![CDATA[We were experiencing issues with the monitoring service. It may happen that monitoring data is missing.

The issue has been fixed.]]></description>
                        <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Lancom Status</dc:creator>
            <pubDate>Tue, 01 Oct 2024 09:45:00 +0000</pubDate>
                                                                                                        </item>
                <item>
            <title><![CDATA[Inconsistencies in the port information of switches in the device overview]]></title>
                        <link>https://status.cloud.lancom.de/incidents/29/</link>
            <guid isPermaLink="true">https://status.cloud.lancom.de/incidents/29/</guid>
            <description><![CDATA[From approximately 30.08.2024 16:30 CEST to 02.09.2024 12:00 CEST, inconsistencies in the port information in the overview could occur (port status and LLDP name).]]></description>
                        <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Lancom Status</dc:creator>
            <pubDate>Fri, 30 Aug 2024 14:30:00 +0000</pubDate>
                                                                                                        </item>
                <item>
            <title><![CDATA[LMC disturbed between 5:05 CEST to 8:05 CEST]]></title>
                        <link>https://status.cloud.lancom.de/incidents/28/</link>
            <guid isPermaLink="true">https://status.cloud.lancom.de/incidents/28/</guid>
            <description><![CDATA[Today the LMC was disturbed from approx. 5:05 CEST to 8:05 CEST. During this time, the LMC could only be used to a limited extent. Some devices were displayed as offline and monitoring was not possible.

All functions were restored. The lost monitoring data remains missing.]]></description>
                        <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Lancom Status</dc:creator>
            <pubDate>Thu, 29 Aug 2024 03:05:00 +0000</pubDate>
                                                                                                        </item>
                <item>
            <title><![CDATA[Possibility of intermittently missing monitoring data points in public LMC]]></title>
                        <link>https://status.cloud.lancom.de/incidents/27/</link>
            <guid isPermaLink="true">https://status.cloud.lancom.de/incidents/27/</guid>
            <description><![CDATA[During the night from yesterday (2024-08-27 / 23:03 CEST) to today (2024-08-28 / 10.11 CEST) we had an issue with traffic routing inside the public LMC.

In this timespan there might be intermittently missing data points for some devices.]]></description>
                        <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Lancom Status</dc:creator>
            <pubDate>Tue, 27 Aug 2024 21:03:00 +0000</pubDate>
                                                                                                        </item>
                <item>
            <title><![CDATA[LMC LTA Login currently malfunctioning]]></title>
                        <link>https://status.cloud.lancom.de/incidents/26/</link>
            <guid isPermaLink="true">https://status.cloud.lancom.de/incidents/26/</guid>
            <description><![CDATA[On Thursday, 22.08.2024 between approx. 01:00 and 13:00 CEST, there was a malfunction of the LTA Login in the LMC.]]></description>
                        <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Lancom Status</dc:creator>
            <pubDate>Wed, 21 Aug 2024 23:00:00 +0000</pubDate>
                                                                                                        </item>
                <item>
            <title><![CDATA[Issue with monitoring service]]></title>
                        <link>https://status.cloud.lancom.de/incidents/25/</link>
            <guid isPermaLink="true">https://status.cloud.lancom.de/incidents/25/</guid>
            <description><![CDATA[Monitoring data from up to 3000 devices could not be collected between 01:00 am and 08:30 am CEST. The issue has been resolved. Network operations were not attected. Unfortunately, the data cannot be restored for the duration of the outage.
We apologize for any inconvenience.]]></description>
                        <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Lancom Status</dc:creator>
            <pubDate>Tue, 13 Aug 2024 23:00:00 +0000</pubDate>
                                                                                                        </item>
                <item>
            <title><![CDATA[Individual devices in LMC offline]]></title>
                        <link>https://status.cloud.lancom.de/incidents/24/</link>
            <guid isPermaLink="true">https://status.cloud.lancom.de/incidents/24/</guid>
            <description><![CDATA[On Monday, 12.08.2024 between approx. 11:20 and 11:40 a.m. CEST there was a network malfunction in the LMC Data Center.

The malfunction has been rectified, but some devices with LCOS SX & LCOS LX operating systems are still offline. We are working on a solution.]]></description>
                        <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Lancom Status</dc:creator>
            <pubDate>Tue, 13 Aug 2024 10:20:00 +0000</pubDate>
                                                                                                        </item>
                <item>
            <title><![CDATA[Disruption in the LMC Data Center on 12.08.2024]]></title>
                        <link>https://status.cloud.lancom.de/incidents/23/</link>
            <guid isPermaLink="true">https://status.cloud.lancom.de/incidents/23/</guid>
            <description><![CDATA[On 12.08.2024 there was a disruption in the LMC Data Center from approximately 11:20 to 11:40 CEST.]]></description>
                        <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Lancom Status</dc:creator>
            <pubDate>Mon, 12 Aug 2024 13:47:56 +0000</pubDate>
                                                                                                        </item>
                <item>
            <title><![CDATA[LMC currently malfunctioning]]></title>
                        <link>https://status.cloud.lancom.de/incidents/21/</link>
            <guid isPermaLink="true">https://status.cloud.lancom.de/incidents/21/</guid>
            <description><![CDATA[We are currently investigating the cause. Network operation is not affected.
We apologize for the inconvenience.]]></description>
                        <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Lancom Status</dc:creator>
            <pubDate>Thu, 01 Aug 2024 07:00:00 +0000</pubDate>
                                                                                                        </item>
                <item>
            <title><![CDATA[Monitoring service disrupted]]></title>
                        <link>https://status.cloud.lancom.de/incidents/20/</link>
            <guid isPermaLink="true">https://status.cloud.lancom.de/incidents/20/</guid>
            <description><![CDATA[We are working to rectify the behavior and apologize for any inconvenience caused.]]></description>
                        <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Lancom Status</dc:creator>
            <pubDate>Mon, 29 Jul 2024 11:20:00 +0000</pubDate>
                                                                                                        </item>
                <item>
            <title><![CDATA[Problem with monitoring service during planned maintenance work on the LMC]]></title>
                        <link>https://status.cloud.lancom.de/incidents/19/</link>
            <guid isPermaLink="true">https://status.cloud.lancom.de/incidents/19/</guid>
            <description><![CDATA[Thursday, 04.07.2024, there was a problem during planned maintenance work on the LMC.

As a result, monitoring did not reactivate automatically as expected in all cases. The reasons for this are under investigation, not all devices are affected. 

Manual work has been initiated to restore monitoring. This should be completed by 04.07.2024 evening. 

We will provide further updates if the situation changes.]]></description>
                        <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Lancom Status</dc:creator>
            <pubDate>Thu, 04 Jul 2024 06:00:00 +0000</pubDate>
                                                                                                        </item>
                <item>
            <title><![CDATA[Störung der Geräteverbindungen | Intermittent device connection errors]]></title>
                        <link>https://status.cloud.lancom.de/incidents/18/</link>
            <guid isPermaLink="true">https://status.cloud.lancom.de/incidents/18/</guid>
            <description><![CDATA[##### Deutsch
Im Zeitraum vom **21.12. 15:00 Uhr** bis **26.12. 13:00 Uhr** kam es wiederholt zu Störungen der Netzwerkverbindung zur LMC. Entsprechende Warnungen wurden im Geräte-Log angezeigt. Grafiken und Diagramme können in diesem Zeitraum Lücken aufweisen.

##### English
The network connection to the LMC was intermittently degraded between **21.12. 15:00** and **26.12. 13:00**. Cloud connection loss warnings have been logged in the Device Log. Graphs and diagrams may show gaps during this period.]]></description>
                        <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Lancom Status</dc:creator>
            <pubDate>Thu, 21 Dec 2023 14:00:00 +0000</pubDate>
                                                                                                        </item>
                <item>
            <title><![CDATA[Transfer of local unit configuration changes malfunctioning]]></title>
                        <link>https://status.cloud.lancom.de/incidents/16/</link>
            <guid isPermaLink="true">https://status.cloud.lancom.de/incidents/16/</guid>
            <description><![CDATA[Currently, there may be problems when taking over local device configuration changes. The elimination of this behaviour is being worked on.]]></description>
                        <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Lancom Status</dc:creator>
            <pubDate>Fri, 03 Feb 2023 10:00:00 +0000</pubDate>
                                                                                                        </item>
                <item>
            <title><![CDATA[Menus not accessible, monitoring data on Dashboard missing]]></title>
                        <link>https://status.cloud.lancom.de/incidents/15/</link>
            <guid isPermaLink="true">https://status.cloud.lancom.de/incidents/15/</guid>
            <description><![CDATA[Due to a malfunction, the menus "Sites", "Devices" and "Addins" cannot be accessed and no monitoring data is displayed in the dashboard.]]></description>
                        <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Lancom Status</dc:creator>
            <pubDate>Fri, 03 Feb 2023 07:00:00 +0000</pubDate>
                                                                                                        </item>
                <item>
            <title><![CDATA[Failure of the Control service in the LANCOM Management Cloud]]></title>
                        <link>https://status.cloud.lancom.de/incidents/14/</link>
            <guid isPermaLink="true">https://status.cloud.lancom.de/incidents/14/</guid>
            <description><![CDATA[Currently the Control service in the LANCOM Management Cloud is disrupted. As a result devices are shown as "offline" and the configuration cannot be rolled out. We apologise for the inconvenience.

LANCOM Systems is working intensively on a solution to restore the functionality as soon as possible. We will update this notice accordingly.]]></description>
                        <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Lancom Status</dc:creator>
            <pubDate>Tue, 20 Dec 2022 10:33:06 +0000</pubDate>
                                                                                                        </item>
                <item>
            <title><![CDATA[DISPLAY OF THE CONFIGURATION STATUS CURRENTLY PARTIALLY INCORRECT]]></title>
                        <link>https://status.cloud.lancom.de/incidents/13/</link>
            <guid isPermaLink="true">https://status.cloud.lancom.de/incidents/13/</guid>
            <description><![CDATA[We are working to rectify the behaviour and apologise for any inconvenience caused.]]></description>
                        <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Lancom Status</dc:creator>
            <pubDate>Wed, 04 May 2022 11:15:00 +0000</pubDate>
                                                                                                        </item>
                <item>
            <title><![CDATA[Monitoring &amp; Dashboard of the LMC currently out of order]]></title>
                        <link>https://status.cloud.lancom.de/incidents/12/</link>
            <guid isPermaLink="true">https://status.cloud.lancom.de/incidents/12/</guid>
            <description><![CDATA[The monitoring service is operational.

Due to a malfunction, monitoring data is missing from about 10 am to 1:30 pm. We apologize for any inconvenience caused.]]></description>
                        <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Lancom Status</dc:creator>
            <pubDate>Thu, 20 Jan 2022 09:10:00 +0000</pubDate>
                                                                                                        </item>
                <item>
            <title><![CDATA[Malfunction with LMC autoupdater for device firmware]]></title>
                        <link>https://status.cloud.lancom.de/incidents/11/</link>
            <guid isPermaLink="true">https://status.cloud.lancom.de/incidents/11/</guid>
            <description><![CDATA[Due to the malfunction, firmware updates may fail in some cases. A solution is currently being worked on.]]></description>
                        <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Lancom Status</dc:creator>
            <pubDate>Wed, 29 Sep 2021 07:30:00 +0000</pubDate>
                                                                                                        </item>
                <item>
            <title><![CDATA[Network disruption in the LMC]]></title>
                        <link>https://status.cloud.lancom.de/incidents/9/</link>
            <guid isPermaLink="true">https://status.cloud.lancom.de/incidents/9/</guid>
            <description><![CDATA[Managed devices are displayed offline due to network failure at the hoster. Monitoring is restricted. We are working on eliminating the problem!]]></description>
                        <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Lancom Status</dc:creator>
            <pubDate>Wed, 12 Feb 2020 08:17:00 +0000</pubDate>
                                                                                                        </item>
                <item>
            <title><![CDATA[Cloud is responding with 503]]></title>
                        <link>https://status.cloud.lancom.de/incidents/6/</link>
            <guid isPermaLink="true">https://status.cloud.lancom.de/incidents/6/</guid>
            <description><![CDATA[Our systems are throwing error code 503 when visiting cloud.lancom.de]]></description>
                        <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Lancom Status</dc:creator>
            <pubDate>Thu, 21 Mar 2019 09:45:00 +0000</pubDate>
                                                                                                        </item>
            </channel>
</rss>
