<?xml version="1.0" encoding="UTF-8" ?>
<feed xmlns="http://www.w3.org/2005/Atom">
    <title type="text">Omnidots Status</title>
    <subtitle type="html"><![CDATA[Status Feed]]></subtitle>
    <link href="http://status.omnidots.com/atom"></link>
    <id>https://status.omnidots.com/</id>
    <link rel="alternate" type="text/html" href="http://status.omnidots.com/atom" ></link>
    <link rel="self" type="application/atom+xml" href="https://status.omnidots.com/" ></link>
        <updated>2026-04-18T08:30:34+00:00</updated>
        <entry>
            <author>
                <name>Omnidots Status</name>
            </author>
            <title type="text"><![CDATA[Signalling issues resolved]]></title>
            <link rel="alternate" type="text/html" href="http://status.omnidots.com/incident/2092/"></link>
            <id>http://status.omnidots.com/incident/2092/</id>
            <summary type="html"><![CDATA[<p>We are glad to share that the degraded 4G/LTE problems have been resolved. Your SWARM units should be coming online again. We are sorry for the inconvenience caused.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2025-09-01T11:32:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Omnidots Status</name>
            </author>
            <title type="text"><![CDATA[Degraded performance on 4G/LTE]]></title>
            <link rel="alternate" type="text/html" href="http://status.omnidots.com/incident/2091/"></link>
            <id>http://status.omnidots.com/incident/2091/</id>
            <summary type="html"><![CDATA[<p>Our SIM provider is experiencing a small outage. The SWARMS affected will continue measuring, and will upload the data once the connection is restored. We expect this issue to be resolved shortly, apologies for the inconvenience!</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2025-09-01T10:06:47+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Omnidots Status</name>
            </author>
            <title type="text"><![CDATA[All systems are operational]]></title>
            <link rel="alternate" type="text/html" href="http://status.omnidots.com/incident/2090/"></link>
            <id>http://status.omnidots.com/incident/2090/</id>
            <summary type="html"><![CDATA[<p>All systems are operational.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2025-07-28T19:46:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Omnidots Status</name>
            </author>
            <title type="text"><![CDATA[IMPORTANT: Honeycomb System Update Notice. (click here for more information)]]></title>
            <link rel="alternate" type="text/html" href="http://status.omnidots.com/incident/1991/"></link>
            <id>http://status.omnidots.com/incident/1991/</id>
            <summary type="html"><![CDATA[<p>Dear valued customers,</p>
<p>Following the unsuccessful deploy of the Honeycomb update from past Saturday, Omnidots now plans to do the update on Saturday the 31st of May. The update will take place at 19:00 (7pm) CEST and is scheduled for a couple of hours.</p>
<p>Typically, we perform updates in a way that minimizes disruption to our customers. However, due to the size of this update, the system will need to go offline temporarily. This is an exceptional situation that won't be standard practice for Omnidots in the future, but in this instance, it's the only way to implement the update properly.</p>
<p>Important Information:</p>
<ul>
<li>The update will temporarily affect access to the Honeycomb system</li>
<li>All sensors will continue to collect data during the update period</li>
<li>Alarms will be temporarily delayed but will be processed once the system is back online</li>
<li>All data collected during the update will be automatically uploaded and available after completion</li>
</ul>
<p>What to Expect:</p>
<p>During this maintenance period, you may experience:</p>
<ul>
<li>Temporary inability to access the Honeycomb interface</li>
<li>Delayed alarm notifications</li>
<li>Brief interruption in real-time data viewing</li>
</ul>
<p>Rest assured that no data will be lost during this process. All measurements will be stored and become available once the update is complete.</p>
<p>We appreciate your patience and understanding as we work to improve our services.</p>
<p>Best regards,</p>
<p>The Omnidots Team</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2025-05-31T17:00:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Omnidots Status</name>
            </author>
            <title type="text"><![CDATA[IMPORTANT: Honeycomb System Update Notice (click here for more information)]]></title>
            <link rel="alternate" type="text/html" href="http://status.omnidots.com/incident/1990/"></link>
            <id>http://status.omnidots.com/incident/1990/</id>
            <summary type="html"><![CDATA[<p>Dear valued customers,</p>
<p>We would like to inform you that we will be performing a system update to enhance the Honeycomb performance and reliability. The update will take place on Saturday 4pm (16:00) CEST. We expect that the update will take a couple of hours.</p>
<p>Typically, we perform updates in a way that minimizes disruption to our customers. However, due to the size of this update, the system will need to go offline temporarily. This is an exceptional situation that won't be standard practice for Omnidots in the future, but in this instance, it's the only way to implement the update properly.</p>
<p>Important Information:</p>
<ul>
<li>The update will temporarily affect access to the Honeycomb system</li>
<li>All sensors will continue to collect data during the update period</li>
<li>Alarms will be temporarily delayed but will be processed once the system is back online</li>
<li>All data collected during the update will be automatically uploaded and available after completion</li>
</ul>
<p>What to Expect:</p>
<p>During this maintenance period, you may experience:</p>
<ul>
<li>Temporary inability to access the Honeycomb interface</li>
<li>Delayed alarm notifications</li>
<li>Brief interruption in real-time data viewing</li>
</ul>
<p>Rest assured that no data will be lost during this process. All measurements will be stored and become available once the update is complete.</p>
<p>We appreciate your patience and understanding as we work to improve our services.</p>
<p>Best regards,</p>
<p>The Omnidots Team</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2025-05-24T14:00:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Omnidots Status</name>
            </author>
            <title type="text"><![CDATA[Team Omnidots]]></title>
            <link rel="alternate" type="text/html" href="http://status.omnidots.com/incident/1988/"></link>
            <id>http://status.omnidots.com/incident/1988/</id>
            <summary type="html"><![CDATA[<p>We have seen all service stabilise and devices should come back online on the next authentication attempt. We are continuing to monitor the network performance during the coming period.</p>
<p>Thank you for your patience.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2025-04-03T11:48:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Omnidots Status</name>
            </author>
            <title type="text"><![CDATA[Team Omnidots]]></title>
            <link rel="alternate" type="text/html" href="http://status.omnidots.com/incident/1987/"></link>
            <id>http://status.omnidots.com/incident/1987/</id>
            <summary type="html"><![CDATA[<p>We have seen slight improvements in device authentication. We are actively working to resolve the ongoing incident. We continue to observe instability on 2G/3G/4G/LTE. We will continue to provide regular updates.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2025-04-03T11:32:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Omnidots Status</name>
            </author>
            <title type="text"><![CDATA[Team Omnidots]]></title>
            <link rel="alternate" type="text/html" href="http://status.omnidots.com/incident/1986/"></link>
            <id>http://status.omnidots.com/incident/1986/</id>
            <summary type="html"><![CDATA[<p>We are actively working to resolve the ongoing incident. At this time, we have observed instability on 2G/3G as well as 4G/LTE. This incident is affecting device authentication, while established connections remain unaffected. We will continue to provide regular updates.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2025-04-03T11:03:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Omnidots Status</name>
            </author>
            <title type="text"><![CDATA[Team Omnidots]]></title>
            <link rel="alternate" type="text/html" href="http://status.omnidots.com/incident/1985/"></link>
            <id>http://status.omnidots.com/incident/1985/</id>
            <summary type="html"><![CDATA[<p>We're pleased to let you know that the issues affecting our network have been resolved, and all services are now fully operational. We appreciate your patience and apologize for any inconvenience caused.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2025-03-26T13:33:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Omnidots Status</name>
            </author>
            <title type="text"><![CDATA[Team Omnidots]]></title>
            <link rel="alternate" type="text/html" href="http://status.omnidots.com/incident/1984/"></link>
            <id>http://status.omnidots.com/incident/1984/</id>
            <summary type="html"><![CDATA[<p>We have seen all service stabilise and devices should come back online on the next authentication attempt. We are continuing to monitor the network performance during the coming period.</p>
<p>Thank you for your patience.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2025-03-26T10:21:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Omnidots Status</name>
            </author>
            <title type="text"><![CDATA[Team Omnidots]]></title>
            <link rel="alternate" type="text/html" href="http://status.omnidots.com/incident/1983/"></link>
            <id>http://status.omnidots.com/incident/1983/</id>
            <summary type="html"><![CDATA[<p>We're aware of the issues affecting our network and are actively working to resolve them. This could result in longer authentication times or dropped connections.</p>
<p>We apologize for any inconvenience and appreciate your patience.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2025-03-26T09:52:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Omnidots Status</name>
            </author>
            <title type="text"><![CDATA[Omnidots Status Update]]></title>
            <link rel="alternate" type="text/html" href="http://status.omnidots.com/incident/1980/"></link>
            <id>http://status.omnidots.com/incident/1980/</id>
            <summary type="html"><![CDATA[<p>We're pleased to let you know that the issues affecting our network have been resolved, and all services are now fully operational. We appreciate your patience and apologize for any inconvenience caused.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2024-12-03T15:51:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Omnidots Status</name>
            </author>
            <title type="text"><![CDATA[Omnidots Status Update]]></title>
            <link rel="alternate" type="text/html" href="http://status.omnidots.com/incident/1979/"></link>
            <id>http://status.omnidots.com/incident/1979/</id>
            <summary type="html"><![CDATA[<p>We are seeing strong improvements of the overall network performance and devices are coming back online. We continue to closely monitor the situation.</p>
<p>We'll provide more updates as we progress. Thank you for your patience.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2024-12-03T13:13:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Omnidots Status</name>
            </author>
            <title type="text"><![CDATA[Omnidots Status Update]]></title>
            <link rel="alternate" type="text/html" href="http://status.omnidots.com/incident/1978/"></link>
            <id>http://status.omnidots.com/incident/1978/</id>
            <summary type="html"><![CDATA[<p>We are continuing to actively monitor and we are seeing improvements with device authentications. We expect more devices to come back online in the coming period.</p>
<p>We will continue to provide regular updates. Thank you for your patience and understanding.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2024-12-03T12:30:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Omnidots Status</name>
            </author>
            <title type="text"><![CDATA[Team Omnidots]]></title>
            <link rel="alternate" type="text/html" href="http://status.omnidots.com/incident/1977/"></link>
            <id>http://status.omnidots.com/incident/1977/</id>
            <summary type="html"><![CDATA[<p>We are experiencing high load of authentication attempts. The high load of signalling activity from these attempts is affecting some device authentication due to attempts being dropped. This could result in longer authentication times or dropped connections. Our team is actively monitoring the situation.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2024-12-03T12:11:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Omnidots Status</name>
            </author>
            <title type="text"><![CDATA[Team Omnidots]]></title>
            <link rel="alternate" type="text/html" href="http://status.omnidots.com/incident/1975/"></link>
            <id>http://status.omnidots.com/incident/1975/</id>
            <summary type="html"><![CDATA[<p>The issues have been resolved, all sims are back online.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2024-10-21T14:45:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Omnidots Status</name>
            </author>
            <title type="text"><![CDATA[Team Omnidots]]></title>
            <link rel="alternate" type="text/html" href="http://status.omnidots.com/incident/1974/"></link>
            <id>http://status.omnidots.com/incident/1974/</id>
            <summary type="html"><![CDATA[<p>We continue to monitor the network and are seeing devices coming back online. We expect more devices to come back online in the coming period. For more updates, keep an eye on the status.omnidots.com page.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2024-10-21T14:19:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Omnidots Status</name>
            </author>
            <title type="text"><![CDATA[Team Omnidots]]></title>
            <link rel="alternate" type="text/html" href="http://status.omnidots.com/incident/1973/"></link>
            <id>http://status.omnidots.com/incident/1973/</id>
            <summary type="html"><![CDATA[<p>We are observing signalling issues with our SIM cards. This is resulting in devices experiencing dropped connections. We will make sure to keep you updated on status.omnidots.com.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2024-10-21T13:00:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Omnidots Status</name>
            </author>
            <title type="text"><![CDATA[Scheduled downtime]]></title>
            <link rel="alternate" type="text/html" href="http://status.omnidots.com/incident/1969/"></link>
            <id>http://status.omnidots.com/incident/1969/</id>
            <summary type="html"><![CDATA[<p>At 09:00 CEST on Saturday morning we will do a quick update. We expect a window of 30 minutes tops of down time. During this period all SWARMS will continue measuring according to schedule.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2024-10-12T07:00:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Omnidots Status</name>
            </author>
            <title type="text"><![CDATA[Team Omnidots]]></title>
            <link rel="alternate" type="text/html" href="http://status.omnidots.com/incident/1968/"></link>
            <id>http://status.omnidots.com/incident/1968/</id>
            <summary type="html"><![CDATA[<p>The incident has been resolved. All SIM ranges are open and functioning again.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2024-10-02T19:24:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Omnidots Status</name>
            </author>
            <title type="text"><![CDATA[Team Omnidots]]></title>
            <link rel="alternate" type="text/html" href="http://status.omnidots.com/incident/1967/"></link>
            <id>http://status.omnidots.com/incident/1967/</id>
            <summary type="html"><![CDATA[<p>We are continuing to monitor the situation. Currently 2G and 3G devices are having trouble authenticating (signalling). We will keep you posted on status.omnidots.com.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2024-10-01T15:48:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Omnidots Status</name>
            </author>
            <title type="text"><![CDATA[Team Omnidots]]></title>
            <link rel="alternate" type="text/html" href="http://status.omnidots.com/incident/1966/"></link>
            <id>http://status.omnidots.com/incident/1966/</id>
            <summary type="html"><![CDATA[<p>We're currently experiencing signalling and device authentication issues due to problems with one of our upstream providers. At the moment, we only see a small regression. We are actively monitoring the situation and will keep you updated via status.omnidots.com.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2024-10-01T14:15:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Omnidots Status</name>
            </author>
            <title type="text"><![CDATA[Team Omnidots]]></title>
            <link rel="alternate" type="text/html" href="http://status.omnidots.com/incident/1955/"></link>
            <id>http://status.omnidots.com/incident/1955/</id>
            <summary type="html"><![CDATA[<p>All issues have been solved. The situation has returned to a normal level.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2024-07-02T15:12:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Omnidots Status</name>
            </author>
            <title type="text"><![CDATA[Team Omnidots]]></title>
            <link rel="alternate" type="text/html" href="http://status.omnidots.com/incident/1954/"></link>
            <id>http://status.omnidots.com/incident/1954/</id>
            <summary type="html"><![CDATA[<p>We have seen systems stabilize and device authentication normalize. We will continue to monitor the situation to ensure ongoing stability.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2024-07-02T14:04:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Omnidots Status</name>
            </author>
            <title type="text"><![CDATA[Team Omnidots]]></title>
            <link rel="alternate" type="text/html" href="http://status.omnidots.com/incident/1953/"></link>
            <id>http://status.omnidots.com/incident/1953/</id>
            <summary type="html"><![CDATA[<p>We are seeing improvements with device authentication as the network continues to stabilize. We will continue to report as efforts progress.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2024-07-02T13:17:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Omnidots Status</name>
            </author>
            <title type="text"><![CDATA[Team Omnidots]]></title>
            <link rel="alternate" type="text/html" href="http://status.omnidots.com/incident/1952/"></link>
            <id>http://status.omnidots.com/incident/1952/</id>
            <summary type="html"><![CDATA[<p>Our provider is continuing to work on this issue. There are no significant updates at this moment, but we will keep you informed as soon as we have more information.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2024-07-02T12:42:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Omnidots Status</name>
            </author>
            <title type="text"><![CDATA[Team Omnidots]]></title>
            <link rel="alternate" type="text/html" href="http://status.omnidots.com/incident/1951/"></link>
            <id>http://status.omnidots.com/incident/1951/</id>
            <summary type="html"><![CDATA[<p>We have identified a SIM authentication issue that is affecting a small subset of devices’ ability to attach to the network. We are working towards stabilizing the situation and will report as efforts progress.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2024-07-02T11:20:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Omnidots Status</name>
            </author>
            <title type="text"><![CDATA[Team Omnidots]]></title>
            <link rel="alternate" type="text/html" href="http://status.omnidots.com/incident/1949/"></link>
            <id>http://status.omnidots.com/incident/1949/</id>
            <summary type="html"><![CDATA[<p>We're pleased to let you know that the issues affecting signaling and device authentication have been resolved. We are continuing to monitor for any further issues.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2024-06-06T17:34:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Omnidots Status</name>
            </author>
            <title type="text"><![CDATA[Team Omnidots]]></title>
            <link rel="alternate" type="text/html" href="http://status.omnidots.com/incident/1948/"></link>
            <id>http://status.omnidots.com/incident/1948/</id>
            <summary type="html"><![CDATA[<p>We are seeing improvements and recovery of devices. We expect more devices to recover in the coming period.</p>
<p>For frequent updates, keep an eye on status.omnidots.com.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2024-06-06T15:22:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Omnidots Status</name>
            </author>
            <title type="text"><![CDATA[Team Omnidots]]></title>
            <link rel="alternate" type="text/html" href="http://status.omnidots.com/incident/1946/"></link>
            <id>http://status.omnidots.com/incident/1946/</id>
            <summary type="html"><![CDATA[<p>The provider has implemented a fix and the network stability is improving. We expect to see devices coming back online in the coming period.
We will continue to provide regular hourly updates on status.omnidots.com.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2024-06-06T13:44:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Omnidots Status</name>
            </author>
            <title type="text"><![CDATA[Team Omnidots]]></title>
            <link rel="alternate" type="text/html" href="http://status.omnidots.com/incident/1945/"></link>
            <id>http://status.omnidots.com/incident/1945/</id>
            <summary type="html"><![CDATA[<p>The provider is still working on implementing a fix. There are no further updates at this time. Follow status.omnidots.com for frequent updates.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2024-06-06T13:15:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Omnidots Status</name>
            </author>
            <title type="text"><![CDATA[Team Omnidots]]></title>
            <link rel="alternate" type="text/html" href="http://status.omnidots.com/incident/1944/"></link>
            <id>http://status.omnidots.com/incident/1944/</id>
            <summary type="html"><![CDATA[<p>The provider has identified the issue causing instability and are implementing a fix to imitate further issues.
We'll provide more updates when we receive those. For updates, follow status.omnidots.com.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2024-06-06T12:26:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Omnidots Status</name>
            </author>
            <title type="text"><![CDATA[Team Omnidots]]></title>
            <link rel="alternate" type="text/html" href="http://status.omnidots.com/incident/1943/"></link>
            <id>http://status.omnidots.com/incident/1943/</id>
            <summary type="html"><![CDATA[<p>We have been noticing an increased amount of signaling causing issues with the signaling part of the authentication. This may result in increased or dropped device authentication during this time. For frequent updates, go to status.omnidots.com.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2024-06-06T12:00:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Omnidots Status</name>
            </author>
            <title type="text"><![CDATA[Tom Oegema]]></title>
            <link rel="alternate" type="text/html" href="http://status.omnidots.com/incident/1942/"></link>
            <id>http://status.omnidots.com/incident/1942/</id>
            <summary type="html"><![CDATA[<p>A major global outage of the SIM provider, resulting in a data connection failure of the SWARM.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2024-05-29T03:48:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Omnidots Status</name>
            </author>
            <title type="text"><![CDATA[Honeycomb sometimes gives 502]]></title>
            <link rel="alternate" type="text/html" href="http://status.omnidots.com/incident/986/"></link>
            <id>http://status.omnidots.com/incident/986/</id>
            <summary type="html"><![CDATA[<p>Our Honeycomb is unfortunately giving an HTTP error 502 from time to time. We're investigating what's the root cause of this. Please try the page again if you encounter a 502. We sincerely apologize for any inconvenience this may have caused.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2021-06-11T08:43:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Omnidots Status</name>
            </author>
            <title type="text"><![CDATA[Honeycomb unreachable]]></title>
            <link rel="alternate" type="text/html" href="http://status.omnidots.com/incident/981/"></link>
            <id>http://status.omnidots.com/incident/981/</id>
            <summary type="html"><![CDATA[<p>Due to networking issues at one of our operators we are unfortunately experiencing connection issues. Your SWARMS will continue measuring. As soon as the networking issues have been resolved Honeycomb will come back online and all SWARMS will upload their backlog. We sincerely apologize for any inconvenience this may have caused.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2021-06-10T20:25:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Omnidots Status</name>
            </author>
            <title type="text"><![CDATA[Scheduled downtime]]></title>
            <link rel="alternate" type="text/html" href="http://status.omnidots.com/incident/951/"></link>
            <id>http://status.omnidots.com/incident/951/</id>
            <summary type="html"><![CDATA[<p>Between Saturday June 6th at 7pm CEST and Sunday June 7th 11am CEST we will do a quick update. We expect a window of 15 minutes tops of down time. During this period all Swarms will continue measuring according to schedule.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2020-06-05T07:02:05+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Omnidots Status</name>
            </author>
            <title type="text"><![CDATA[Scheduled downtime]]></title>
            <link rel="alternate" type="text/html" href="http://status.omnidots.com/incident/943/"></link>
            <id>http://status.omnidots.com/incident/943/</id>
            <summary type="html"><![CDATA[<p>At 9 am CET on december 24 2019. We will do a quick update. We expect a window of 15 minutes tops of down time. During this period all Swarms will continue measuring according to schedule.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2019-12-23T16:17:19+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Omnidots Status</name>
            </author>
            <title type="text"><![CDATA[All systems up and running]]></title>
            <link rel="alternate" type="text/html" href="http://status.omnidots.com/incident/942/"></link>
            <id>http://status.omnidots.com/incident/942/</id>
            <summary type="html"><![CDATA[<p>This morning Honeycomb was offline. We have worked hard and seriously on a solution and are happy that everything is working again. We are sorry that we had to keep you waiting. If you have any questions, click on the chat at the bottom right of the screen.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2019-12-06T11:41:11+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Omnidots Status</name>
            </author>
            <title type="text"><![CDATA[Scheduled downtime]]></title>
            <link rel="alternate" type="text/html" href="http://status.omnidots.com/incident/922/"></link>
            <id>http://status.omnidots.com/incident/922/</id>
            <summary type="html"><![CDATA[<p>At 21pm CET on November 9th we will do a quick update. We expect a window of 15 minutes tops of down time. During this period all Swarms will continue measuring according to schedule.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2019-11-08T15:51:02+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Omnidots Status</name>
            </author>
            <title type="text"><![CDATA[Scheduled downtime]]></title>
            <link rel="alternate" type="text/html" href="http://status.omnidots.com/incident/920/"></link>
            <id>http://status.omnidots.com/incident/920/</id>
            <summary type="html"><![CDATA[<p>At 2019-11-06 8:00 UTC+1. We will do a quick update. We expect a window of 15 minutes tops of down time. During this period all Swarms will continue measuring according to schedule.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2019-11-05T07:32:27+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Omnidots Status</name>
            </author>
            <title type="text"><![CDATA[Scheduled downtime]]></title>
            <link rel="alternate" type="text/html" href="http://status.omnidots.com/incident/918/"></link>
            <id>http://status.omnidots.com/incident/918/</id>
            <summary type="html"><![CDATA[<p>On Saturday evening November 2nd (CET) we will do a major update to support the growing number of Swarms. We expect a window of 2 hours tops of down time. During this period all Swarms will continue measuring according to schedule.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2019-11-01T21:31:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Omnidots Status</name>
            </author>
            <title type="text"><![CDATA[Scheduled downtime]]></title>
            <link rel="alternate" type="text/html" href="http://status.omnidots.com/incident/916/"></link>
            <id>http://status.omnidots.com/incident/916/</id>
            <summary type="html"><![CDATA[<p>At 8pm on October 25th 2019 CEST. We will do a quick update. We expect a window of 15 minutes tops of down time. During this period all Swarms will continue measuring according to schedule.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2019-10-24T15:08:05+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Omnidots Status</name>
            </author>
            <title type="text"><![CDATA[Scheduled downtime]]></title>
            <link rel="alternate" type="text/html" href="http://status.omnidots.com/incident/911/"></link>
            <id>http://status.omnidots.com/incident/911/</id>
            <summary type="html"><![CDATA[<p>At 8pm on October 8th 2019 CEST we will do a quick update. We expect a window of 10 minutes tops of down time. During this period all Swarms will continue measuring according to schedule.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2019-10-08T10:07:49+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Omnidots Status</name>
            </author>
            <title type="text"><![CDATA[Server outage in our Amazon datacenter.]]></title>
            <link rel="alternate" type="text/html" href="http://status.omnidots.com/incident/908/"></link>
            <id>http://status.omnidots.com/incident/908/</id>
            <summary type="html"><![CDATA[<p>Due to a server outage in our Amazon datacenter we were experiencing downtime this morning. All Swarms were measuring according to schedule, however they might have given false offline notifications.
The issue was resolved at the end of the morning CEST.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2019-10-08T06:30:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Omnidots Status</name>
            </author>
            <title type="text"><![CDATA[Scheduled downtime]]></title>
            <link rel="alternate" type="text/html" href="http://status.omnidots.com/incident/904/"></link>
            <id>http://status.omnidots.com/incident/904/</id>
            <summary type="html"><![CDATA[<p>At 8 PM CEST on 23 sept 2019. We will do a quick update. We expect a window of 15 minutes tops of down time. During this period all Swarms will continue measuring according to schedule.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2019-09-20T06:34:57+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Omnidots Status</name>
            </author>
            <title type="text"><![CDATA[Scheduled downtime]]></title>
            <link rel="alternate" type="text/html" href="http://status.omnidots.com/incident/897/"></link>
            <id>http://status.omnidots.com/incident/897/</id>
            <summary type="html"><![CDATA[<p>At 8 PM CEST on September 7th we will do some quick maintenance, we expect a window of 10 minutes tops of down time. During this period all Swarms will continue measuring according to schedule.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2019-09-06T15:39:27+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Omnidots Status</name>
            </author>
            <title type="text"><![CDATA[Incorrect reports of Swarms going offline]]></title>
            <link rel="alternate" type="text/html" href="http://status.omnidots.com/incident/895/"></link>
            <id>http://status.omnidots.com/incident/895/</id>
            <summary type="html"><![CDATA[<p>Due to an unexpected outage at our cloud provider yesterday night some Swarms might have incorrectly been reported as offline between September 5th 10:30 PM CEST and September 6th 5:30 AM CEST.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2019-09-06T06:00:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Omnidots Status</name>
            </author>
            <title type="text"><![CDATA[Unexpected downtime]]></title>
            <link rel="alternate" type="text/html" href="http://status.omnidots.com/incident/889/"></link>
            <id>http://status.omnidots.com/incident/889/</id>
            <summary type="html"><![CDATA[<p>Due to an unexpected outage at our cloud provider, access to our Honeycomb is limited since 22:30 CEST on September 5th. All Swarms are measure according to schedule. However some Swarms might have -incorrectly- been marked as offline.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2019-09-05T20:30:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Omnidots Status</name>
            </author>
            <title type="text"><![CDATA[Scheduled downtime]]></title>
            <link rel="alternate" type="text/html" href="http://status.omnidots.com/incident/882/"></link>
            <id>http://status.omnidots.com/incident/882/</id>
            <summary type="html"><![CDATA[<p>At 7 am CEST on August 29th we will do a quick update. We expect a window of 10 minutes tops of down time. During this period all Swarms will continue measuring according to schedule.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2019-08-28T08:46:03+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Omnidots Status</name>
            </author>
            <title type="text"><![CDATA[Scheduled downtime]]></title>
            <link rel="alternate" type="text/html" href="http://status.omnidots.com/incident/881/"></link>
            <id>http://status.omnidots.com/incident/881/</id>
            <summary type="html"><![CDATA[<p>At 7 am CEST on August 27th we will do a quick update. We expect a window of 10 minutes tops of down time. During this period all Swarms will continue measuring according to schedule.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2019-08-26T06:33:21+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Omnidots Status</name>
            </author>
            <title type="text"><![CDATA[Scheduled downtime]]></title>
            <link rel="alternate" type="text/html" href="http://status.omnidots.com/incident/880/"></link>
            <id>http://status.omnidots.com/incident/880/</id>
            <summary type="html"><![CDATA[<p>At 8 am CEST on Tuesday August 20th we will do a quick update. We expect a window of 3 minutes tops of down time. During this period all Swarms will continue measuring according to schedule.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2019-08-18T07:37:14+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Omnidots Status</name>
            </author>
            <title type="text"><![CDATA[Scheduled downtime]]></title>
            <link rel="alternate" type="text/html" href="http://status.omnidots.com/incident/879/"></link>
            <id>http://status.omnidots.com/incident/879/</id>
            <summary type="html"><![CDATA[<p>At 9:00 am CEST on August 17th we will do a quick update. We expect a window of 5 minutes tops of down time. During this period all Swarms will continue measuring according to schedule.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2019-08-16T07:00:01+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Omnidots Status</name>
            </author>
            <title type="text"><![CDATA[Scheduled downtime]]></title>
            <link rel="alternate" type="text/html" href="http://status.omnidots.com/incident/878/"></link>
            <id>http://status.omnidots.com/incident/878/</id>
            <summary type="html"><![CDATA[<p>At 8 am CEST on Thursday August 15th we will do a quick update. We expect a window of 5 minutes tops of down time. During this period all Swarms will continue measuring according to schedule.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2019-08-13T18:04:56+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Omnidots Status</name>
            </author>
            <title type="text"><![CDATA[Incorrect reports of Swarms going offline]]></title>
            <link rel="alternate" type="text/html" href="http://status.omnidots.com/incident/876/"></link>
            <id>http://status.omnidots.com/incident/876/</id>
            <summary type="html"><![CDATA[<p>Due to Honeycomb server maintenance our notifier might have incorrectly reported Swarms going offline on July 20th 2019 between 7 PM and 11 PM.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2019-07-22T06:40:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Omnidots Status</name>
            </author>
            <title type="text"><![CDATA[Scheduled downtime]]></title>
            <link rel="alternate" type="text/html" href="http://status.omnidots.com/incident/873/"></link>
            <id>http://status.omnidots.com/incident/873/</id>
            <summary type="html"><![CDATA[<p>At 7:00 PM on July 20th 2019 the Honeycomb will undergo maintenance. We expect a window of 3 hours of down time. During this period all Swarms will continue measuring according to schedule, notifications will be postponed until after the maintenance has finished.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2019-07-19T06:36:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Omnidots Status</name>
            </author>
            <title type="text"><![CDATA[Scheduled downtime]]></title>
            <link rel="alternate" type="text/html" href="http://status.omnidots.com/incident/872/"></link>
            <id>http://status.omnidots.com/incident/872/</id>
            <summary type="html"><![CDATA[<p>At 8 am CEST on July 16th 2019. We will do a quick update. We expect a window of 15 minutes tops of down time. During this period all Swarms will continue measuring according to schedule.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2019-07-15T07:08:49+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Omnidots Status</name>
            </author>
            <title type="text"><![CDATA[Scheduled downtime]]></title>
            <link rel="alternate" type="text/html" href="http://status.omnidots.com/incident/871/"></link>
            <id>http://status.omnidots.com/incident/871/</id>
            <summary type="html"><![CDATA[<p>At 10-07-2019 at 8:00 am (Europe/Amsterdam timezone). We will do a quick update. We expect a window of 10 minutes tops of down time. During this period all Swarms will continue measuring according to schedule.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2019-07-08T15:21:12+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Omnidots Status</name>
            </author>
            <title type="text"><![CDATA[Scheduled downtime]]></title>
            <link rel="alternate" type="text/html" href="http://status.omnidots.com/incident/869/"></link>
            <id>http://status.omnidots.com/incident/869/</id>
            <summary type="html"><![CDATA[<p>At 8:20 am CEST on Friday July 5th we will do a quick update. We expect a window of 10 minutes tops of down time. During this period all Swarms will continue measuring according to schedule.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2019-07-03T14:25:43+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Omnidots Status</name>
            </author>
            <title type="text"><![CDATA[Scheduled downtime]]></title>
            <link rel="alternate" type="text/html" href="http://status.omnidots.com/incident/868/"></link>
            <id>http://status.omnidots.com/incident/868/</id>
            <summary type="html"><![CDATA[<p>At 8 am CEST on Tuesday July 2nd we will do a quick update. We expect a window of 5 minutes tops of down time. During this period all Swarms will continue measuring according to schedule.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2019-07-01T08:15:42+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Omnidots Status</name>
            </author>
            <title type="text"><![CDATA[Scheduled downtime]]></title>
            <link rel="alternate" type="text/html" href="http://status.omnidots.com/incident/867/"></link>
            <id>http://status.omnidots.com/incident/867/</id>
            <summary type="html"><![CDATA[<p>At 8 am CEST on Monday July 1st. We will do a quick update. We expect a window of 15 minutes tops of down time. During this period all Swarms will continue measuring according to schedule.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2019-06-28T09:19:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Omnidots Status</name>
            </author>
            <title type="text"><![CDATA[Scheduled downtime]]></title>
            <link rel="alternate" type="text/html" href="http://status.omnidots.com/incident/866/"></link>
            <id>http://status.omnidots.com/incident/866/</id>
            <summary type="html"><![CDATA[<p>At Thuesday 8:00 AM Europe/Amsterdam timezone. We will do a quick update. We expect a window of 15 minutes tops of down time. During this period all Swarms will continue measuring according to schedule.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2019-06-24T07:39:16+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Omnidots Status</name>
            </author>
            <title type="text"><![CDATA[Swarm Data Connection Outage]]></title>
            <link rel="alternate" type="text/html" href="http://status.omnidots.com/incident/865/"></link>
            <id>http://status.omnidots.com/incident/865/</id>
            <summary type="html"><![CDATA[<p>Data provider Vodafone for region Netherlands is having issues on their network. Swarms are unable to connect to our servers.</p>
<p>We expect the data connection to be restored between 10:00 and 11:00 UTC+2.</p>
<p>The issues is resolved at 10:40 UTC+2.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2019-06-05T07:03:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Omnidots Status</name>
            </author>
            <title type="text"><![CDATA[Scheduled downtime]]></title>
            <link rel="alternate" type="text/html" href="http://status.omnidots.com/incident/855/"></link>
            <id>http://status.omnidots.com/incident/855/</id>
            <summary type="html"><![CDATA[<p>At 28 May 8:00 GMT+2 we will do a quick update. We expect a window of 30 minutes tops of down time. During this period all Swarms will continue measuring according to schedule.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2019-05-27T06:48:46+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Omnidots Status</name>
            </author>
            <title type="text"><![CDATA[Scheduled downtime]]></title>
            <link rel="alternate" type="text/html" href="http://status.omnidots.com/incident/853/"></link>
            <id>http://status.omnidots.com/incident/853/</id>
            <summary type="html"><![CDATA[<p>At 2019-05-16 08:00 UTC+2. We will do a quick update. We expect a window of 15 minutes down time. During this period all Swarms will continue measuring according to schedule.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2019-05-15T09:13:06+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Omnidots Status</name>
            </author>
            <title type="text"><![CDATA[Scheduled downtime]]></title>
            <link rel="alternate" type="text/html" href="http://status.omnidots.com/incident/852/"></link>
            <id>http://status.omnidots.com/incident/852/</id>
            <summary type="html"><![CDATA[<p>At 14/05/2019 08:00 (GMT+2) . We will do a quick update. We expect a window of 30 minutes tops of down time. During this period all Swarms will continue measuring according to schedule.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2019-05-13T09:04:34+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Omnidots Status</name>
            </author>
            <title type="text"><![CDATA[Short scheduled downtime]]></title>
            <link rel="alternate" type="text/html" href="http://status.omnidots.com/incident/851/"></link>
            <id>http://status.omnidots.com/incident/851/</id>
            <summary type="html"><![CDATA[<p>At 03/05/2019 (DD/MM/YYYY) at 16:00 (GMT+2). We will do a quick update. We expect a window of 15 minutes tops of down time. During this period all Swarms will continue measuring according to schedule.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2019-05-03T08:04:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Omnidots Status</name>
            </author>
            <title type="text"><![CDATA[Short scheduled downtime]]></title>
            <link rel="alternate" type="text/html" href="http://status.omnidots.com/incident/850/"></link>
            <id>http://status.omnidots.com/incident/850/</id>
            <summary type="html"><![CDATA[<p>At 02/05/2019 at 16:00 (GMT+2). We will do a quick update. We expect a window of 15 minutes tops of down time. During this period all Swarms will continue measuring according to schedule.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2019-05-02T08:17:06+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Omnidots Status</name>
            </author>
            <title type="text"><![CDATA[Short scheduled downtime.]]></title>
            <link rel="alternate" type="text/html" href="http://status.omnidots.com/incident/845/"></link>
            <id>http://status.omnidots.com/incident/845/</id>
            <summary type="html"><![CDATA[<p>At 30/04/2019 at 16:00 (GMT+2). We will do a quick update. We expect a window of 15 minutes tops of down time.
During this period all Swarms will continue measuring according to schedule.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2019-04-30T08:07:18+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Omnidots Status</name>
            </author>
            <title type="text"><![CDATA[Planned maintenance]]></title>
            <link rel="alternate" type="text/html" href="http://status.omnidots.com/incident/841/"></link>
            <id>http://status.omnidots.com/incident/841/</id>
            <summary type="html"><![CDATA[<p>Tomorrow at 7:30 (GMT+2) the Honeycomb will be down for a short period to deploy a new version.
We expect up to half an hour of downtime.</p>
<p>During this window all Swarms will continue measuring as expected.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2019-04-29T05:45:01+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Omnidots Status</name>
            </author>
            <title type="text"><![CDATA[Missing weekly and daily reports]]></title>
            <link rel="alternate" type="text/html" href="http://status.omnidots.com/incident/834/"></link>
            <id>http://status.omnidots.com/incident/834/</id>
            <summary type="html"><![CDATA[<p>We're receiving multiple reports from our customers regarding missing reports.</p>
<p>Our team has identified the root cause and is working on making and testing a possible solution.
We're expecting to fix the issue today, on the following report round all missing reports will be generated.</p>
<p>In the mean time, needed reports can still be generated by hand if they are urgently needed.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2019-04-23T06:00:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Omnidots Status</name>
            </author>
            <title type="text"><![CDATA[Maintenance on our main server]]></title>
            <link rel="alternate" type="text/html" href="http://status.omnidots.com/incident/758/"></link>
            <id>http://status.omnidots.com/incident/758/</id>
            <summary type="html"><![CDATA[<p>On 5 February at 19:00 CET the Honeycomb platform will be offline for a scheduled maintenance.
The expected duration is 1 hour. During the maintenance Swarms will continue measuring, but can't connect to the platform.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2019-02-05T06:57:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Omnidots Status</name>
            </author>
            <title type="text"><![CDATA[Falsely marked offline sensor notifications]]></title>
            <link rel="alternate" type="text/html" href="http://status.omnidots.com/incident/734/"></link>
            <id>http://status.omnidots.com/incident/734/</id>
            <summary type="html"><![CDATA[<p>This weekend our server falsely determined sensors offline during scheduled offline time. We are working on a fix.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2018-12-08T06:00:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Omnidots Status</name>
            </author>
            <title type="text"><![CDATA[Invalid online/offline notifications]]></title>
            <link rel="alternate" type="text/html" href="http://status.omnidots.com/incident/262/"></link>
            <id>http://status.omnidots.com/incident/262/</id>
            <summary type="html"><![CDATA[<p>Today we have identified an issue with the Swarm online/offline notification system.  Whenever a Swarm is sleeping according to its schedule it will incorrectly show offline in the Honeycomb and generate an invalid notification accordingly. The issue is expected to be resolved October 25th 2018 before 5pm CEST.</p>
<p>All Swarms are expected to wakeup according to their schedule and an online notification will be generated.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2018-10-24T19:01:33+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Omnidots Status</name>
            </author>
            <title type="text"><![CDATA[Some Swarms uploading data again]]></title>
            <link rel="alternate" type="text/html" href="http://status.omnidots.com/incident/106/"></link>
            <id>http://status.omnidots.com/incident/106/</id>
            <summary type="html"><![CDATA[<p>We've identified and possibly fixed an issue where Swarms were told to upload data again by the server.
We are monitoring the issue right now. We've set the timestamp of this message to a later point so the message is seen the day after as well.</p>
<p>This problem may have caused notifications to be resend with an old timestamp.
This problem affected 26 Swarms in total.</p>
<p>We apologize for the inconvenience and are looking into what caused this issue.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2018-09-18T16:00:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Omnidots Status</name>
            </author>
            <title type="text"><![CDATA[Planned maintenance]]></title>
            <link rel="alternate" type="text/html" href="http://status.omnidots.com/incident/56/"></link>
            <id>http://status.omnidots.com/incident/56/</id>
            <summary type="html"><![CDATA[<p>On Sunday 16 September at 19:00 the Honeycomb will be offline for planned maintenance.</p>
<p>We will perform an upgrade to the server infrastructure to support the continuous growth of Swarm data. We expect 1 hour of downtime followed by another hour of degraded performance. During the second hour the data will me divided over multiple servers which causes a high impact on our server.</p>
<p>During the downtime the Swarms will store their data internally and will upload this after the maintenance period.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2018-09-14T11:52:41+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Omnidots Status</name>
            </author>
            <title type="text"><![CDATA[Daily reports failed]]></title>
            <link rel="alternate" type="text/html" href="http://status.omnidots.com/incident/52/"></link>
            <id>http://status.omnidots.com/incident/52/</id>
            <summary type="html"><![CDATA[<p>The honeycomb was unable to send the daily reports.</p>
<p>We've fixed this issue and for the next daily report round the reports will be send.
Regarding the not send report, this report will have to be made by hand.</p>
<p>We apologize for the inconvenience.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2018-09-05T01:00:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Omnidots Status</name>
            </author>
            <title type="text"><![CDATA[Instance upgrade for all Omnidots services]]></title>
            <link rel="alternate" type="text/html" href="http://status.omnidots.com/incident/26/"></link>
            <id>http://status.omnidots.com/incident/26/</id>
            <summary type="html"><![CDATA[<p>Tomorrow morning Omnidots will be performing a planned maintenance. The outage might take up to half an hour.</p>
<p>During the maintenance <strong>all</strong> services of Omnidots will be unavailable.</p>
<hr />
<p>During the maintenance the server is upgraded to a new instance.
All Swarms in the field will continue their operations as setup and measurements will be avaiable at a later moment.</p>
<hr />
<p>The upgrade took longer than expected due to network settings which had to be updated.
All systems have properly started at 9:30 and are working now.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2018-08-30T09:46:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Omnidots Status</name>
            </author>
            <title type="text"><![CDATA[URL unavailable]]></title>
            <link rel="alternate" type="text/html" href="http://status.omnidots.com/incident/18/"></link>
            <id>http://status.omnidots.com/incident/18/</id>
            <summary type="html"><![CDATA[<p>The URL is unreachable: GET http://website:8000/api/v1/list_sensors?token=163cef4b11184dc8a31e7516ef02a14e</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2018-08-17T11:16:18+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Omnidots Status</name>
            </author>
            <title type="text"><![CDATA[URL unavailable]]></title>
            <link rel="alternate" type="text/html" href="http://status.omnidots.com/incident/11/"></link>
            <id>http://status.omnidots.com/incident/11/</id>
            <summary type="html"><![CDATA[<p>Unexpected HTTP status (500)</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2018-08-10T11:32:47+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Omnidots Status</name>
            </author>
            <title type="text"><![CDATA[URL unavailable]]></title>
            <link rel="alternate" type="text/html" href="http://status.omnidots.com/incident/10/"></link>
            <id>http://status.omnidots.com/incident/10/</id>
            <summary type="html"><![CDATA[<p>The URL is unreachable: GET http://website:8000/accounts/login/?next=/measuring_point/</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2018-08-10T11:31:48+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Omnidots Status</name>
            </author>
            <title type="text"><![CDATA[URL unavailable]]></title>
            <link rel="alternate" type="text/html" href="http://status.omnidots.com/incident/9/"></link>
            <id>http://status.omnidots.com/incident/9/</id>
            <summary type="html"><![CDATA[<p>Unexpected HTTP status (500)</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2018-08-10T11:31:38+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Omnidots Status</name>
            </author>
            <title type="text"><![CDATA[URL unavailable]]></title>
            <link rel="alternate" type="text/html" href="http://status.omnidots.com/incident/5/"></link>
            <id>http://status.omnidots.com/incident/5/</id>
            <summary type="html"><![CDATA[<p>Unexpected HTTP status (400)</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2018-08-08T07:20:28+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Omnidots Status</name>
            </author>
            <title type="text"><![CDATA[URL unavailable]]></title>
            <link rel="alternate" type="text/html" href="http://status.omnidots.com/incident/6/"></link>
            <id>http://status.omnidots.com/incident/6/</id>
            <summary type="html"><![CDATA[<p>Unexpected HTTP status (400)</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2018-08-08T07:20:28+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Omnidots Status</name>
            </author>
            <title type="text"><![CDATA[URL unavailable]]></title>
            <link rel="alternate" type="text/html" href="http://status.omnidots.com/incident/4/"></link>
            <id>http://status.omnidots.com/incident/4/</id>
            <summary type="html"><![CDATA[<p>The URL is unreachable: GET http://website:8000/accounts/login/?next=/measuring_point/</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2018-08-08T06:18:30+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Omnidots Status</name>
            </author>
            <title type="text"><![CDATA[URL unavailable]]></title>
            <link rel="alternate" type="text/html" href="http://status.omnidots.com/incident/3/"></link>
            <id>http://status.omnidots.com/incident/3/</id>
            <summary type="html"><![CDATA[<p>The URL is unreachable: GET http://notifier:8002/api/sub/sensor/6/</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2018-08-08T06:18:19+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Omnidots Status</name>
            </author>
            <title type="text"><![CDATA[URL unavailable]]></title>
            <link rel="alternate" type="text/html" href="http://status.omnidots.com/incident/2/"></link>
            <id>http://status.omnidots.com/incident/2/</id>
            <summary type="html"><![CDATA[<p>The URL is unreachable: GET http://website:8000/api/v1/list_sensors?token=163cef4b11184dc8a31e7516ef02a14e</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2018-08-08T06:18:12+00:00</updated>
        </entry>
</feed>
