<?xml version="1.0" encoding="UTF-8" ?>
<feed xmlns="http://www.w3.org/2005/Atom">
    <title type="text">Nedap Retail Statuspage</title>
    <subtitle type="html"><![CDATA[Status Feed]]></subtitle>
    <link href="https://status.nedap-retail.com/atom"></link>
    <id>http://status.nedap-retail.com/</id>
    <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/atom" ></link>
    <link rel="self" type="application/atom+xml" href="http://status.nedap-retail.com/" ></link>
        <updated>2026-05-14T09:41:57+00:00</updated>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Connection issues for iD Cloud Team Count (EU Instance)]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/394/"></link>
            <id>https://status.nedap-retail.com/incident/394/</id>
            <summary type="html"><![CDATA[<p>Our technical team has fixed the issue affecting Team Count on the EU instance. We have monitored the situation for the past 15 minutes, and all Team Count behavior is back to normal. This incident is now marked as resolved. We apologize for the inconvenience caused.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2026-03-31T08:45:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Connection issues for iD Cloud Team Count (EU Instance)]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/393/"></link>
            <id>https://status.nedap-retail.com/incident/393/</id>
            <summary type="html"><![CDATA[<p>Our team has investigated the issue affecting Team Count on the EU instance. We are seeing positive improvement in processing and connection errors are lowering. Users are able to connect to Team Count again. We will continue to monitor the situation closely and share another update as soon as we have more information.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2026-03-31T08:30:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Connection issues for iD Cloud Team Count (EU Instance)]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/392/"></link>
            <id>https://status.nedap-retail.com/incident/392/</id>
            <summary type="html"><![CDATA[<p>We see some connection issues with our Team Count services for iD Cloud on the EU instance. Our team is currently investigating and we will update the statuspage shortly.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2026-03-31T08:00:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Degraded Performance – Delays and Slow Processing]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/391/"></link>
            <id>https://status.nedap-retail.com/incident/391/</id>
            <summary type="html"><![CDATA[<p>We have continued to monitor the situation and can confirm that performance has fully returned to normal. All systems are operating as expected.</p>
<p>We apologize for any inconvenience caused.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2026-03-18T09:55:51+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Degraded Performance – Delays and Slow Processing]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/390/"></link>
            <id>https://status.nedap-retail.com/incident/390/</id>
            <summary type="html"><![CDATA[<p>Performance has returned to normal and all systems are operating as expected, although users may have experienced minor delays earlier.</p>
<p>We will continue to monitor the situation and will provide further updates as needed.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2026-03-18T09:29:09+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Degraded Performance – Delays and Slow Processing]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/389/"></link>
            <id>https://status.nedap-retail.com/incident/389/</id>
            <summary type="html"><![CDATA[<p>We are currently experiencing degraded performance across our services. Users may notice delays and slower processing times than usual.
Our team is actively investigating the issue and working to restore normal performance as quickly as possible. We will provide updates as more information becomes available.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2026-03-18T09:00:57+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Support Portal is available again]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/388/"></link>
            <id>https://status.nedap-retail.com/incident/388/</id>
            <summary type="html"><![CDATA[<p>The issues at Cloudflare have resolved and our Support Portal is reachable again.
Thank you for your patience.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2025-12-05T09:21:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Support Portal not available due to Cloudflare outage]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/387/"></link>
            <id>https://status.nedap-retail.com/incident/387/</id>
            <summary type="html"><![CDATA[<p>Our Support Portal is currently unavailable due to issues at Cloudflare. We are keeping a close eye on this and will post an update as soon as this is available again.
In case you need support, please contact us via email. Thank you for your understanding.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2025-12-05T08:30:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Issues with iD Cloud - data processing delays - EU Instance]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/386/"></link>
            <id>https://status.nedap-retail.com/incident/386/</id>
            <summary type="html"><![CDATA[<p>We have monitored the situation and all is working as expected. All services are fully operational again and all data has been processed. Apologies for the inconvenience.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2025-12-01T16:27:38+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Issues with iD Cloud - data processing delays - EU Instance]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/385/"></link>
            <id>https://status.nedap-retail.com/incident/385/</id>
            <summary type="html"><![CDATA[<p>We experienced data processing delays at an external supplier, but we are now seeing data coming in and the systems are processing information again. Some features in iD Cloud may have shown errors during this period, but functionality should gradually return to normal. We will continue to monitor the situation and provide an update if anything changes.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2025-12-01T16:14:48+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Issues with iD Cloud - data processing delays - EU Instance]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/384/"></link>
            <id>https://status.nedap-retail.com/incident/384/</id>
            <summary type="html"><![CDATA[<p>We are seeing data processing delays on one of our servers.</p>
<p>It is possible that some features in iD Cloud are currently not able to retrieve data and show an error.
Our team is investigating this and we will post an update as soon as we know more.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2025-12-01T15:57:39+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Issues with iD Cloud APIs, Web &amp; Device Management - EU Instance]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/383/"></link>
            <id>https://status.nedap-retail.com/incident/383/</id>
            <summary type="html"><![CDATA[<p>We have monitored the situation and all is working as expected. All services are fully operational again and all data has been processed. Apologies for the inconvenience.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2025-09-22T07:54:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Issues with iD Cloud APIs, Web &amp; Device Management - EU Instance]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/382/"></link>
            <id>https://status.nedap-retail.com/incident/382/</id>
            <summary type="html"><![CDATA[<p>A fix has been identified &amp; implemented for the issues regarding the iD Cloud APIs, iD Cloud Web &amp; Device Management on the EU Instance. Our development team will keep monitoring the situation closely. We apologize for any inconvenience caused.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2025-09-22T05:39:39+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Issues with iD Cloud APIs, Web &amp; Device Management - EU Instance]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/381/"></link>
            <id>https://status.nedap-retail.com/incident/381/</id>
            <summary type="html"><![CDATA[<p>Our teams are still investigating the issues with iD Cloud APIs, iD Cloud Web and Device Management on the EU Instance. We want to reassure you that we are doing our upmost best to get this solved and will send an additional update when we have more information.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2025-09-22T05:18:48+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Issues with iD Cloud APIs, Web &amp; Device Management - EU Instance]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/380/"></link>
            <id>https://status.nedap-retail.com/incident/380/</id>
            <summary type="html"><![CDATA[<p>We are seeing issues with iD Cloud APIs, iD Cloud Web &amp; Device Management on the EU Instance. We are currently investigating with our internal teams and will keep you updated on this status page.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2025-09-22T04:49:15+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[iD Cloud Web service disruption (resolved) - EU &amp; US Instance]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/379/"></link>
            <id>https://status.nedap-retail.com/incident/379/</id>
            <summary type="html"><![CDATA[<p>The iD Cloud Web service disruption has been resolved.
Our development team will keep monitoring the situation.</p>
<p>We apologize for any inconvenience caused.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2025-09-10T13:50:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[iD Cloud Web service disruption (resolved) - EU &amp; US Instance]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/378/"></link>
            <id>https://status.nedap-retail.com/incident/378/</id>
            <summary type="html"><![CDATA[<p>The iD Cloud Web service disruption has been resolved.
Our development team will keep monitoring the situation.</p>
<p>We apologize for any inconvenience caused.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2025-09-10T13:47:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[iD Cloud Web service disruption (investigating) - EU &amp; US Instance]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/377/"></link>
            <id>https://status.nedap-retail.com/incident/377/</id>
            <summary type="html"><![CDATA[<p>We are currently experiencing a service disruption. iD Cloud pages might load slowly or not load at all.
Our development team is working to identify the root cause and implement a solution.</p>
<p>We will send an additional update when we have more information.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2025-09-10T13:40:47+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[iD Cloud Web service disruption (investigating) - EU &amp; US Instance]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/376/"></link>
            <id>https://status.nedap-retail.com/incident/376/</id>
            <summary type="html"><![CDATA[<p>We are currently experiencing a service disruption. iD Cloud pages might load slowly or not load at all.
Our development team is working to identify the root cause and implement a solution.</p>
<p>We will send an additional update when we have more information.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2025-09-10T13:40:23+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Connection issues on iD Cloud services resolved (EU Instance)]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/375/"></link>
            <id>https://status.nedap-retail.com/incident/375/</id>
            <summary type="html"><![CDATA[<p>The networking instability has been addressed and all services are now normally reachable again. We will continue to monitor to ensure full stability. No data was lost during this incident and all data has now been processed.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2025-09-02T19:05:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Connection issues on iD Cloud services (EU Instance)]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/374/"></link>
            <id>https://status.nedap-retail.com/incident/374/</id>
            <summary type="html"><![CDATA[<p>We see the connectivity issues resolving and our services are normally reachable again. Our team is monitoring the situation to make sure all services are stable.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2025-09-02T18:45:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Connection issues on iD Cloud services (EU Instance)]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/372/"></link>
            <id>https://status.nedap-retail.com/incident/372/</id>
            <summary type="html"><![CDATA[<p>We are currently experiencing some instability in our network on the EU instance, which may result in services giving an error. Our networking team is aware of the issue and is actively investigating. We will post an update once we know more.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2025-09-02T18:35:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Delay in Data Processing Issue - EU Instance]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/371/"></link>
            <id>https://status.nedap-retail.com/incident/371/</id>
            <summary type="html"><![CDATA[<p>At the moment, we are not seeing delays in data processing anymore. We apologize for the inconvenience this may have caused and we will keep monitoring this closely.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2025-05-29T11:40:30+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Delay in Data Processing Issue - EU Instance]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/370/"></link>
            <id>https://status.nedap-retail.com/incident/370/</id>
            <summary type="html"><![CDATA[<p>Our team is currently working on validating the cause of the delay in data processing. We will provide you with an update when we have more information available.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2025-05-29T11:23:35+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Delay in Data Processing Issue - EU Instance]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/369/"></link>
            <id>https://status.nedap-retail.com/incident/369/</id>
            <summary type="html"><![CDATA[<p>We are currently seeing a delay in data processing on the EU instance. Our team is investigating this at the moment. We will keep you updated via the status page.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2025-05-29T10:54:59+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[iD Cloud processing delays (EU instance) - fixed]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/368/"></link>
            <id>https://status.nedap-retail.com/incident/368/</id>
            <summary type="html"><![CDATA[<p>We have made some configuration changes to improve the data processing on our iD Cloud EU instance. We see the data processing back to normal levels and all data has now been processed that was inbound to iD Cloud. We will keep monitoring the situation and will update this page when necessary.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2025-04-22T12:46:46+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[iD Cloud Data Processing Delays (EU Instance)]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/367/"></link>
            <id>https://status.nedap-retail.com/incident/367/</id>
            <summary type="html"><![CDATA[<p>We see a delay in data processing for iD Cloud data on our EU instance. Our team is investigating this and keeping a close eye on this. It is possible that data processing is delayed which might impact data shown in Availability, Refill and Realtime Stock levels.
We will update this page as soon as we know more.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2025-04-22T12:28:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[iD Cloud SFTP Server Issue (EU Instance)]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/366/"></link>
            <id>https://status.nedap-retail.com/incident/366/</id>
            <summary type="html"><![CDATA[<p>Everything looks stable again on the SFTP server, We will keep continuing to monitor the situation closely.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2025-04-14T14:10:35+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[iD Cloud SFTP Server Issue (EU Instance)]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/365/"></link>
            <id>https://status.nedap-retail.com/incident/365/</id>
            <summary type="html"><![CDATA[<p>We see that the SFTP data is being processed again and we will keep monitoring this closely. Our sincere apologies for the inconvenience this might have caused.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2025-04-14T13:32:21+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[iD Cloud SFTP Server Issue (EU Instance)]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/364/"></link>
            <id>https://status.nedap-retail.com/incident/364/</id>
            <summary type="html"><![CDATA[<p>At the moment, there are issues with the SFTP server on the EU instance. Our team is investigating this issue and we will keep you informed via this statuspage.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2025-04-14T12:33:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[iD Cloud SFTP Server Issue (EU Instance)]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/363/"></link>
            <id>https://status.nedap-retail.com/incident/363/</id>
            <summary type="html"><![CDATA[<p>The SFTP server on the EU instance is operational again. We will keep monitoring this closely. Our sincere apologies for the inconvencience this might have caused.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2025-04-04T14:16:43+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[iD Cloud SFTP Server Issue (EU Instance)]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/362/"></link>
            <id>https://status.nedap-retail.com/incident/362/</id>
            <summary type="html"><![CDATA[<p>The team implemented a fix and is monitoring the SFTP server on the EU instance. We see that the SFTP data is being processed successfully again. In case we have more information available, this will also be posted on this status page.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2025-04-04T13:51:07+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[iD Cloud SFTP Server Issue (EU Instance)]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/361/"></link>
            <id>https://status.nedap-retail.com/incident/361/</id>
            <summary type="html"><![CDATA[<p>Our team still faces performance issues on the SFTP server on the EU instance. We are watching this closely.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2025-04-04T13:20:36+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[iD Cloud SFTP Server Issue (EU Instance)]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/360/"></link>
            <id>https://status.nedap-retail.com/incident/360/</id>
            <summary type="html"><![CDATA[<p>The SFTP server on the EU instance is up again. Our team is closely watching this at the moment. When we have a next update available, this will be posted on this status page.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2025-04-04T12:50:25+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[iD Cloud SFTP Server Issue Identified (EU Instance)]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/359/"></link>
            <id>https://status.nedap-retail.com/incident/359/</id>
            <summary type="html"><![CDATA[<p>The team has identified the issue and is working to identify how to fix this. Once we have more information, we will keep you updated via this status page.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2025-04-04T12:15:15+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[iD Cloud SFTP Server Issues (EU Instance)]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/357/"></link>
            <id>https://status.nedap-retail.com/incident/357/</id>
            <summary type="html"><![CDATA[<p>At the moment, there are issues with the SFTP server on the EU instance. Our team is investigating this issue and we will keep you informed via this statuspage.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2025-04-04T11:46:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[iD Cloud web loading issues resolved (EU &amp; US instance)]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/356/"></link>
            <id>https://status.nedap-retail.com/incident/356/</id>
            <summary type="html"><![CDATA[<p>Our team has found the issue in iD Cloud web and have implemented a fix for this.
iD Cloud web should be available again for all users. Our apologies for this inconvenience.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2025-02-26T13:55:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[iD Cloud web loading issues (EU &amp; US instance)]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/355/"></link>
            <id>https://status.nedap-retail.com/incident/355/</id>
            <summary type="html"><![CDATA[<p>We are seeing an issue with loading the overview page in iD Cloud web (both EU &amp; US instance). Users see a white screen instead of our normal dashboard.
Our development team is working to identify the root cause and implement a solution.</p>
<p>We will send an additional update when we have more information.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2025-02-26T13:30:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[iD Cloud Realtime stock issues (EU Instance) Resolved]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/352/"></link>
            <id>https://status.nedap-retail.com/incident/352/</id>
            <summary type="html"><![CDATA[<p>The incident involving iD Cloud Realtime Stock on our EU instance has been resolved.
All data processing is back to normal and the realtime stock information is accessible again. This means the iD Cloud features depending on this information are now also working again.</p>
<p>We sincerely apologize for the inconvenience caused by this.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2024-10-24T11:14:38+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[iD Cloud Realtime stock issues (EU Instance)]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/351/"></link>
            <id>https://status.nedap-retail.com/incident/351/</id>
            <summary type="html"><![CDATA[<p>We see our systems recovering and the external provider has posted an update that they have implemented the fix.
Our teams are closely watching the systems to verify all data is processed correctly again. As soon as everything is recovered, we will post an update again.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2024-10-24T11:00:28+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[iD Cloud Realtime stock issues (EU Instance)]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/350/"></link>
            <id>https://status.nedap-retail.com/incident/350/</id>
            <summary type="html"><![CDATA[<p>We received an update that the external provider has identified the issue and that they are implementing a fix. We are keeping a close eye on this and as soon as we see the systems recovering, we will update this page again.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2024-10-24T10:29:43+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[iD Cloud Realtime stock issues (EU Instance)]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/349/"></link>
            <id>https://status.nedap-retail.com/incident/349/</id>
            <summary type="html"><![CDATA[<p>One of our external providers is having issues, which is affecting the iD Cloud service on the EU instance. We have raised a high priority issue with them and the issue is actively being worked on.
Unfortunately until that issue is resolved, all features that require realtime stock information (like Shipments, Refill, Availability, Realtime Count etc) will encounter errors in both the iD Cloud app and iD Cloud web.
As soon as we have more information or updates, we will update you again here.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2024-10-24T09:57:19+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[iD Cloud Realtime stock issues (EU Instance)]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/348/"></link>
            <id>https://status.nedap-retail.com/incident/348/</id>
            <summary type="html"><![CDATA[<p>We are seeing issues with iD Cloud Realtime stock on our EU instance currently. Our technical team is currently investigating this.
This may have impact on Refill and Availability in our mobile apps. And the updates to item statuses are delayed. Also in iD Cloud web, an error may occur when trying to retrieve this data.
When we have more information, this will be shared on our status page.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2024-10-24T09:39:26+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Cube: Issues with authorizations]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/347/"></link>
            <id>https://status.nedap-retail.com/incident/347/</id>
            <summary type="html"><![CDATA[<p>The issue with the authorizations has been identified. A fix is currently being implemented, and the systems are being restored to full functionality.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2024-10-24T08:37:09+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Cube: Issues with authorizations]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/346/"></link>
            <id>https://status.nedap-retail.com/incident/346/</id>
            <summary type="html"><![CDATA[<p>Currently, Cube is experiencing issues with authorizations, which is affecting parts of functionality of the access control system. We are actively working on resolving the issue.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2024-10-24T07:06:06+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[iD Cloud services issues (US instance) resolved]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/345/"></link>
            <id>https://status.nedap-retail.com/incident/345/</id>
            <summary type="html"><![CDATA[<p>Our team has checked all previous errors and ran all necessary tests to mark the issue as resolved. The team will keep monitoring this closely and in case anything changes, we will update the status page again.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2024-09-12T18:30:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[iD Cloud services issues (US instance) are resolved]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/344/"></link>
            <id>https://status.nedap-retail.com/incident/344/</id>
            <summary type="html"><![CDATA[<p>Our team has implemented a fix and we are seeing the error rates going down. The team is monitoring this and running through open alerts to resolve these all. We see data being posted again to and from our iD Cloud applications on the US Instance. We will place an update once all checks have been done.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2024-09-12T17:52:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Service disruption - general (identified) (US Instance)]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/343/"></link>
            <id>https://status.nedap-retail.com/incident/343/</id>
            <summary type="html"><![CDATA[<p>The team is still working on implementing a fix for the issue that was identified on the iD Cloud US Instance. We do not have an estimation yet on how long this will take. As soon as we know more, we will update our status page again. Please know that multiple teams are currently working on resolving the issues we see.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2024-09-12T17:42:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Service disruption - general (Identified) (US Instance)]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/342/"></link>
            <id>https://status.nedap-retail.com/incident/342/</id>
            <summary type="html"><![CDATA[<p>Our team has most likely found the issue and is working on repairing this as fast as possible. Until the fix is implemented, iD Cloud services on the US instance will remain unstable and it is possible that the iD Cloud app and web application are not reachable. We see mostly issues with retrieving data from iD Cloud and in some cases sending data.</p>
<p>We will keep you updated.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2024-09-12T17:18:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Service disruption - general (investigating) (US Instance)]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/341/"></link>
            <id>https://status.nedap-retail.com/incident/341/</id>
            <summary type="html"><![CDATA[<p>At this moment we see errors for our iD Cloud US instance. Our team is currently investigating these and find out what exactly the issue is.
It is possible you experience slow responses in our app and web application at the moment, our APIs are partly unavailable or our app showing a connection error.</p>
<p>Our development team is working to identify the root cause.
We will send an additional update when we have more information.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2024-09-12T16:50:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[iD Cloud Service disruption resolved (EU instance)]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/340/"></link>
            <id>https://status.nedap-retail.com/incident/340/</id>
            <summary type="html"><![CDATA[<p>The past few hours we have seen normal operating procedure of our iD Cloud application and mark this incident as resolved.
Our teams will keep monitoring the applications closely to ensure everything remains stable.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2024-08-13T16:26:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[iD Cloud service disruption (resolving) EU instance]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/339/"></link>
            <id>https://status.nedap-retail.com/incident/339/</id>
            <summary type="html"><![CDATA[<p>The fixes that have been implemented are effective. We continue to see a decreased error rate and our applications return to normal behavior.
Our teams will keep monitoring the situation closely to ensure everything remains stable.</p>
<p>We sincerely apologize for the inconvenience that was caused by this incident.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2024-08-13T13:44:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[iD Cloud service disruption (investigating) EU instance]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/338/"></link>
            <id>https://status.nedap-retail.com/incident/338/</id>
            <summary type="html"><![CDATA[<p>We see that our applications are continuing to show improvements. The team is monitoring this very closely and has this as their highest priority. Although we continue to see a decrease of errors and connection issues, it is still possible that some stores experience a connection issue.</p>
<p>Next to this we would like to ensure you that no data has been lost. Data processing might have been slower than normal, but all data that is processed is valid and will be accessible in iD Cloud.</p>
<p>We will post an update again, if we have more information.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2024-08-13T11:50:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[iD Cloud service disruption (investigating) EU instance]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/337/"></link>
            <id>https://status.nedap-retail.com/incident/337/</id>
            <summary type="html"><![CDATA[<p>We see the performance of our applications improving. Our teams are still working very hard to mitigate the issues and monitoring the improvements. While we see improvements in the usage of iD Cloud, it is still possible that there are connection issues.</p>
<p>Our teams are still working on this with the highest urgency. As soon as we have more information available, we will post an update.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2024-08-13T09:37:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[iD Cloud service disruption (investigating) EU instance]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/336/"></link>
            <id>https://status.nedap-retail.com/incident/336/</id>
            <summary type="html"><![CDATA[<p>We still see some lingering issues from last night, which may cause an interruption in connection to iD Cloud. This may result in not being able to start a count from the app or sending in data.
Our teams are still working on this with the highest urgency. As soon as we have more information available, we will post an update.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2024-08-13T06:15:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[iD Cloud Web service disruption (resolving) EU instance]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/335/"></link>
            <id>https://status.nedap-retail.com/incident/335/</id>
            <summary type="html"><![CDATA[<p>We are currently observing positive improvements in our environment and have decided to continue monitoring performance and stability rather than transitioning to our new environment immediately.</p>
<p>While this approach will take a bit longer, it ensures that we do not risk any data loss. The new environment was successfully brought online and our new environment remains a viable backup option, so we are prepared to switch if necessary.</p>
<p>We understand that this has taken longer than desired and appreciate the urgency for you and your organization. Our teams are diligently working on resolving the issue, and we will provide further updates as soon as we have significant progress to share. Thank you for your patience and understanding.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2024-08-12T23:12:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[iD Cloud Web service disruption (investigating) EU instance]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/334/"></link>
            <id>https://status.nedap-retail.com/incident/334/</id>
            <summary type="html"><![CDATA[<p>For the first approach, we are still in the phase of investigating and attempting to resolve the current issues.</p>
<p>The second team is working diligently and making good progress in setting up the new environment to make the solution available again, should the current environment not be fixed in time.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2024-08-12T21:28:21+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[iD Cloud Web service disruption (investigating) EU instance]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/333/"></link>
            <id>https://status.nedap-retail.com/incident/333/</id>
            <summary type="html"><![CDATA[<p>Due to the prolonged duration of the problems/issues and the lack of a quick solution, we have decided to proceed with two approaches:</p>
<ul>
<li>
<p>We will continue investigating and attempting to resolve the issues in a timely manner.</p>
</li>
<li>
<p>If not resolved within a timely manner, simultaneously, a second team will set up a new environment to restore availability. The downside is that this will result in data loss, but availability will be restored and this is our main priority.</p>
</li>
</ul>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2024-08-12T20:02:53+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[iD Cloud Web service disruption (investigating) EU instance]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/332/"></link>
            <id>https://status.nedap-retail.com/incident/332/</id>
            <summary type="html"><![CDATA[<p>Issues are still ongoing and our teams are still working very hard on fixing the issues. We appreciate your patience and understanding as we continue to resolve them.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2024-08-12T19:01:30+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[iD Cloud Web service disruption (investigating) EU instance]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/331/"></link>
            <id>https://status.nedap-retail.com/incident/331/</id>
            <summary type="html"><![CDATA[<p>All the teams are working very hard to resolve these issues regarding Transactions and Team counting, this being our top priority.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2024-08-12T18:27:56+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[iD Cloud Web service disruption (investigating) EU instance]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/330/"></link>
            <id>https://status.nedap-retail.com/incident/330/</id>
            <summary type="html"><![CDATA[<p>We are still working on fixes throughout the clusters. We identified that we are mainly experiencing issues with Transactions and Team counting.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2024-08-12T17:54:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[iD Cloud Web service disruption (investigating) EU instance]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/329/"></link>
            <id>https://status.nedap-retail.com/incident/329/</id>
            <summary type="html"><![CDATA[<p>We are still working on fixes throughout the clusters. Until the issues are fixed it is possible that our applications (API, web and app) still encounter processing delays.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2024-08-12T17:07:07+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[iD Cloud Web service disruption (investigating) EU instance]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/328/"></link>
            <id>https://status.nedap-retail.com/incident/328/</id>
            <summary type="html"><![CDATA[<p>Our hosting partner has identified the cause and is working on fixes throughout the clusters.
Until the issues are fixed it is possible that our applications (API, web and app) still encounter processing delays. The teams are working on this to get this resolved as quickly as possible. Once we have more information, we will post an update again on our status page.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2024-08-12T16:26:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[iD Cloud Web service disruption (investigating) EU instance]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/327/"></link>
            <id>https://status.nedap-retail.com/incident/327/</id>
            <summary type="html"><![CDATA[<p>One of our messaging processing systems has degraded performance. This may result in slower performance or time outs. Our development team is working, together with our hosting partner, to identify the root cause.</p>
<p>We will send an additional update when we have more information.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2024-08-12T15:47:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[iD Cloud Service disruption resolved (EU instance)]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/326/"></link>
            <id>https://status.nedap-retail.com/incident/326/</id>
            <summary type="html"><![CDATA[<p>The fixes have been implemented by our network partner and we see our services are back to normal again. Our development teams will keep monitoring the situation to ensure everything remains stable.</p>
<p>We sincerely apologize for the inconvenience that was caused by this incident.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2024-07-09T16:59:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[iD Cloud Service disruption resolving (EU instance)]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/325/"></link>
            <id>https://status.nedap-retail.com/incident/325/</id>
            <summary type="html"><![CDATA[<p>We see our services improving and the error rate going down, this means that most of our applications are reachable again. Our network partner is still working on implementing the final fixes and we will post an update once all services are completely back to normal again.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2024-07-09T16:45:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[iD Cloud Service disruption (EU instance)]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/324/"></link>
            <id>https://status.nedap-retail.com/incident/324/</id>
            <summary type="html"><![CDATA[<p>Our network partner has identified the cause and is implementing fixes throughout the clusters. We see improvements in the error rates from these fixes. Until the fixes are applied to the whole environment, it is still possible that a connection issue occurs. The team is working as quickly as possible to get the fixes in place and get our services back to normal.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2024-07-09T16:22:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[iD Cloud Service disruption (EU instance)]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/323/"></link>
            <id>https://status.nedap-retail.com/incident/323/</id>
            <summary type="html"><![CDATA[<p>Our network partner is looking into the issues and trying to find the root cause. Until the issues are fixed it is possible that our applications (API, web and app) still encounter intermittent connection issues. The teams are working on this to get this resolved as quickly as possible. Once we have more information, we will post an update again on our status page.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2024-07-09T15:55:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[iD Cloud Web service disruption (EU instance)]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/322/"></link>
            <id>https://status.nedap-retail.com/incident/322/</id>
            <summary type="html"><![CDATA[<p>We are currently experiencing a service disruption. iD Cloud web, our APIs or mobile app on the EU instance might load slowly or not load at all.
Our development team is working, together with our network partner, to identify the root cause and implement a solution.</p>
<p>We will send an additional update when we have more information.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2024-07-09T15:30:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Data Processing Delays - Shipments (EU Instance) Fixed]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/320/"></link>
            <id>https://status.nedap-retail.com/incident/320/</id>
            <summary type="html"><![CDATA[<p>We can safely confirm that the team's fix has resolved the issue. Data processing is as expected.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2023-10-24T17:53:17+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Data Processing Delays - Shipments (EU instance) Watching]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/319/"></link>
            <id>https://status.nedap-retail.com/incident/319/</id>
            <summary type="html"><![CDATA[<p>The team has implemented a fix that has resolved the delay in processing the shipments. We will be monitoring the situation closely.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2023-10-24T14:45:07+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Data Processing Delays - Shipments (EU instance) Identified]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/318/"></link>
            <id>https://status.nedap-retail.com/incident/318/</id>
            <summary type="html"><![CDATA[<p>The root cause of the delay in the processing of the shipments has been identified.  The team is working on a patch to solve the issue.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2023-10-24T13:52:13+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Data Processing Delays - Shipments (EU instance) Investigating]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/317/"></link>
            <id>https://status.nedap-retail.com/incident/317/</id>
            <summary type="html"><![CDATA[<p>Our data processing infrastructure is running behind, which is causing inaccuracies. There is a delay in the processing of the information of the shipments. Customers might experience a delay in the processing of stock mutations. We are still investigating the root cause.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2023-10-24T13:25:33+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Data Processing Delays - Shipments (EU instance) Investigating]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/316/"></link>
            <id>https://status.nedap-retail.com/incident/316/</id>
            <summary type="html"><![CDATA[<p>Our data processing infrastructure is running behind which is causing inaccuracies. There is a delay in the processing of the information of the shipments. We are still investigating the root cause.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2023-10-24T12:56:50+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Data Processing Delays- Shipments (EU instance) Investigating]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/315/"></link>
            <id>https://status.nedap-retail.com/incident/315/</id>
            <summary type="html"><![CDATA[<p>Our data processing infrastructure is running behind which is causing inaccuracies. There is a delay in the processing of the information of the shipments. We are investigating the root cause.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2023-10-24T12:23:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Degraded Performance with teamcounting - fixed (EU instance)]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/314/"></link>
            <id>https://status.nedap-retail.com/incident/314/</id>
            <summary type="html"><![CDATA[<p>The service disruption has been resolved. We have implemented a solution and after closely monitoring, the situation is stable.</p>
<p>We apologize for any inconvenience this may have caused.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2023-10-09T13:52:06+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Degraded Performance with teamcounting - monitoring (EU instance)]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/312/"></link>
            <id>https://status.nedap-retail.com/incident/312/</id>
            <summary type="html"><![CDATA[<p>The performance issues of Teamcounting have been resolved. All counts have been processed, and no data has been lost.
The development team has identified the root cause and will implement a solution this afternoon. Until then we will closely monitor the situation.</p>
<p>We will update the status page when we have implemented the solution.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2023-10-09T08:22:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Degraded Performance with teamcounting -  investigating (EU instance)]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/311/"></link>
            <id>https://status.nedap-retail.com/incident/311/</id>
            <summary type="html"><![CDATA[<p>We are currently experiencing a service disruption. This has impacted the performance of Teamcounting.</p>
<p>Our development team has identified a possible cause and is investigating further.</p>
<p>We will send an additional update when we have more information.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2023-10-09T07:57:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Nedap Retail services reachable again - issues resolved (EU instance)]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/310/"></link>
            <id>https://status.nedap-retail.com/incident/310/</id>
            <summary type="html"><![CDATA[<p>The issues were fixed by our development teams and all processing is restored to normal. Our services are functioning normally again, which means iD Cloud web, iD Cloud app, Device Management and Analytics are reachable again.
We are very sorry for the inconvenience caused by this. A further investigation will follow during the following week.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2023-07-30T18:05:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Nedap Retail services not reachable (EU instance)]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/309/"></link>
            <id>https://status.nedap-retail.com/incident/309/</id>
            <summary type="html"><![CDATA[<p>At the moment we are experiencing an issue on our EU instance where our Nedap Retail services (including iD Cloud web, iD Cloud app, Device Management and Analytics are currently not reachable. Our developers are investigating the issue at this moment and hope to be able to find the root cause quickly. We will keep this page updated.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2023-07-30T17:40:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Elevated API Errors]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/308/"></link>
            <id>https://status.nedap-retail.com/incident/308/</id>
            <summary type="html"><![CDATA[<p>The measures we have taken to work around the AWS issues were successful. Our dashboards and monitoring systems have returned to normal and our applications are functional again. Again, our sincere apologies for any inconvenience caused.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2023-06-30T17:12:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Elevated API Errors]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/307/"></link>
            <id>https://status.nedap-retail.com/incident/307/</id>
            <summary type="html"><![CDATA[<p>We have rerouted traffic to work around the unavailability of some of our AWS EC2 instances and are currently seeing error rates going down. We will continue to monitor the situation and take action when necessary.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2023-06-30T16:43:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Elevated API Errors]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/306/"></link>
            <id>https://status.nedap-retail.com/incident/306/</id>
            <summary type="html"><![CDATA[<p>Due to the elevated API errors we see, iD Cloud web and our iD Cloud App are not functioning properly. Unfortunately AWS is still experiencing issues with connectivity and we will update you as soon as these issues have been resolved by AWS.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2023-06-30T16:07:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Elevated API Errors]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/305/"></link>
            <id>https://status.nedap-retail.com/incident/305/</id>
            <summary type="html"><![CDATA[<p>We are experiencing an elevated level of API errors. We received a message from AWS stating: &quot;We are investigating an issue that impacts the availability of some EC2 instances in the us-east-2 region.&quot;</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2023-06-30T15:51:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Elevated API Errors]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/304/"></link>
            <id>https://status.nedap-retail.com/incident/304/</id>
            <summary type="html"><![CDATA[<p>We are experiencing an elevated level of API errors and are currently investigating the issue.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2023-06-30T15:41:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Elevated API Errors (EU instance)]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/303/"></link>
            <id>https://status.nedap-retail.com/incident/303/</id>
            <summary type="html"><![CDATA[<p>The elevated errors in our APIs have been resolved. The processing of messages on our APIs is back to normal and therefore our iD Cloud app and web application are performing normally again. Our development team is still monitoring this very closely and if there are any new updates we will post these on this page.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2023-06-22T10:17:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Elevated API Errors (EU instance)]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/302/"></link>
            <id>https://status.nedap-retail.com/incident/302/</id>
            <summary type="html"><![CDATA[<p>We have identified the root cause of the issue. Our teams are working on implementing improvements on our servers to get all delays resolved. We will keep you posted via this page.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2023-06-22T10:04:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Elevated API Errors (EU instance)]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/301/"></link>
            <id>https://status.nedap-retail.com/incident/301/</id>
            <summary type="html"><![CDATA[<p>We also see a delay in retrieving and creating Shipment notices. This can cause errors in our iD Cloud app when trying to receive shipments. We kindly ask you to wait until the incident is resolved for receiving shipments in your stores. Our development team is still trying to resolve these issues and we will keep you posted via this page.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2023-06-22T09:28:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Elevated API Errors (EU instance)]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/300/"></link>
            <id>https://status.nedap-retail.com/incident/300/</id>
            <summary type="html"><![CDATA[<p>We see elevated errors on our Article API, this can also impact loading of other features in our iD Cloud application. It can take a bit longer to load expected stock for an RFID count or to retrieve Refill suggestions. Our team is working hard to get these errors resolved as soon as possible and we will keep you updated via this page.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2023-06-22T09:09:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Elevated API Errors (EU instance)]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/299/"></link>
            <id>https://status.nedap-retail.com/incident/299/</id>
            <summary type="html"><![CDATA[<p>Most impacted is currently the retrieving of article images to show in our iD Cloud app and web application. Our team is further investigating and trying to resolve the issue as fast as possible. We will post updates on this page when we know more.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2023-06-22T08:48:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Elevated API Errors (EU instance)]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/298/"></link>
            <id>https://status.nedap-retail.com/incident/298/</id>
            <summary type="html"><![CDATA[<p>Unfortunately we are experiencing an elevated level of API errors and are currently investigating the issue.
We see that some of our iD Cloud applications respond slowly. All our developers are currently on this case and we will try to get this resolved a.s.a.p.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2023-06-22T08:25:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Service disruption - general (resolved) (EU instance)]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/297/"></link>
            <id>https://status.nedap-retail.com/incident/297/</id>
            <summary type="html"><![CDATA[<p>The service disruption has been resolved.
Our development team will keep monitoring the situation.</p>
<p>We apologize for any inconvenience caused.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2023-06-22T00:17:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Elevated API Errors (EU instance)]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/295/"></link>
            <id>https://status.nedap-retail.com/incident/295/</id>
            <summary type="html"><![CDATA[<p>We are experiencing an elevated level of API errors and are currently investigating the issue.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2023-06-21T23:01:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Performance issues with the expected stock endpoints (EU and US) (resolved)]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/294/"></link>
            <id>https://status.nedap-retail.com/incident/294/</id>
            <summary type="html"><![CDATA[<p>All issues with the expected stock endpoints have been resolved.</p>
<p>We would like to extend our sincere apologies for the inconvenience caused by this incident.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2023-06-19T20:35:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Performance issues with the expected stock endpoints (EU and US) (resolved)]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/293/"></link>
            <id>https://status.nedap-retail.com/incident/293/</id>
            <summary type="html"><![CDATA[<p>The issues within the EU and US instances are resolved. Applications in the EU are recovered while the issues in the US are in the process of starting to recover.</p>
<p>Our team is closely monitoring the situation.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2023-06-19T19:42:39+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Performance issues with the expected stock endpoints (EU and US) (Investigating)]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/292/"></link>
            <id>https://status.nedap-retail.com/incident/292/</id>
            <summary type="html"><![CDATA[<p>We are currently experiencing issues with the expected stock endpoints on the EU and US instances. Expected stock may not be up to date when starting a count. We are investigating the issue.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2023-06-19T16:59:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Connection issues Nedap Retail Services (EU instance)]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/291/"></link>
            <id>https://status.nedap-retail.com/incident/291/</id>
            <summary type="html"><![CDATA[<p>Our team has been monitoring the situation closely the past hour and we see that all applications are connecting normally again.</p>
<p>The connection issues are now resolved and all systems are operational again.
A further investigation will follow on this incident and we will post a post mortem on our support portal once this investigation is finalized.</p>
<p>We would like to extend our sincere apologies for the inconvenience caused by this incident.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2023-05-30T15:52:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Connection issues Nedap Retail Services (EU instance)]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/290/"></link>
            <id>https://status.nedap-retail.com/incident/290/</id>
            <summary type="html"><![CDATA[<p>Our team has implemented fixes on our EU instance servers to solve the connection issues. We see that our systems recovered and applications from the field are coming back online and are able to connect again.</p>
<p>Our team is closely monitoring this situation and we will place an update once we see all systems are green again. No data has been lost during this incident.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2023-05-30T14:36:19+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Connection issues Nedap Retail Services (EU instance)]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/289/"></link>
            <id>https://status.nedap-retail.com/incident/289/</id>
            <summary type="html"><![CDATA[<p>We have rerouted some traffic, which resulted in better availability of our server applications. We will continue investigating the source of the issue and monitor the ongoing situations.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2023-05-30T14:09:01+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Connection issues Nedap Retail Services (EU instance)]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/288/"></link>
            <id>https://status.nedap-retail.com/incident/288/</id>
            <summary type="html"><![CDATA[<p>A critical part of our infrastructure is having issues, causing our devices (gates and apps) in the field to reconnect, slowing down all network traffic. Most apps and integrations are impacted.
Our teams are still investigating and as soon as we have an additional update we will update our status page.</p>
<p>We are very sorry for the inconvenience and hope to have the issues resolved as soon as possible</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2023-05-30T13:54:16+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Connection issues Nedap Retail Services (EU instance)]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/287/"></link>
            <id>https://status.nedap-retail.com/incident/287/</id>
            <summary type="html"><![CDATA[<p>The connection issues are still being investigated. This can impact the following services and give errors when trying to connect to these:</p>
<ul>
<li>iD Cloud Web (EU)</li>
<li>iD Cloud Apps (EU)</li>
<li>iD Cloud API (EU)</li>
<li>iD Cloud SFTP (EU)</li>
<li>iD Cloud EAS (EU)</li>
<li>Cube</li>
<li>Nedap Retail Analytics</li>
<li>Device Management</li>
</ul>
<p>Connection might be very slow or giving an error while trying to connect.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2023-05-30T12:55:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[iD Cloud Web service disruption (EU instance)]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/286/"></link>
            <id>https://status.nedap-retail.com/incident/286/</id>
            <summary type="html"><![CDATA[<p>We are experiencing some performance issues on EU servers. iD Cloud Web and Device Management are still working but could be a little slower than expected. We are closely monitoring the situation.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2023-05-30T11:30:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Connection issues resolved on Nedap Retail Services (EU instance)]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/285/"></link>
            <id>https://status.nedap-retail.com/incident/285/</id>
            <summary type="html"><![CDATA[<p>Our team has been monitoring the situation closely the past hour and we see that all applications are connecting normally again.
The connection issues are now resolved and all systems are operational again.</p>
<p>A further investigation will follow on this incident and we will post a post mortem on our support portal once this investigation is finalized.
We would like to extend our sincere apologies for the inconvenience caused by this incident.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2023-04-21T18:25:37+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Connection issues Nedap Retail Services (EU instance)]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/284/"></link>
            <id>https://status.nedap-retail.com/incident/284/</id>
            <summary type="html"><![CDATA[<p>Our team has implemented fixes on our EU instance servers to solve the connection issues. We see our systems recovering and applications from the field are coming back online and are able to connect again. The upcoming hours all connections will recover. During this period, connection can still be a bit slower, but this should resolve in the upcoming hours.</p>
<p>Our team is closely monitoring this situation and we will again place an update once we see all systems are green again.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2023-04-21T17:19:07+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Connection issues Nedap Retail Services (EU instance)]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/283/"></link>
            <id>https://status.nedap-retail.com/incident/283/</id>
            <summary type="html"><![CDATA[<p>Our teams have implemented measures to reduce the connection issues on our EU instance. We see some improvements in the connectivity of our applications, but we are still investigating the root cause. We continue to work very hard with multiple teams on finding and implementing a solution.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2023-04-21T16:45:29+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Connection issues Nedap Retail Services (EU instance)]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/282/"></link>
            <id>https://status.nedap-retail.com/incident/282/</id>
            <summary type="html"><![CDATA[<p>Our development teams and our hosting partner are all investigating the connection issues on our EU instance to find out what is causing these issues. Unfortunately we have not yet been able to resolve these issues, but are still working on this very hard.</p>
<p>We are very sorry for the inconvenience and hope to have the issues resolved as soon as possible.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2023-04-21T15:23:54+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Connection issues Nedap Retail Services (EU instance)]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/281/"></link>
            <id>https://status.nedap-retail.com/incident/281/</id>
            <summary type="html"><![CDATA[<p>Our teams have not yet found the root cause of the connection issues. They are still investigating and as soon as we have an additional update we will update our status page.</p>
<p>We are very sorry for the inconvenience and hope to have the issues resolved as soon as possible.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2023-04-21T14:28:52+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Connection issues Nedap Retail Services (EU instance)]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/280/"></link>
            <id>https://status.nedap-retail.com/incident/280/</id>
            <summary type="html"><![CDATA[<p>The connection issues are still being investigated. This can impact the following services and give errors when trying to connect to these:</p>
<ul>
<li>iD Cloud Web (EU)</li>
<li>iD Cloud Apps (EU)</li>
<li>iD Cloud API (EU)</li>
<li>iD Cloud SFTP (EU)</li>
<li>iD Cloud EAS (EU)</li>
<li>Cube</li>
<li>Nedap Retail Analytics</li>
<li>Device Management</li>
</ul>
<p>Connection might be very slow or giving an error while trying to connect. We are trying to find the root cause and resolve the issue as soon as possible. We will keep you updated via our status page.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2023-04-21T13:38:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Connection issues iD Cloud (EU instance)]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/279/"></link>
            <id>https://status.nedap-retail.com/incident/279/</id>
            <summary type="html"><![CDATA[<p>We see connection issues to our iD Cloud EU instance. Our teams are currently investigating this and we will update you as soon as possible.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2023-04-21T13:15:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Issues with the Shipments functionality on the EU instance (resolved)]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/278/"></link>
            <id>https://status.nedap-retail.com/incident/278/</id>
            <summary type="html"><![CDATA[<p>The issues with the database servers with processing some shipments have been resolved.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2023-04-12T13:38:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Issues with the Shipments functionality on the EU instance (investigating)]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/277/"></link>
            <id>https://status.nedap-retail.com/incident/277/</id>
            <summary type="html"><![CDATA[<p>We are currently experiencing issues with our database servers with processing some shipments. Our technical team is currently investigating these issues. As soon as we know more, we will place an update on this page.</p>
<p>We apologize for any inconvenience caused.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2023-04-12T12:17:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Scheduled Maintenance on Shipment API (US instance &amp; EU instance)]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/276/"></link>
            <id>https://status.nedap-retail.com/incident/276/</id>
            <summary type="html"><![CDATA[<p>On Sunday 9 April 2023, the iD Cloud Shipments functionality and APIs will be partly unavailable due to a scheduled maintenance window.</p>
<ul>
<li>Time frame <strong>09:00 - 10:00 CEST - US instance</strong> will be in maintenance</li>
<li>Time frame <strong>10:00 - 13:00 CEST - EU instance</strong> will be in maintenance</li>
</ul>
<p>During this time frame the Shipment API will be only partly available. More details on this maintenance can be found on <a href="https://support.nedapretail.com/support/solutions/articles/22000279417">our support portal</a>.</p>
<p><strong>Update US instance:</strong> The maintenance on our US instance was done successfully and the Shipment functionality and APIs are available again.</p>
<p><strong>Update EU instance:</strong> 12:49 CEST - The migration on the EU instance is currently in motion. The maintenance takes a little bit longer then expected, but we expect this to be done within the next few hours. Details on how this migration can impact your organization can be found on <a href="https://support.nedapretail.com/support/solutions/articles/22000279417">our support portal</a>.</p>
<p>13:35 CEST - The maintenance on the EU instance has been finalized. The Shipment functionality and APIs are available again.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2023-04-09T06:43:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Authetication issues resolved (EU instance)]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/275/"></link>
            <id>https://status.nedap-retail.com/incident/275/</id>
            <summary type="html"><![CDATA[<p>Our development team was able to resolve the issues with authentication on our EU instance. This means that all our applications (web and mobile) should work normally again.
Our backend applications are catching up with the processing delay and is expected to be caught up shortly. No data has been lost.</p>
<p>Our team will investigate this further and will look into any further actions needed to prevent this in the future. We sincerely apologize for the inconvenience caused by this issue.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2022-11-29T16:30:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Authentication issues causing processing delays (EU instance)]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/274/"></link>
            <id>https://status.nedap-retail.com/incident/274/</id>
            <summary type="html"><![CDATA[<p>Due to the authentication issues we currently face on our EU instance, it is also possible that long lived API tokens receive errors due to the delay in response. Next to this we see some processing delays in our backend applications. Once the authentication issues have been resolved these processing delays will resolve again. We will keep you updated via this page.</p>
<p>Update: it is also possible that the iD Cloud mobile apps face synchronization or connection issues</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2022-11-29T15:10:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Authentication issues (EU instance)]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/273/"></link>
            <id>https://status.nedap-retail.com/incident/273/</id>
            <summary type="html"><![CDATA[<p>Our development team has identified the issue and is currently working to resolving this. They are working on this as fast as possible.
Until the issues are completely resolved it is not possible to do a new login into our web applications, SFTP server or API connection (via short lived tokens).</p>
<p>We sincerely apologize for the inconvenience.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2022-11-29T14:45:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Authentication issues (EU instance)]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/272/"></link>
            <id>https://status.nedap-retail.com/incident/272/</id>
            <summary type="html"><![CDATA[<p>We are seeing issues with creating new OAuth tokens which is used in connecting to our Nedap Retail systems on the EU instance. This means that for some users it will currently not be possible to login to iD Cloud web or create a new short lived token for use in APIs or SFTP.</p>
<p>Our development team is investigating the issue and is working to get this resolved a.s.a.p.</p>
<p>We will post an update as soon as we have more information.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2022-11-29T13:50:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Service disruption - general (resolved) (EU instance)]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/271/"></link>
            <id>https://status.nedap-retail.com/incident/271/</id>
            <summary type="html"><![CDATA[<p>The service disruption has been resolved.
Our development team will keep monitoring the situation.</p>
<p>We apologize for any inconvenience caused.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2022-11-21T11:35:08+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Service disruption - general (investigating) (EU instance)]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/269/"></link>
            <id>https://status.nedap-retail.com/incident/269/</id>
            <summary type="html"><![CDATA[<p>We are currently experiencing a service disruption on our iD Cloud EU instance. Multiple of our Nedap Retail applications and or APIs might load slowly or not load at all.
The affected applications can be seen in the statuses listed above.</p>
<p>Our development team is working to identify the root cause and implement a solution.</p>
<p>We will send an additional update when we have more information.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2022-11-21T10:04:13+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Service disruption - general (resolved)]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/268/"></link>
            <id>https://status.nedap-retail.com/incident/268/</id>
            <summary type="html"><![CDATA[<p>The service disruption has been resolved.
Our development team will keep monitoring the situation.</p>
<p>We apologize for any inconvenience caused.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2022-11-20T18:10:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Service disruption - general (investigating)]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/267/"></link>
            <id>https://status.nedap-retail.com/incident/267/</id>
            <summary type="html"><![CDATA[<p>We are currently experiencing a service disruption. Multiple of our Nedap Retail applications might load slowly or not load at all.
The affected applications can be seen in the statuses listed above.</p>
<p>Our development team is working to identify the root cause and implement a solution.</p>
<p>We will send an additional update when we have more information.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2022-11-20T15:36:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Email delivery is working again]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/266/"></link>
            <id>https://status.nedap-retail.com/incident/266/</id>
            <summary type="html"><![CDATA[<p>The external service has fixed the email delivery issues. They are now processing the backlog of emails that accumulated during their outage. All scheduled emails from our online services will be delivered into your mailbox. We apologize for any inconvenience this might have caused you today.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2022-11-02T15:56:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Email delivery is delayed]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/265/"></link>
            <id>https://status.nedap-retail.com/incident/265/</id>
            <summary type="html"><![CDATA[<p>The external service that delivers our emails for reports and account details is currently encountering an outage. Due to this, the emails from our services are delayed.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2022-11-02T07:41:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Email delivery is working again]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/264/"></link>
            <id>https://status.nedap-retail.com/incident/264/</id>
            <summary type="html"><![CDATA[<p>The external service has fixed the email delivery issues. They are now processing the backlog of emails that accumulated during their outage. All scheduled emails from our online services will be delivered into your mailbox. We apologize for any inconvenience this might have caused you today.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2022-11-01T07:43:05+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Email delivery is delayed]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/263/"></link>
            <id>https://status.nedap-retail.com/incident/263/</id>
            <summary type="html"><![CDATA[<p>The external service that delivers our emails for reports and account details is currently encountering an outage. Due to this, the emails from our services are delayed.
Once the external service is up and running again, all emails will automatically be delivered.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2022-10-31T19:11:07+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[iD Cloud Web service disruption (resolved)]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/262/"></link>
            <id>https://status.nedap-retail.com/incident/262/</id>
            <summary type="html"><![CDATA[<p>The iD Cloud service disruption has been resolved.
Our development team will keep monitoring the situation.
We apologize for any inconvenience caused.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2022-10-25T06:46:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[iD Cloud Web service disruption (investigating)]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/261/"></link>
            <id>https://status.nedap-retail.com/incident/261/</id>
            <summary type="html"><![CDATA[<p>We are currently experiencing a service disruption. iD Cloud pages and article synchronization might load slowly or not load at all.
Our development team is working to identify the root cause and implement a solution.</p>
<p>We will send an additional update when we have more information.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2022-10-25T06:30:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Data Processing Delays - Reporting Tools Affected]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/260/"></link>
            <id>https://status.nedap-retail.com/incident/260/</id>
            <summary type="html"><![CDATA[<p>The root cause was found for the delays in our data processing infrastructure. No data has been lost and it should be caught up in a few hours.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2022-10-21T14:25:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Data Processing Delays - Reporting Tools Affected]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/259/"></link>
            <id>https://status.nedap-retail.com/incident/259/</id>
            <summary type="html"><![CDATA[<p>Our data processing infrastructure is running behind which is causing significant delays in the reporting tools. No data has been lost. We are investigating the cause of the delays.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2022-10-21T07:00:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Connection issues iD Cloud US instance resolved]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/258/"></link>
            <id>https://status.nedap-retail.com/incident/258/</id>
            <summary type="html"><![CDATA[<p>Our team was able to resolve the connection issues to our iD Cloud US instance. Our team will further investigate the root cause and a post mortem will be placed on our support portal.</p>
<p><strong>Update:</strong> only our iD Cloud web environment had connection issues. All our back-end processes were not affected and our APIs were accessible the whole time. This means no data has been lost.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2022-09-30T08:45:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Connection issues iD Cloud US Instance]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/257/"></link>
            <id>https://status.nedap-retail.com/incident/257/</id>
            <summary type="html"><![CDATA[<p>We see intermittent connection interruptions to our services on our US cluster. Our team is investigating and trying to resolve the issue as soon as possible.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2022-09-30T08:15:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[iD Cloud iOS app v2022.3.1 now available]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/256/"></link>
            <id>https://status.nedap-retail.com/incident/256/</id>
            <summary type="html"><![CDATA[<p>The new app version, iD Cloud iOS app v2022.3.1, with the hotfix for the receiving issue is now available in the Apple App Store.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2022-07-14T17:05:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[iD Cloud app iOS 2022.3.0 - Receiving of goods not available]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/255/"></link>
            <id>https://status.nedap-retail.com/incident/255/</id>
            <summary type="html"><![CDATA[<p>Our development team has created a hotfix for the receiving issue in iOS app v2022.3.0. The new app version has now been tested and is submitted to Apple for review.
This app version is v2022.3.1 and will become available in the Apple App Store as soon as the review from Apple is done.</p>
<p>We apologize for the inconvenience caused by this issue.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2022-07-14T14:20:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[iD Cloud app iOS 2022.3.0 - Receiving of goods not available]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/254/"></link>
            <id>https://status.nedap-retail.com/incident/254/</id>
            <summary type="html"><![CDATA[<p>Update: To prevent iOS mobile devices — that have not yet been upgraded to 2022.3.0 — from upgrading, the iD Cloud iOS app has been removed from the App Store as a precaution. Our development team is working on a hotfix for this issue that will become available in a new app release.
We will update this page as soon as this hotfix is available and an additional email will be sent to all iOS customers to inform them about the hotfix changes.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2022-07-14T11:15:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[iD Cloud app iOS 2022.3.0 - Receiving of goods not available]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/253/"></link>
            <id>https://status.nedap-retail.com/incident/253/</id>
            <summary type="html"><![CDATA[<p>An issue has been detected with the iD Cloud iOS app (2022.3.0) released on Wednesday, July 13. When the shipment receiving process is finished, a thumbs-down is sometimes shown, with the message that the shipment has already been received elsewhere (which is not the case). We are working on a solution to resolve this issue.
This issue only applies if you receive with an ASN as reference</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2022-07-13T15:36:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Login via external service and access to developer portal available again]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/252/"></link>
            <id>https://status.nedap-retail.com/incident/252/</id>
            <summary type="html"><![CDATA[<p>The issues at Cloudflare seem to have been resolved. This means that our external login service via Auth0 and our developer portal are available again.
If anything changes, we will update you via this page.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2022-06-21T07:27:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Login via external service and access to developer portal not possible]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/251/"></link>
            <id>https://status.nedap-retail.com/incident/251/</id>
            <summary type="html"><![CDATA[<p>Our third party vendor Auth0 is having an outage which causes login via external service to not be available. Also our developer portal is not reachable at the moment due to this issue.</p>
<p>The root cause seems to be issues with Cloudflare which a lot of services world wide are relying on for secure connectivity.
More information can be found on their statuspage. https://www.cloudflarestatus.com/</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2022-06-21T06:56:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[iD Cloud web - Count control working again (EU instance only)]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/250/"></link>
            <id>https://status.nedap-retail.com/incident/250/</id>
            <summary type="html"><![CDATA[<p>All work that was affecting the Count Control page in iD Cloud web (EU only) has been finished. The page should be loading normally again.
We apologize for the inconvenience caused by this.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2022-06-15T13:40:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[iD Cloud web - Count control sometimes loading slow (EU instance only)]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/249/"></link>
            <id>https://status.nedap-retail.com/incident/249/</id>
            <summary type="html"><![CDATA[<p>Due to unforeseen circumstances during a scheduled update on our servers, the count control page on the EU instance of iD Cloud web will sometimes be a little bit slow in loading or not available. If this occurs, this will only last a couple of minutes, so please try to reload the page after a few minutes.
We sincerely apologize for the inconvenience caused by this.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2022-06-15T11:00:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Support portal is reachable again]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/248/"></link>
            <id>https://status.nedap-retail.com/incident/248/</id>
            <summary type="html"><![CDATA[<p>The login issues with the support portal are resolved and everyone should be able to access the support portal again. If you still encounter any issues, please reach out to us via email.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2022-06-01T07:35:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Support portal sometimes not reachable]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/247/"></link>
            <id>https://status.nedap-retail.com/incident/247/</id>
            <summary type="html"><![CDATA[<p>Our support portal is hosted with Freshdesk and we are encountering some intermittent login issues at the moment. We are in contact with Freshdesk to get this resolved as quickly as possible.
You can still reach our support teams via the normal email addresses and we will be able to deliver support to you via that way. We will update you here as soon as it is all resolved.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2022-06-01T07:00:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Service disruption - general EU (resolved)]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/246/"></link>
            <id>https://status.nedap-retail.com/incident/246/</id>
            <summary type="html"><![CDATA[<p>The service disruption has been resolved.
Our development team will keep monitoring the situation.</p>
<p>We apologize for any inconvenience caused.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2022-05-12T14:06:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Service disruption - general EU (investigating)]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/245/"></link>
            <id>https://status.nedap-retail.com/incident/245/</id>
            <summary type="html"><![CDATA[<p>We are currently experiencing a service disruption. Multiple of our Nedap Retail applications might load slowly or not load at all.
The affected applications can be seen in the statuses listed above.</p>
<p>Our development team is working to identify the root cause and implement a solution.</p>
<p>We will send an additional update when we have more information.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2022-05-12T13:58:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[iD Cloud Web service disruption in the US (resolved)]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/244/"></link>
            <id>https://status.nedap-retail.com/incident/244/</id>
            <summary type="html"><![CDATA[<p>The iD Cloud Web service disruption has been resolved.
Our development team will keep monitoring the situation.
We apologize for any inconvenience caused.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2022-05-11T17:12:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[iD Cloud Web service disruption in the US (investigating)]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/243/"></link>
            <id>https://status.nedap-retail.com/incident/243/</id>
            <summary type="html"><![CDATA[<p>We are currently experiencing a service disruption. iD Cloud pages might load slowly or not load at all.
Our development team is working to identify the root cause and implement a solution.</p>
<p>We will send an additional update when we have more information.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2022-05-11T16:51:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Issues with external login provider (Auth0) - resolved]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/242/"></link>
            <id>https://status.nedap-retail.com/incident/242/</id>
            <summary type="html"><![CDATA[<p>The issues with our external login provider (Auth0) have been resolved. Some login attempts ended in an SSL error, which has now been resolved.
All users should be able to login again. Our team will keep monitoring the situation. We sincerely apologize for the inconvenience caused by this.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2022-05-05T10:02:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Issues with external login provider (Auth0)]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/241/"></link>
            <id>https://status.nedap-retail.com/incident/241/</id>
            <summary type="html"><![CDATA[<p>Unfortunately we are again experiencing issues with our external login provider (Auth0). Users that try to login via SSO may experience an error while trying to login with external credentials.</p>
<p>Our development team is currently investigating this issue and trying to get this resolved with the external login provider as quickly as possible. We will update the status page once we have more information.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2022-05-05T09:55:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Issues with external login provider (Auth0) - resolved]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/240/"></link>
            <id>https://status.nedap-retail.com/incident/240/</id>
            <summary type="html"><![CDATA[<p>The issues with our external login provider (Auth0) have been resolved. All users should be able to login again.
We sincerely apologize for the inconvenience caused by this.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2022-05-04T15:55:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Issues with external login provider (Auth0)]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/239/"></link>
            <id>https://status.nedap-retail.com/incident/239/</id>
            <summary type="html"><![CDATA[<p>We are experiencing issues with our external login provider (Auth0). Users that try to login via SSO may experience an error while trying to login with external credentials.
Our development team is currently investigating this issue and trying to get this resolved as quickly as possible. We will update the status page once we have more information.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2022-05-04T13:15:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Issues with the database servers (resolved)]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/238/"></link>
            <id>https://status.nedap-retail.com/incident/238/</id>
            <summary type="html"><![CDATA[<p>The issues with the database servers have been resolved. Our team will keep watching all applications closely and make sure all works accordingly.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2022-04-26T09:45:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Issues with the database servers (monitoring)]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/237/"></link>
            <id>https://status.nedap-retail.com/incident/237/</id>
            <summary type="html"><![CDATA[<p>Our database servers are returning back to normal. Our technical team will closely monitor the databases and applications the upcoming time.
It can take some time for the applications to catch-up on the historic traffic, but in a short time all application should be caught up again.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2022-04-26T09:35:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Issues with the database servers (investigating)]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/236/"></link>
            <id>https://status.nedap-retail.com/incident/236/</id>
            <summary type="html"><![CDATA[<p>We are currently experiencing issues with our database servers. Our technical team is currently investigating these issues. As soon as we know more, we will place an update on this page.</p>
<p>We apologize for any inconvenience caused.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2022-04-26T09:10:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[iD Cloud Web service disruption (resolved)]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/235/"></link>
            <id>https://status.nedap-retail.com/incident/235/</id>
            <summary type="html"><![CDATA[<p>The iD Cloud service disruption has been resolved.
Our development team will keep monitoring the situation.
We apologize for any inconvenience caused.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2022-03-30T10:36:02+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[iD Cloud Web service disruption]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/234/"></link>
            <id>https://status.nedap-retail.com/incident/234/</id>
            <summary type="html"><![CDATA[<p>We are currently experiencing a service disruption. iD Cloud pages might load slowly or not load at all.
Our development team is working to identify the root cause and implement a solution.</p>
<p>We will send an additional update when we have more information.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2022-03-30T10:22:18+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Nedap Retail EU service disruptions (resolved)]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/233/"></link>
            <id>https://status.nedap-retail.com/incident/233/</id>
            <summary type="html"><![CDATA[<p>The service disruptions for nedapretail.com have been resolved.
Our development team will keep monitoring the situation.
We apologize for any inconvenience caused.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2021-11-09T14:40:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Nedap Retail EU service disruptions]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/232/"></link>
            <id>https://status.nedap-retail.com/incident/232/</id>
            <summary type="html"><![CDATA[<p>We are currently experiencing service disruptions for the nedapretail.com. Pages and API's might load slowly.
Our development team is working to identify the root cause and implement a solution.</p>
<p>We will send an additional update when we have more information.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2021-11-09T13:45:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[iD Cloud service disruption (resolved)]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/231/"></link>
            <id>https://status.nedap-retail.com/incident/231/</id>
            <summary type="html"><![CDATA[<p>The iD Cloud service disruption has been resolved. Our development team will keep monitoring the situation.
We apologize for any inconvenience caused.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2021-10-28T13:20:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[iD Cloud service disruption]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/230/"></link>
            <id>https://status.nedap-retail.com/incident/230/</id>
            <summary type="html"><![CDATA[<p>We are currently experiencing a service disruption. iD Cloud Web and API's might load slowly or not load at all.
Our development team has identified the root cause and is looking for a solution.</p>
<p>We will send an additional update when we have more information.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2021-10-28T13:00:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[iD Cloud service disruption]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/229/"></link>
            <id>https://status.nedap-retail.com/incident/229/</id>
            <summary type="html"><![CDATA[<p>The iD Cloud service disruption have been resolved.
Our development team will keep monitoring the situation.
We apologize for any inconvenience caused.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2021-09-27T21:26:23+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[iD Cloud service disruption]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/228/"></link>
            <id>https://status.nedap-retail.com/incident/228/</id>
            <summary type="html"><![CDATA[<p>We are still investigating the data processing delays. iD Cloud functionality might load slowly or not load at all.
Our development team is working to identify the root cause and implement a solution.
We will send an additional update when we have more information.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2021-09-27T20:18:03+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Data Processing Delays]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/227/"></link>
            <id>https://status.nedap-retail.com/incident/227/</id>
            <summary type="html"><![CDATA[<p>Our development team is still working to identify the root cause and implement a solution.
As soon as we have more information we will post another update.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2021-09-27T19:04:20+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Data Processing Delays]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/226/"></link>
            <id>https://status.nedap-retail.com/incident/226/</id>
            <summary type="html"><![CDATA[<p>Our data processing infrastructure is running behind which is causing inaccuracies in the reporting tools. No data has been lost and the system should be caught up shortly.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2021-09-27T17:00:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Nedap Retail Analytics disruption]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/225/"></link>
            <id>https://status.nedap-retail.com/incident/225/</id>
            <summary type="html"><![CDATA[<p>We had a service disruption. Nedap Retail Analytics pages might have loaded slowly or not loaded at all.</p>
<p>Our development team has identify the root cause and resolved the issue.</p>
<p>As a result customers that are using the occupancy solution might see an error page. Reloading the page will resolve the issue.</p>
<p>We apologize for any inconvenience this might have caused you.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2021-09-10T12:20:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Email delivery is working again]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/224/"></link>
            <id>https://status.nedap-retail.com/incident/224/</id>
            <summary type="html"><![CDATA[<p>The external service has fixed the email delivery issues. They are now processing the backlog of emails that accumulated during their outage. Over the next couple of hours all scheduled emails from our online services will be delivered into your mailbox. We apologize for any inconvenience this might have caused you today.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2021-08-12T17:15:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Email delivery is delayed]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/223/"></link>
            <id>https://status.nedap-retail.com/incident/223/</id>
            <summary type="html"><![CDATA[<p>The external email service stated that they were able to fix the issues they were facing. They are now slowly bringing back online services, including transactional email delivery. Due to the backlog that was gathered during their outage, it can take a while before emails will get delivered. They should all get delivered automatically.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2021-08-12T15:00:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Email delivery is delayed]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/221/"></link>
            <id>https://status.nedap-retail.com/incident/221/</id>
            <summary type="html"><![CDATA[<p>The external service that sends out our transactional emails is still having issues. A core component in their networking system is down, and they are building a new one. The estimate the recovery time to be at least 2 hours.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2021-08-12T12:00:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Email delivery is delayed]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/220/"></link>
            <id>https://status.nedap-retail.com/incident/220/</id>
            <summary type="html"><![CDATA[<p>Unfortunately the external email service is still having issues. Therefore our email delivery from our services is still delayed.
Once the external email service is up and running again all scheduled emails will get delivered automatically.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2021-08-12T08:15:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Email delivery is delayed]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/219/"></link>
            <id>https://status.nedap-retail.com/incident/219/</id>
            <summary type="html"><![CDATA[<p>The external service that delivers our emails for reports and account details is currently encountering an outage. Due to this, the emails from our services are delayed.
Once the external service is up and running again, all emails will automatically be delivered.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2021-08-12T05:30:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Connection issues US iD Cloud servers resolved]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/218/"></link>
            <id>https://status.nedap-retail.com/incident/218/</id>
            <summary type="html"><![CDATA[<p>The connection issues to our iD Cloud US instance have been resolved. Our development team will keep monitoring the situation. We apologize for any inconvenience caused.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2021-07-30T21:55:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Connection issues to our US iD Cloud servers]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/217/"></link>
            <id>https://status.nedap-retail.com/incident/217/</id>
            <summary type="html"><![CDATA[<p>We are experiencing connection issues to some of our iD Cloud services on our US instance. This can cause some of our features not being able to connect to our servers. Our development team is investigating this and trying to resolve this as quickly as possible. We will place an update as soon as we know more.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2021-07-30T21:35:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Connection issues US iD Cloud servers resolved]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/216/"></link>
            <id>https://status.nedap-retail.com/incident/216/</id>
            <summary type="html"><![CDATA[<p>The connection issues to our iD Cloud US instance have been resolved. Our development team will keep monitoring the situation. We apologize for any inconvenience caused.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2021-07-30T20:00:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Connection issues to our US iD Cloud servers]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/215/"></link>
            <id>https://status.nedap-retail.com/incident/215/</id>
            <summary type="html"><![CDATA[<p>We are experiencing connection issues to some of our iD Cloud services on our US instance. This can cause some of our features not being able to connect to our servers. Our development team is investigating this and trying to resolve this as quickly as possible. We will place an update as soon as we know more.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2021-07-30T17:00:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Developer portal is available again]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/214/"></link>
            <id>https://status.nedap-retail.com/incident/214/</id>
            <summary type="html"><![CDATA[<p>After our third party vendor replaced the certificates on the developer portal it is now reachable again. We apologize for the inconvenience caused.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2021-07-02T17:35:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Developer portal not reachable]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/213/"></link>
            <id>https://status.nedap-retail.com/incident/213/</id>
            <summary type="html"><![CDATA[<p>Currently our developer portal is not reachable due to a certificate error. We are in close contact with the third party maintaining the portal to get this resolved as soon as possible.
If you need any !D Cloud API information in the meantime, please feel free to contact our support team so they can help you.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2021-07-02T13:25:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Infrastructure issues]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/209/"></link>
            <id>https://status.nedap-retail.com/incident/209/</id>
            <summary type="html"><![CDATA[<p>The issues with our infrastructure are resolved. Our technical team will closely monitor the environment to see if no other issues will occur.
We apologize for any inconvenience caused.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2021-06-24T20:55:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Infrastructure issues]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/208/"></link>
            <id>https://status.nedap-retail.com/incident/208/</id>
            <summary type="html"><![CDATA[<p>We are currently experiencing issues with our infrastructure. Our technical team is currently investigating these issues. As soon as we know more, we will place an update on this page.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2021-06-24T19:25:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Elevated API Errors]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/207/"></link>
            <id>https://status.nedap-retail.com/incident/207/</id>
            <summary type="html"><![CDATA[<p>All issues are resolved and data processing is returned to normal operation. We are very sorry for any inconvenience caused.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2021-05-17T08:30:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Elevated API Errors]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/206/"></link>
            <id>https://status.nedap-retail.com/incident/206/</id>
            <summary type="html"><![CDATA[<p>The issues are resolved and operations should resume to normal quickly.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2021-05-17T07:37:37+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Elevated API Errors]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/205/"></link>
            <id>https://status.nedap-retail.com/incident/205/</id>
            <summary type="html"><![CDATA[<p>The issue is identified and the developers are doing their best to fix the issue.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2021-05-17T07:05:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Elevated API Errors]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/204/"></link>
            <id>https://status.nedap-retail.com/incident/204/</id>
            <summary type="html"><![CDATA[<p>We are experiencing an elevated level of API errors and are currently investigating the issue.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2021-05-17T05:30:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Timeouts resolved]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/202/"></link>
            <id>https://status.nedap-retail.com/incident/202/</id>
            <summary type="html"><![CDATA[<p>We have found the cause of the timeouts and implemented a fix. We are very sorry for any inconvenience caused.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2021-05-16T23:30:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Network issues causing timeouts]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/201/"></link>
            <id>https://status.nedap-retail.com/incident/201/</id>
            <summary type="html"><![CDATA[<p>We are currently investigating timeouts in our infrastructure that seem to be related to network issues. You could experience performance issues or timeouts when using our applications.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2021-05-16T22:30:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[!D Cloud - delays and time outs have been resolved]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/200/"></link>
            <id>https://status.nedap-retail.com/incident/200/</id>
            <summary type="html"><![CDATA[<p>The technical team has identified the issue in !D Cloud that could cause delays or time outs in retrieving some of the !D Cloud data. They have resolved this issue now and all data is accessible again without error. No data has been lost during this period. We will keep monitoring the system closely. We apologize for any inconvenience caused.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2021-04-26T15:25:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[!D Cloud - delays and time outs in some !D Cloud features]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/199/"></link>
            <id>https://status.nedap-retail.com/incident/199/</id>
            <summary type="html"><![CDATA[<p>We noticed some delays and time outs in responses for some of our !D Cloud functionalities (for example retrieving a count or retrieving refill suggestions). Our technical team is currently investigating this and trying to resolve these issues quickly. We will keep you updated on this page.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2021-04-26T15:15:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Infrastructure issues]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/197/"></link>
            <id>https://status.nedap-retail.com/incident/197/</id>
            <summary type="html"><![CDATA[<p>The issues with our infrastructure are resolved. Our technical team will closely monitor the environment to see if no other issues will occur.</p>
<p>We apologize for any inconvenience caused.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2021-03-25T18:02:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Infrastructure issues]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/196/"></link>
            <id>https://status.nedap-retail.com/incident/196/</id>
            <summary type="html"><![CDATA[<p>We are currently experiencing issues with our infrastructure. Our technical team is currently investigating these issues. As soon as we know more, we will place an update on this page.</p>
<p>We apologize for any inconvenience caused.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2021-03-25T17:35:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[DNS issues have been resolved]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/195/"></link>
            <id>https://status.nedap-retail.com/incident/195/</id>
            <summary type="html"><![CDATA[<p>The DDOS attack at Transip (our DNS provider) has been mitigated and our Nedap Retail applications are reachable again. We will keep monitoring this closely and if there are any changes in the status we will update our page again.</p>
<p>Feel free to reach out to our support desks via the normal channels if you have additional questions. We are sorry for any inconvenience caused.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2021-03-22T15:15:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[!D Cloud impacted by DDOS attack on DNS provider]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/194/"></link>
            <id>https://status.nedap-retail.com/incident/194/</id>
            <summary type="html"><![CDATA[<p><strong>Update:</strong> the DNS provider Transip is still working hard to resolve the issues following the DDOS attack. Unfortunately we cannot provide a time line when all issues have been resolved, but as soon as they are, we will update our status page. Due to the issues it is possible that you are not able to reach !D Cloud web or use the !D Cloud app at the moment. Once the issues at Transip are resolved, all services will be reachable again.</p>
<p>Our DNS provider Transip is having issues due to a DDOS attack. They are working as fast as they can to resolve this issue. Due to this the reachability of our Nedap Retail applications can be interrupted (!D Cloud web, !D Cloud apps, Device Management, Analytics, Support portal and Cube).</p>
<p>For more updates on the issue, please also check the status page from Transip: https://www.transnoc.nl/</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2021-03-22T14:12:56+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[DNS provider is having issues]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/193/"></link>
            <id>https://status.nedap-retail.com/incident/193/</id>
            <summary type="html"><![CDATA[<p>Our DNS provider Transip is having issues due to a DDOS attack. They are working as fast as they can to resolve this issue.
Due to this the reachability of our Nedap Retail applications can be interrupted (!D Cloud web, !D Cloud apps, Device Management, Analytics, Support portal and Cube).</p>
<p>For more updates on the issue, please also check the status page from Transip: https://www.transnoc.nl/</p>
<p><strong>Update 15:00:</strong> Transip is still working on mitigating the DDOS attack. As soon as this is resolved, we will update our status page.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2021-03-22T12:30:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Scheduled maintenance on the support portal]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/192/"></link>
            <id>https://status.nedap-retail.com/incident/192/</id>
            <summary type="html"><![CDATA[<p>On <strong>Thursday 25 February 2021</strong> between <strong>13:00 and 16:00 CET</strong> we will perform scheduled maintenance to our support portal. We need to update the login methodology which may cause interruptions in the availability of the support portal during the scheduled time period.</p>
<p><strong>What is the impact of this maintenance?</strong>
During the scheduled time frame it is possible you will get login errors when trying to access the support portal. This will mostly impact users that frequently access the support portal for the knowledge base or for raising tickets. If you encounter a login error, please be patient and try again at a later time.</p>
<p><strong>Email and phone support will continue to work normally</strong>
You can still reach our support teams via email and phone. So if you need support urgently, feel free to contact us via the known email addresses and numbers.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2021-02-25T12:19:22+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Support portal back online]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/191/"></link>
            <id>https://status.nedap-retail.com/incident/191/</id>
            <summary type="html"><![CDATA[<p>We see that the support portal is getting back online. We will keep monitoring the situation and will place an update here once all issues have been resolved.
Apologies for the inconvenience.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2021-02-22T10:45:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Support portal currently not available]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/190/"></link>
            <id>https://status.nedap-retail.com/incident/190/</id>
            <summary type="html"><![CDATA[<p>Our support portal is currently not reachable. The external service provider is looking into the issue and hopefully this can be resolved quickly.
We will see your incoming tickets and are still reachable by phone. It can just take some time to be able to respond to these tickets and our !D Cloud knowledge base is unavailable at this moment. Feel free to reach out by phone if any immediate help is needed.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2021-02-22T10:25:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Scheduled maintenance on the support portal]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/189/"></link>
            <id>https://status.nedap-retail.com/incident/189/</id>
            <summary type="html"><![CDATA[<p>On <strong>Thursday 25 February 2021</strong> between <strong>13:00 and 16:00 CET</strong> we will perform scheduled maintenance to our support portal. We need to update the login methodology which may cause interruptions in the availability of the support portal during the scheduled time period.</p>
<p><strong>What is the impact of this maintenance?</strong>
During the scheduled time frame it is possible you will get login errors when trying to access the support portal. This will mostly impact users that frequently access the support portal for the knowledge base or for raising tickets. If you encounter a login error, please be patient and try again at a later time.</p>
<p><strong>Email and phone support will continue to work normally</strong>
You can still reach our support teams via email and phone. So if you need support urgently, feel free to contact us via the known email addresses and numbers.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2021-02-10T10:36:03+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Data processing has been restored]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/188/"></link>
            <id>https://status.nedap-retail.com/incident/188/</id>
            <summary type="html"><![CDATA[<p>Our data processing has been restored.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2021-02-04T16:32:41+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Data Processing Delays - Reporting Tools Affected]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/186/"></link>
            <id>https://status.nedap-retail.com/incident/186/</id>
            <summary type="html"><![CDATA[<p>Due to a short hiccup in our internal network our data processing infrastructure for OS/t systems is running behind which is causing inaccuracies in the reporting tools. No data has been lost and the system should be caught up shortly.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2021-02-04T14:20:19+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Data Processing Delays - Reporting Tools Affected]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/187/"></link>
            <id>https://status.nedap-retail.com/incident/187/</id>
            <summary type="html"><![CDATA[<p>Due to a short hiccup in our internal network our data processing infrastructure for OS/t systems is running behind which is causing inaccuracies in the reporting tools. No data has been lost and the system should be caught up shortly.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2021-02-04T14:00:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Some applications were affected by a delay in data processing]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/185/"></link>
            <id>https://status.nedap-retail.com/incident/185/</id>
            <summary type="html"><![CDATA[<p>For about 10 minutes some of our applications were responding slowly due to a delay in data processing. The affected applications were Analytics and !D Cloud web and possibly there were some slow calls on our APIs. We were directly alerted about the slowdown in data processing and the issue was quickly resolved. No data has been lost and all applications are running smoothly again. If you encountered any delays in this time frame we apologize for the inconvenience.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2021-01-25T12:27:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Data processing has been restored]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/184/"></link>
            <id>https://status.nedap-retail.com/incident/184/</id>
            <summary type="html"><![CDATA[<p>The solution has been deployed to our production environment. All reports from 01:00 AM will be delivered as normal. We will try to deliver all missed reports before noon GMT+1</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2020-12-14T00:05:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Data Processing Delays - Reporting Tools Affected]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/183/"></link>
            <id>https://status.nedap-retail.com/incident/183/</id>
            <summary type="html"><![CDATA[<p>The issue is identified. A solution to fix the reporting tools is currently implement.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2020-12-13T23:10:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Data Processing Delays - Reporting Tools Affected]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/182/"></link>
            <id>https://status.nedap-retail.com/incident/182/</id>
            <summary type="html"><![CDATA[<p>Our data processing infrastructure is having issues with our reporting infrastructure. As a result no reports are send via email or (s)ftp.
No data has been lost and reports will be delivered as soon as possible. Currently the team is working hard on finding a solution.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2020-12-13T20:00:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Data processing has been restored]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/181/"></link>
            <id>https://status.nedap-retail.com/incident/181/</id>
            <summary type="html"><![CDATA[<p>Our data processing has been restored and all delayed reports are processed.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2020-12-13T06:35:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Data processing has been restored]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/180/"></link>
            <id>https://status.nedap-retail.com/incident/180/</id>
            <summary type="html"><![CDATA[<p>Our data processing has been restored and our systems are up to date.
The team will monitor our systems closely to check all is working normally again.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2020-12-13T05:00:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Data Processing Delays - Reporting Tools Affected]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/178/"></link>
            <id>https://status.nedap-retail.com/incident/178/</id>
            <summary type="html"><![CDATA[<p>Our data processing infrastructure is running behind which is causing inaccuracies in the reporting tools. No data has been lost and the system should be caught up shortly. Changes towards cardholders are processed correctly.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2020-12-13T04:00:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Data Processing Delays - Reporting Tools Affected]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/179/"></link>
            <id>https://status.nedap-retail.com/incident/179/</id>
            <summary type="html"><![CDATA[<p>Our data processing infrastructure is running behind which is causing a delayed sending of email and (s)ftp reports for the Analytics platform. No data has been lost and the system should be caught up shortly.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2020-12-13T00:00:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Data processing has been restored]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/177/"></link>
            <id>https://status.nedap-retail.com/incident/177/</id>
            <summary type="html"><![CDATA[<p>Our data processing has been restored and our systems will catch up shortly.
The team will monitor our systems closely to check all is working normally again.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2020-12-07T17:05:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Data Processing Delays - Reporting Tools Affected]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/176/"></link>
            <id>https://status.nedap-retail.com/incident/176/</id>
            <summary type="html"><![CDATA[<p>Our data processing infrastructure for OS/t systems is running behind as a result of large data processing tasks. Which is causing inaccuracies in the reporting tools.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2020-12-07T14:00:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Network interruptions]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/175/"></link>
            <id>https://status.nedap-retail.com/incident/175/</id>
            <summary type="html"><![CDATA[<p>The DNS provider is stating that the DDOS attack is under control and that all domains should be reachable normally again. We keep monitoring the situation and if anything changes we will update you via our status page.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2020-12-01T09:45:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Network interruptions]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/174/"></link>
            <id>https://status.nedap-retail.com/incident/174/</id>
            <summary type="html"><![CDATA[<p>At the moment, one of the larger DNS providers in the Netherlands is being hindered by a DDOS attack. This affects internet traffic, so that websites are occasionally accessible or not. This also affects all Nedap Retail applications. Please try again at a later moment if you have trouble connecting to one of our services.
Unfortunately, we have no influence on this from our side. We are closely monitoring the situation and will update this post as more information is available.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2020-12-01T07:15:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Data processing has been restored]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/173/"></link>
            <id>https://status.nedap-retail.com/incident/173/</id>
            <summary type="html"><![CDATA[<p>Our data processing has been restored and our systems have processed all data again.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2020-09-30T10:59:18+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Data Processing Delays for OS/t - Reporting Tools Affected]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/172/"></link>
            <id>https://status.nedap-retail.com/incident/172/</id>
            <summary type="html"><![CDATA[<p>We have identified the problem with the OS/t data delivery. The root cause has been solved, all the data is currently processed and will be caught up shortly.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2020-09-30T08:42:41+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Data Processing Delays for OS/t - Reporting Tools Affected]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/171/"></link>
            <id>https://status.nedap-retail.com/incident/171/</id>
            <summary type="html"><![CDATA[<p>Our data processing infrastructure for OS/t systems is running behind which is causing inaccuracies in the reporting tools.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2020-09-30T08:33:37+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Maintenance window !D Cloud Tuesday 15 September 2020 11:00-15:00 CEST]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/170/"></link>
            <id>https://status.nedap-retail.com/incident/170/</id>
            <summary type="html"><![CDATA[<p>To implement improvements to our article database in !D Cloud we are announcing a maintenance window for our !D Cloud back-end servers on <strong>Tuesday 15 September 2020 between 11:00 - 15:00 CEST</strong>.</p>
<p><strong>What is the impact?</strong></p>
<p>During this maintenance window we will migrate our back-end processes which store and index article information in our system. Of course we try to limit the impact of this migration as much as possible.</p>
<p>During this migration there can be a delay in processing new or updated article information that is uploaded to !D Cloud. So if new article information is uploaded it is possible that this does not show directly. We don't expect a large impact, since most article upload processes are scheduled outside the chosen maintenance time frame.</p>
<p>All our other !D Cloud processes will work normally during this maintenance window. So for the stores this maintenance will not have any impact. They can still use the !D Cloud app normally and send and receive data to and from !D Cloud.</p>
<p>Once the maintenance window is finished, uploaded article information will be processed normally again and become available without any further delay.</p>
<p><strong>To summarize: during the maintenance window there can be a delay in processing new article information, all other processes will function normally.</strong></p>
<p>For any questions, please contact our <a href="mailto:support-idcloud@nedap.com">support department</a>.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2020-09-01T08:11:19+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Data processing has been restored]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/169/"></link>
            <id>https://status.nedap-retail.com/incident/169/</id>
            <summary type="html"><![CDATA[<p>Our data processing has been restored and our systems a showing up to date information.
The team will monitor our systems closely to check all is working normally again.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2020-07-22T06:05:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Data Processing Delays - Reporting Tools Affected]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/168/"></link>
            <id>https://status.nedap-retail.com/incident/168/</id>
            <summary type="html"><![CDATA[<p>Our data processing infrastructure is running behind which is causing inaccuracies in the reporting tools. No data has been lost and the system should be caught up shortly.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2020-07-22T05:19:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Data Processing Delays - Reporting Tools Affected]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/167/"></link>
            <id>https://status.nedap-retail.com/incident/167/</id>
            <summary type="html"><![CDATA[<p>Our data processing infrastructure is running behind which is causing inaccuracies in the reporting tools. No data has been lost and the system should be caught up shortly.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2020-07-22T00:00:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Data Processing Delays - Reporting Tools Affected]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/165/"></link>
            <id>https://status.nedap-retail.com/incident/165/</id>
            <summary type="html"><![CDATA[<p>Our data processing infrastructure is restored all data is processed. No data has been lost during the issue.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2020-07-13T13:45:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Data Processing Delays - Reporting Tools Affected]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/166/"></link>
            <id>https://status.nedap-retail.com/incident/166/</id>
            <summary type="html"><![CDATA[<p>Our data processing infrastructure is restored all data is processed. No data has been lost during the issue.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2020-07-13T13:30:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Data Processing Delays - Reporting Tools Affected]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/164/"></link>
            <id>https://status.nedap-retail.com/incident/164/</id>
            <summary type="html"><![CDATA[<p>Our data processing infrastructure is running behind which is causing inaccuracies in the system status of OS/t systems. No data has been lost and the system should be caught up shortly.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2020-07-13T11:22:18+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Data Processing Delays - Reporting Tools Affected]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/163/"></link>
            <id>https://status.nedap-retail.com/incident/163/</id>
            <summary type="html"><![CDATA[<p>Our data processing infrastructure is running behind which is causing inaccuracies in the system status of OS/t systems. No data has been lost and the system should be caught up shortly.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2020-07-13T11:21:26+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[!D Cloud server issues]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/162/"></link>
            <id>https://status.nedap-retail.com/incident/162/</id>
            <summary type="html"><![CDATA[<p>The server issues have been resolved and we see normal processing rates again. This means that !D Cloud web can be reached normally again. No data was lost during this period.</p>
<p>Our team will continue to monitor the situation to make sure all systems keep working normally. We apologize for any inconvenience caused.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2020-05-26T11:10:38+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[!D Cloud server issues]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/161/"></link>
            <id>https://status.nedap-retail.com/incident/161/</id>
            <summary type="html"><![CDATA[<p>Our development team is still working on the issues with our !D Cloud servers to get them fixed as soon as possible.</p>
<p>The issues may cause !D Cloud web to respond slowly and it is possible that a timeout occurs when loading a web page. We also see slow downs in retrieving ERP stock data in the app as well as !D Cloud web.
All data that is sent to !D Cloud will be processed normally, so no data will be lost. It is possible that the data becomes available with a slight delay due to the server issues.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2020-05-26T09:49:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[!D Cloud server issues]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/160/"></link>
            <id>https://status.nedap-retail.com/incident/160/</id>
            <summary type="html"><![CDATA[<p>We are currently having some issues with our servers. This might result in some parts of our !D Cloud application not being usable for stores.
We are investigating this issue and will keep you updated when we have more details</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2020-05-26T09:00:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[!D Cloud -  Maintenance scheduled for 27 May 2020]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/159/"></link>
            <id>https://status.nedap-retail.com/incident/159/</id>
            <summary type="html"><![CDATA[<p>We hope your are all doing well! Our !D Cloud development team has been quite busy the last couple of months and have been working on some improvements for our !D Cloud back-end. To implement these improvements we are announcing a maintenance window for our !D Cloud back-end servers on <strong>Wednesday 27 May 2020 between 08:00 - 17:00 CEST</strong>.</p>
<p><strong>What is the impact?</strong>
During this maintenance window we will migrate our back-end processes which store and index article information in our system. Of course we try to limit the impact of this migration as much as possible.</p>
<p>During the day each customer will be migrated to the new version. During this migration there can be a delay in processing new or updated article information that is uploaded to !D Cloud. So if new article information is uploaded it is possible that this does not show directly but with a delay with a maximum of an hour. This is due to the fact that the new system needs to setup new indexes for all customers.</p>
<p>Since most article information upload processes run during the night we don't expect a large impact during the scheduled maintenance time frame.</p>
<p>All our other !D Cloud processes will work normally during this maintenance window. So for the stores this maintenance will not have any impact. They can still use the !D Cloud app normally and send and receive data to and from !D Cloud.</p>
<p>Once the maintenance window is finished, uploaded article information will be processed normally again and become available without any delay.</p>
<p><strong>To summarize: during the maintenance window there can be a delay in processing new article information, all other processes will function normally.</strong></p>
<p>Please let us know if you have any questions or remarks regarding this e-mail via support-idcloud@nedap.com.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2020-05-11T11:58:26+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Elevated API Errors]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/158/"></link>
            <id>https://status.nedap-retail.com/incident/158/</id>
            <summary type="html"><![CDATA[<p>We have identified the issue in the article, shipment and searchlist API and put measures in place to fix the issue. Everything is now operational again.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2020-04-20T18:46:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Elevated API Errors]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/157/"></link>
            <id>https://status.nedap-retail.com/incident/157/</id>
            <summary type="html"><![CDATA[<p>We are experiencing an elevated level of API errors on the article and shipment APIs and are currently investigating the issue.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2020-04-20T17:25:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Scheduled maintenance (downtime expected)]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/156/"></link>
            <id>https://status.nedap-retail.com/incident/156/</id>
            <summary type="html"><![CDATA[<p>Between 09:00-14:00 CEST we will perform maintenance on our Easinet application. Though we try to keep the impact on our applications as small as possible, we do expect our applications to be offline for a short period of time within the maintenance window.</p>
<p>During the downtime of our applications, please be re-assured that no data will be lost and our applications will catch up quickly after the maintenance is finished.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2020-04-02T07:24:26+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Device Management portal not reachable]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/155/"></link>
            <id>https://status.nedap-retail.com/incident/155/</id>
            <summary type="html"><![CDATA[<p>All issues are resolved. The Device Management portal is working once more.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2020-03-18T07:32:51+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Device Management portal not reachable]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/154/"></link>
            <id>https://status.nedap-retail.com/incident/154/</id>
            <summary type="html"><![CDATA[<p>The device management portal is reachable again. We're currently monitoring the environment.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2020-03-18T07:00:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Device Management portal not reachable]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/153/"></link>
            <id>https://status.nedap-retail.com/incident/153/</id>
            <summary type="html"><![CDATA[<p>Currently we are having issues with our device management portal and it is temporary not reachable.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2020-03-18T05:15:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Issues with the database servers (resolved)]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/152/"></link>
            <id>https://status.nedap-retail.com/incident/152/</id>
            <summary type="html"><![CDATA[<p>The issues with the database servers have been resolved.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2020-02-20T08:49:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Issues with the database servers (investigating)]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/151/"></link>
            <id>https://status.nedap-retail.com/incident/151/</id>
            <summary type="html"><![CDATA[<p>We are currently experiencing issues with our database servers. Our technical team is currently investigating these issues. As soon as we know more, we will place an update on this page.</p>
<p>We apologize for any inconvenience caused.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2020-02-20T07:00:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Team Count is available again]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/150/"></link>
            <id>https://status.nedap-retail.com/incident/150/</id>
            <summary type="html"><![CDATA[<p>The development team has found the issue and implemented a fix. Stores will be able to use the count functionality in the !D Cloud app again.
We apologies for any inconvenience caused.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2020-01-30T14:14:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Team Count currently not working]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/149/"></link>
            <id>https://status.nedap-retail.com/incident/149/</id>
            <summary type="html"><![CDATA[<p>We are currently encountering issues with our Team Counting application. This causes issues for !D Cloud apps that are trying to perform a count in the store. These apps are currently not able to connect to !D Cloud and will see a connection error in their screen. Our development team is investigating the issue and is trying to resolve this as quickly as possible. We will update the status page as soon as we know more.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2020-01-30T14:00:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Developer Portal back online]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/148/"></link>
            <id>https://status.nedap-retail.com/incident/148/</id>
            <summary type="html"><![CDATA[<p>The certificate on the developer portal has been changed and it should be reachable again. Thanks you for your patience and apologies for the inconvenience caused.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2020-01-15T15:30:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Developer Portal not reachable]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/147/"></link>
            <id>https://status.nedap-retail.com/incident/147/</id>
            <summary type="html"><![CDATA[<p><strong>Update:</strong> a new certificate has been requested and installed for the developer portal. Unfortunately it takes some time for the internet to fully change to this new certificate. This will be within the next 24 hours, but hopefully it will be resolved quicker. As soon as the developer portal is available again, we will update our statuspage again.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2020-01-15T11:00:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Developer Portal not reachable]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/146/"></link>
            <id>https://status.nedap-retail.com/incident/146/</id>
            <summary type="html"><![CDATA[<p>Currently we are having issues with our developer portal and it is temporary not reachable. We are currently in contact with the external party to get this resolved a.s.a.p. If you have any questions about our APIs in the meantime, please don't hesitate to contact !D Cloud Support (support-idcloud@nedap.com).</p>
<p><strong>Update:</strong> The certificate used for the developer portal is expired and we are currently working on getting this renewed a.s.a.p. We will inform your once this is done and the developer portal is available again.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2020-01-15T08:30:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[!D Cloud performance issues]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/145/"></link>
            <id>https://status.nedap-retail.com/incident/145/</id>
            <summary type="html"><![CDATA[<p>The issues have been resolved and the performance has stabilized. We will keep monitoring this closely.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2020-01-10T11:30:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[!D Cloud performance issues]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/144/"></link>
            <id>https://status.nedap-retail.com/incident/144/</id>
            <summary type="html"><![CDATA[<p>The issue has been resolved as of now. We are closely monitoring the performance of !D Cloud.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2020-01-10T10:08:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[!D Cloud performance issues]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/143/"></link>
            <id>https://status.nedap-retail.com/incident/143/</id>
            <summary type="html"><![CDATA[<p>We are experiencing some performance issues in !D Cloud. This can result in some of our functionalities being slower than you are used from us.
Our team is working hard on identifying and resolving this issue asap. We apologize for any inconvenience caused.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2020-01-10T09:51:57+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Data Processing Delays - Reporting Tools Affected]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/142/"></link>
            <id>https://status.nedap-retail.com/incident/142/</id>
            <summary type="html"><![CDATA[<p>Email reports from Device Management were delivered with a delay. All reports were delivered this morning 08:00 (CET). We apologize for any inconvenience caused.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2019-12-20T03:00:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Emails are delivered normally again from Device Management]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/141/"></link>
            <id>https://status.nedap-retail.com/incident/141/</id>
            <summary type="html"><![CDATA[<p>The external email service is working properly again, so emails from Device Management are sent normally again.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2019-12-02T10:20:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Delays in email delivery from Device Management]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/140/"></link>
            <id>https://status.nedap-retail.com/incident/140/</id>
            <summary type="html"><![CDATA[<p>Emails sent from Device Management are currently delayed due to issues with our external email provider. Their team is working on it at this moment, hopefully they have this service up and running again shortly.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2019-12-02T08:00:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[EASiNet web environment currently not available]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/139/"></link>
            <id>https://status.nedap-retail.com/incident/139/</id>
            <summary type="html"><![CDATA[<p>Maintenance by our ISP is finished the EASiNet web environment can be reached again.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2019-11-20T19:00:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[EASiNet web environment currently not available]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/138/"></link>
            <id>https://status.nedap-retail.com/incident/138/</id>
            <summary type="html"><![CDATA[<p>Due to maintenance by our ISP the EASiNet web environment cannot be reached. All data is being processed normally and can be viewed within the Nedap Retail Analytics application. Once the maintenance by our ISP is finished the EASiNet websites will be visible again.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2019-11-08T07:00:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Performance issues - Resolved]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/137/"></link>
            <id>https://status.nedap-retail.com/incident/137/</id>
            <summary type="html"><![CDATA[<p>The issues on our servers have been resolved. We apologize for any inconvenience caused</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2019-11-04T17:27:40+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Performance issues, impact currently unknown]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/136/"></link>
            <id>https://status.nedap-retail.com/incident/136/</id>
            <summary type="html"><![CDATA[<p>We are currently experiencing some performance issues on our servers. We are investigating the impact.
We send updates once we have more information on this topic.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2019-11-04T16:45:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Server issues]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/135/"></link>
            <id>https://status.nedap-retail.com/incident/135/</id>
            <summary type="html"><![CDATA[<p>The server issues have been resolved. Our services are fully functional, no data was lost.
We apologize for any inconvenience caused.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2019-10-24T13:54:56+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Server issues]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/134/"></link>
            <id>https://status.nedap-retail.com/incident/134/</id>
            <summary type="html"><![CDATA[<p>Server issues and services are usable but we are still closely monitoring and investigating what went wrong.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2019-10-24T13:33:47+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Server issues]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/133/"></link>
            <id>https://status.nedap-retail.com/incident/133/</id>
            <summary type="html"><![CDATA[<p>We are currently experiencing issues which is causing some of our applications being unusable. We are investigating what is affected and are looking to resolve these issues asap.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2019-10-24T13:12:21+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Delayed processing on finished counts]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/132/"></link>
            <id>https://status.nedap-retail.com/incident/132/</id>
            <summary type="html"><![CDATA[<p>The issues with the count processing have been resolved. Finished counts should be available in !D Cloud web and via API as usual.
We apologize for any inconvenience caused.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2019-10-24T10:05:12+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Delayed processing on finished counts]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/131/"></link>
            <id>https://status.nedap-retail.com/incident/131/</id>
            <summary type="html"><![CDATA[<p>We are currently experiencing delayed processing of counts in !D Cloud web and API. It can take longer than usual before count results are available in !D Cloud web or via our API's.
Please note: Stores can continue counting as usual.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2019-10-24T09:00:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[!D Cloud server issues]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/130/"></link>
            <id>https://status.nedap-retail.com/incident/130/</id>
            <summary type="html"><![CDATA[<p>The server issues we experienced with !D Cloud have been resolved. All functionalities are fully functional.
We once again apologize for any inconvenience caused. If you still experience issues, please contact support-idcloud@nedap.com.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2019-10-08T12:24:17+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[!D Cloud server issues]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/128/"></link>
            <id>https://status.nedap-retail.com/incident/128/</id>
            <summary type="html"><![CDATA[<p>We are currently having some issues with our servers. This might result in some parts of our !D Cloud application not being usable for stores.
We are investigating this issue and will keep you updated when we have more details</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2019-10-08T08:20:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[!D Cloud Server issues]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/129/"></link>
            <id>https://status.nedap-retail.com/incident/129/</id>
            <summary type="html"><![CDATA[<p>We are still experiencing major issues on our !D Cloud servers. Since we are investigating the exact impact we advise our customers to refrain from using !D Cloud until further notice.
We apologize for any inconvenience caused.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2019-10-08T08:20:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Issue processing !D Cloud counts(Resolved)]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/127/"></link>
            <id>https://status.nedap-retail.com/incident/127/</id>
            <summary type="html"><![CDATA[<p>The issues with processing finished counts has been resolved. Counts should now be visible as usual in !D Cloud web.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2019-08-29T09:48:35+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Issue processing !D Cloud counts]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/126/"></link>
            <id>https://status.nedap-retail.com/incident/126/</id>
            <summary type="html"><![CDATA[<p>Since 11:00 CEST we are having an issues processing counts which are sent via the app to !D Cloud. This causes a delay in finished counts showing up on !D Cloud web.
The counts are stored and will be visible once this issue is resolved, no data is lost. We apologize for any inconvenience caused.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2019-08-29T09:00:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Scheduled maintenance is finished]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/125/"></link>
            <id>https://status.nedap-retail.com/incident/125/</id>
            <summary type="html"><![CDATA[<p>Our scheduled maintenance is finished and our database servers are updated successfully. All our Nedap Retail services are working normally again.
During the maintenance no data was lost and all data processing is resumed to normal.</p>
<p>Thank you for your patience and apologies for the inconvenience.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2019-08-22T21:22:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Scheduled maintenance has started]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/124/"></link>
            <id>https://status.nedap-retail.com/incident/124/</id>
            <summary type="html"><![CDATA[<p>Our scheduled maintenance on our database servers has started. This means that you may experience interruptions in your connection to our Nedap Retail applications. We try to keep the interruptions as shortly as possible, but please note that the downtime may occur between now and 24:00 hours this evening. Once the maintenance is finished we will update the statuspage again and send an email to confirm the maintenance is done.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2019-08-22T17:20:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Scheduled maintenance (downtime expected)]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/123/"></link>
            <id>https://status.nedap-retail.com/incident/123/</id>
            <summary type="html"><![CDATA[<p>Tonight between 19:00-24:00 CEST we will perform our scheduled maintenance on our database servers. We will upgrade our database servers to make our applications more reliable and scalable for the future. Though we try to keep the impact on our applications as small as possible, we do expect downtime during this maintenance window.</p>
<p>We will perform several upgrades during this evening. This will cause multiple offline periods for our applications, causing the applications to be unavailable for a short time. The affected applications are: Device Management, Analytics, !D Cloud, Cube, EasiNet, Developer Portal and Support Portal. When an application is unavailable, it will not be reachable via web, app or API during that period. It is possible that multiple applications are offline at the same time during the maintenance window.</p>
<p>During the downtime of our applications, please be assured that no data will be lost and our applications will catch up quickly after the maintenance is finished.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2019-08-22T17:00:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Data processing has been restored - !D Cloud SFTP]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/122/"></link>
            <id>https://status.nedap-retail.com/incident/122/</id>
            <summary type="html"><![CDATA[<p>Our data processing on the !D Cloud SFTP has been restored to normal and our systems will catch up shortly.
The team will monitor our systems closely to check all is working normally again.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2019-08-21T08:45:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Data Processing Delays - !D Cloud SFTP]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/121/"></link>
            <id>https://status.nedap-retail.com/incident/121/</id>
            <summary type="html"><![CDATA[<p>Our data processing on our SFTP servers is running behind. Our technical team is currently implementing a fix and afterwards the data processing will return to normal.  No data has been lost and the system should be caught up shortly, we expect it to take about an hour to catch up.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2019-08-21T06:15:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Cube controllers - Authorization changes delayed]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/120/"></link>
            <id>https://status.nedap-retail.com/incident/120/</id>
            <summary type="html"><![CDATA[<p>Our data processing infrastructure is running behind which is causing a delay in changes for card authorisations .  As a result of the delay it will take longer before a new card will be activated within the store. No data will be lost..</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2019-08-18T06:00:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Cube controller issues]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/119/"></link>
            <id>https://status.nedap-retail.com/incident/119/</id>
            <summary type="html"><![CDATA[<p>The issue with the controller connectivity is identified and a fix is in place. All authorizations and events are currently synchronized.
We will continue to monitor the environment to see if all issues are resolved.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2019-08-14T12:00:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Cube controller issues]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/118/"></link>
            <id>https://status.nedap-retail.com/incident/118/</id>
            <summary type="html"><![CDATA[<p>We are currently having issues with some of the Cube controllers since 09:00 AM CEST. In some situations the access control system can have issues with authorisations for opening doors.
We are working hard to resolve this is as soon as possible.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2019-08-14T07:00:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[!D Cloud web issues in Internet Explorer(Resolved)]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/117/"></link>
            <id>https://status.nedap-retail.com/incident/117/</id>
            <summary type="html"><![CDATA[<p>The functionalities of !D Cloud web in Internet Explorer have been resolved</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2019-08-01T07:51:35+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[!D Cloud web issues in Internet Explorer]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/116/"></link>
            <id>https://status.nedap-retail.com/incident/116/</id>
            <summary type="html"><![CDATA[<p>Some parts of !D Cloud web are currently not correctly displayed and usable for Internet Explorer users.
We are working hard to resolve this issue. As a temporary workaround other browsers can be used.</p>
<p>We apologize for any inconvenience caused</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2019-07-31T13:28:03+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Scheduled maintenance on our database servers - 22 August 2019]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/115/"></link>
            <id>https://status.nedap-retail.com/incident/115/</id>
            <summary type="html"><![CDATA[<p>On <strong>Thursday 22 August 2019</strong> between <strong>19:00-24:00 CEST</strong> we will perform maintenance on our database servers. We will upgrade our database servers to make our applications more reliable and scalable for the future.
Though we try to keep the impact on our applications as small as possible, we do expect downtime during this maintenance window.</p>
<p>We will perform several upgrades during this evening. This will cause multiple offline periods for our applications, causing the applications to be unavailable for a short time. The affected applications are: Device Management, Analytics, !D Cloud, Cube, EasiNet, Developer Portal and Support Portal. When an application is unavailable, it will not be reachable via web, app or API during that period. It is possible that multiple applications are offline at the same time during the maintenance window.</p>
<p>During the downtime of our applications, please be assured that no data will be lost and our applications will catch up quickly after the maintenance is finished.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2019-07-18T11:28:32+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Scheduled maintenance (no downtime expected) for EASiNet]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/114/"></link>
            <id>https://status.nedap-retail.com/incident/114/</id>
            <summary type="html"><![CDATA[<p>Tonight between 19:00-21:00 CEST we will perform maintenance on our EASiNet data centers. Of course we try to keep the impact as minimal as possible. We don't expect any downtime, but during the maintenance window we do expect some slow downs in data processing. If this occurs, please be re-assured that no data will be lost and our applications will catch up quickly after the maintenance is finished.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2019-06-18T14:06:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Scheduled maintenance for our SSO applications]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/113/"></link>
            <id>https://status.nedap-retail.com/incident/113/</id>
            <summary type="html"><![CDATA[<p>On Wednesday 12 June 2019 around 14:00 hours CEST we need to perform some maintenance on our SSO applications. We expect this maintenance to take a maximum of 15 minutes. During this maintenance window it will not be possible to login to our !D Cloud Support Portal and our !D Cloud Developer Portal. It is possible that users trying to login in one of the two portals receive an error notification.</p>
<p>All our other web applications, like Analytics, !D Cloud, Cube and Device Management, will still be available in this maintenance window. Our support desk is still reachable via phone and email.</p>
<p>After the maintenance window both SSO applications will be available again.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2019-06-11T14:05:08+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Search list API back online]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/112/"></link>
            <id>https://status.nedap-retail.com/incident/112/</id>
            <summary type="html"><![CDATA[<p>The search list APIs are available again. We are sorry for any inconvenience this may have caused.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2019-05-29T11:18:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Search list API temporarily unavailable]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/111/"></link>
            <id>https://status.nedap-retail.com/incident/111/</id>
            <summary type="html"><![CDATA[<p>The search list APIs are temporarily unavailable. All other APIs are functioning as normal.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2019-05-29T11:05:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Performance issues]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/110/"></link>
            <id>https://status.nedap-retail.com/incident/110/</id>
            <summary type="html"><![CDATA[<p>Performance issues in our web applications are resolved.
Please note that no data is lost. We apologise for any inconvenience caused.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2019-05-08T10:25:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Elevated API Errors - resolved]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/108/"></link>
            <id>https://status.nedap-retail.com/incident/108/</id>
            <summary type="html"><![CDATA[<p>The source of the API errors have been identified and mitigated.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2019-05-08T08:26:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Performance issues]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/109/"></link>
            <id>https://status.nedap-retail.com/incident/109/</id>
            <summary type="html"><![CDATA[<p>We are currently experiencing some performance issues in our web applications, some requests are not correctly handled and could return an error. If you experience any issues, please try to refresh the page.
Please note that no data will be lost. We apologise for any inconvenience caused.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2019-05-08T08:20:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Elevated API Errors]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/107/"></link>
            <id>https://status.nedap-retail.com/incident/107/</id>
            <summary type="html"><![CDATA[<p>We are experiencing an elevated level of API errors and are currently investigating the issue.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2019-05-08T08:10:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Issues with the database servers resolved (resolved)]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/106/"></link>
            <id>https://status.nedap-retail.com/incident/106/</id>
            <summary type="html"><![CDATA[<p>The performance issues with our database servers are resolved. Our technical team will closely monitor the databases and applications the upcoming time.
It can take some time for the applications to catch-up on the historic traffic, but in a short time all application should be caught up again.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2019-05-03T08:28:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Issues with the database servers (solving)]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/105/"></link>
            <id>https://status.nedap-retail.com/incident/105/</id>
            <summary type="html"><![CDATA[<p>We are currently experiencing performance issues with our database servers. Our technical team is working on a solution now. You could experience some slowdowns or degraded performance of our applications. Please try again if this occurs.</p>
<p>We apologize for any inconvenience caused and will update you as soon as everything is operational again.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2019-05-03T07:50:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[!D Cloud web performance issues]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/104/"></link>
            <id>https://status.nedap-retail.com/incident/104/</id>
            <summary type="html"><![CDATA[<p>The issue has been fixed, everything is operational again.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2019-04-16T07:10:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[!D Cloud web performance issues]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/103/"></link>
            <id>https://status.nedap-retail.com/incident/103/</id>
            <summary type="html"><![CDATA[<p>We see performance issues within our !D Cloud web environment. At the moment we are investigating the issue.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2019-04-16T06:55:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Cube controller connectivity]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/102/"></link>
            <id>https://status.nedap-retail.com/incident/102/</id>
            <summary type="html"><![CDATA[<p>All issues with the connectivity of Cube controllers are fixed. No data is lost during the inactivity.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2019-04-02T04:46:30+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Cube controller connectivity]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/101/"></link>
            <id>https://status.nedap-retail.com/incident/101/</id>
            <summary type="html"><![CDATA[<p>The issue with the controller connectivity is identified and a fix is in place. All authorisations and events are currently synchronised. No data is lost.
We will continue to monitor the environment to see if all issues are resolved.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2019-04-01T17:43:08+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Cube controller connectivity]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/100/"></link>
            <id>https://status.nedap-retail.com/incident/100/</id>
            <summary type="html"><![CDATA[<p>We are currently having issue with the connectivity of Cube controllers which is causing events and authorizations to be delayed.
At the moment we are investigating the cause of the delays.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2019-04-01T10:48:39+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[sFTP timeout issues]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/99/"></link>
            <id>https://status.nedap-retail.com/incident/99/</id>
            <summary type="html"><![CDATA[<p>We have experienced some timeout issues on our sFTP server between 1:25 and 7:00 CET. The issue has now been resolved.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2019-03-30T08:38:53+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Data processing has been restored]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/98/"></link>
            <id>https://status.nedap-retail.com/incident/98/</id>
            <summary type="html"><![CDATA[<p>Our data processing has been restored and our systems will catch up shortly.
The team will monitor our systems closely to check all is working normally again.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2019-02-05T15:46:29+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Data Processing Delays - Reporting Tools Affected]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/96/"></link>
            <id>https://status.nedap-retail.com/incident/96/</id>
            <summary type="html"><![CDATA[<p>Our data processing infrastructure is running behind which is causing inaccuracies in the reporting tools. No data has been lost. We are investigating the cause of the delays.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2019-02-05T10:50:24+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Data Processing Delays - EPCIS events]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/97/"></link>
            <id>https://status.nedap-retail.com/incident/97/</id>
            <summary type="html"><![CDATA[<p>Our data processing infrastructure is running behind which is causing a delay in processing EPCIS events. These events may contain count data and POS data (sold / unsold events). Our team is working on getting the data processing back on track.
No data has been lost and the system should be caught up shortly.</p>
<p><em>As a precaution we have silenced our !D Cloud EAS, to prevent false alarms in the stores.</em></p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2019-02-05T10:00:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Maintenance EASiNet servers finished]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/95/"></link>
            <id>https://status.nedap-retail.com/incident/95/</id>
            <summary type="html"><![CDATA[<p>The maintenance on our EASiNet servers has finished. All data will be processed again and our applications will be caught up shortly.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2019-01-25T10:13:36+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Unexpected maintenance EASiNet servers]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/94/"></link>
            <id>https://status.nedap-retail.com/incident/94/</id>
            <summary type="html"><![CDATA[<p>Due to unexpected maintenance to our EASiNet servers, our EASiNet platform will be offline this morning. We expect our servers to be offline for approximately 1 hour as of <strong>10:30 hours CET</strong>.</p>
<p><strong>Please note:</strong> If the maintenance exceeds 1 hour, OS/t systems can be marked offline in Device Management. In this case it is possible you receive notifications, if these have been configured. After the maintenance is finished, the status of these devices will be corrected.</p>
<p>During the downtime of our application, please be re-assured that no data will be lost and our applications will catch up quickly after the maintenance is finished.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2019-01-25T08:26:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Scheduled maintenance on our data centers on Wednesday 16 January 2019]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/92/"></link>
            <id>https://status.nedap-retail.com/incident/92/</id>
            <summary type="html"><![CDATA[<p><strong>Update 15:09 CET:</strong> Our scheduled maintenance has been finished and all our online applications are back online!</p>
<p>At Nedap Retail we always strive to have our online services up to the latest standards and we keep developing to have a scalable, stable and secure online environment for our customers to use.</p>
<p>Therefore on <strong>Wednesday 16 January 2019 between 15:00-16:00 CET</strong> we will perform maintenance on our data centers. Though we try to keep the impact on our applications as small as possible, we do expect our applications to be offline for a short period of time within the maintenance window.</p>
<p>During the downtime of our applications, please be re-assured that no data will be lost and our applications will catch up quickly after the maintenance is finished. We apologize for any inconvenience caused.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2019-01-11T09:07:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Resolved]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/91/"></link>
            <id>https://status.nedap-retail.com/incident/91/</id>
            <summary type="html"><![CDATA[<p>Everything is back up again.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2018-12-22T16:25:32+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Database back up again]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/90/"></link>
            <id>https://status.nedap-retail.com/incident/90/</id>
            <summary type="html"><![CDATA[<p>Database is back up again. We are currently still monitoring the applications and database.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2018-12-22T14:12:22+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Problems with the Database server]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/89/"></link>
            <id>https://status.nedap-retail.com/incident/89/</id>
            <summary type="html"><![CDATA[<p>We are currently implementing a temporary solution to get the database back up again.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2018-12-22T13:05:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Performance issues with external login provider Auth0]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/87/"></link>
            <id>https://status.nedap-retail.com/incident/87/</id>
            <summary type="html"><![CDATA[<p>Our external login provider 'Auth0' is having  performance issues. We have raised an issue with this provider to get these issues sorted.</p>
<p>Only a small percentages of the login attempts fail, if you get an error message, please try again until you get through.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2018-11-08T09:20:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Servers not reachable]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/86/"></link>
            <id>https://status.nedap-retail.com/incident/86/</id>
            <summary type="html"><![CDATA[<p>This morning our servers were not reachable for two minutes. The issue has been resolved. We are sorry for any inconvenience caused.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2018-10-24T08:03:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[EASiNet not reachable]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/85/"></link>
            <id>https://status.nedap-retail.com/incident/85/</id>
            <summary type="html"><![CDATA[<p>The server issues have been solved and our EASiNet application is reachable again.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2018-09-18T08:10:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[EASiNet not reachable]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/84/"></link>
            <id>https://status.nedap-retail.com/incident/84/</id>
            <summary type="html"><![CDATA[<p>We are experiencing server issues with our EASiNet application. We are currently investigating the cause and will keep you posted.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2018-09-18T06:00:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Servers not reachable]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/83/"></link>
            <id>https://status.nedap-retail.com/incident/83/</id>
            <summary type="html"><![CDATA[<p>During the deployment of our application an error occurred, which resulted in the application not being able to start up again. This caused the servers to be unreachable for a short amount of time. We are currently reviewing and improving the deployment process to prevent this from happening again in the future.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2018-08-16T14:19:38+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Servers not reachable]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/82/"></link>
            <id>https://status.nedap-retail.com/incident/82/</id>
            <summary type="html"><![CDATA[<p>Our servers are reachable again, it was a very short interruption in our services (2 minutes). We are still investigating the root cause of the issue.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2018-08-16T14:11:29+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Servers not reachable]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/81/"></link>
            <id>https://status.nedap-retail.com/incident/81/</id>
            <summary type="html"><![CDATA[<p>We see that our servers are not reachable at the moment. Our team is investigating the issue and we will update the status page as soon as we know more.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2018-08-16T14:06:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Slow performance]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/80/"></link>
            <id>https://status.nedap-retail.com/incident/80/</id>
            <summary type="html"><![CDATA[<p>The source of the performance issues has been identified and mitigated. Performance levels are back to normal. We have monitored the fix and will keep monitoring further.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2018-07-31T10:23:23+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Slow performance]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/79/"></link>
            <id>https://status.nedap-retail.com/incident/79/</id>
            <summary type="html"><![CDATA[<p>The source of the performance issues has been identified and mitigated. Performance levels are back to normal. We will keep monitoring the issue.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2018-07-31T09:59:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Slow performance]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/78/"></link>
            <id>https://status.nedap-retail.com/incident/78/</id>
            <summary type="html"><![CDATA[<p>One of our databases in under heavy load at the moment. You may experience slower performance than you may expect from us. We are sorry for any inconvenience that this may cause.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2018-07-31T09:44:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Degraded performance of all our applications]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/77/"></link>
            <id>https://status.nedap-retail.com/incident/77/</id>
            <summary type="html"><![CDATA[<p>Due to hardware maintenance in our data center, we encountered degraded performance on our applications. Customer impact was minimal and no data has been lost. We will implement improvements to prevent this from happening in the future.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2018-06-26T22:03:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Degraded performance of all our applications]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/76/"></link>
            <id>https://status.nedap-retail.com/incident/76/</id>
            <summary type="html"><![CDATA[<p>Due to hardware maintenance in our data center, we encounter degraded performance on our applications. We are investigating the issue.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2018-06-26T21:10:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Slow performance]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/75/"></link>
            <id>https://status.nedap-retail.com/incident/75/</id>
            <summary type="html"><![CDATA[<p>The source of the performance issues has been identified and mitigated. Performance levels are back to normal.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2018-06-26T09:00:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Slow performance]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/74/"></link>
            <id>https://status.nedap-retail.com/incident/74/</id>
            <summary type="html"><![CDATA[<p>One of our databases in under heavy load at the moment. You may experience slower performance than you may expect from us. We are sorry for any inconvenience that this may cause.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2018-06-26T08:40:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Data Processing Delays for customer counting and alarm data]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/17/"></link>
            <id>https://status.nedap-retail.com/incident/17/</id>
            <summary type="html"><![CDATA[<p>All data processing is restored.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2018-04-12T10:06:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Data Processing Delays for customer counting and alarm data]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/15/"></link>
            <id>https://status.nedap-retail.com/incident/15/</id>
            <summary type="html"><![CDATA[<p>At the moment data processing for customer counting and alarm data can be delayed.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2018-04-12T10:03:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Nedap Retail services down]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/19/"></link>
            <id>https://status.nedap-retail.com/incident/19/</id>
            <summary type="html"><![CDATA[<p>This incident has been resolved.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2018-01-28T08:48:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Nedap Retail services down]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/18/"></link>
            <id>https://status.nedap-retail.com/incident/18/</id>
            <summary type="html"><![CDATA[<p>We are currently experiencing network connectivity issues. Most Nedap Retail services are currently slow or not available. We are investigating the problems and will update this status page as soon as we have more information.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2018-01-28T01:34:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[All Nedap Retail services are down]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/24/"></link>
            <id>https://status.nedap-retail.com/incident/24/</id>
            <summary type="html"><![CDATA[<p>This incident has been resolved.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2017-12-18T21:06:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[All Nedap Retail services are down]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/23/"></link>
            <id>https://status.nedap-retail.com/incident/23/</id>
            <summary type="html"><![CDATA[<p>All services are up again. We are monitoring the situation.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2017-12-18T18:38:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[All Nedap Retail services are down]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/22/"></link>
            <id>https://status.nedap-retail.com/incident/22/</id>
            <summary type="html"><![CDATA[<p>The cause of the outage has been found and we are working on bringing back our services one at a time.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2017-12-18T17:59:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[All Nedap Retail services are down]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/21/"></link>
            <id>https://status.nedap-retail.com/incident/21/</id>
            <summary type="html"><![CDATA[<p>Currently all Nedap Retail services are down. We know there is an issue in the data connection between our data centres in Zwolle and Enschede, and we will update you as soon as we have more information.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2017-12-18T16:32:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[All Nedap Retail services are down]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/20/"></link>
            <id>https://status.nedap-retail.com/incident/20/</id>
            <summary type="html"><![CDATA[<p>Due to network issues our data processing infrastructure is running behind which is causing inaccuracies in the reporting tools and our web applications might respond slowly. No data has been lost and the system should be caught up shortly.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2017-12-18T15:02:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Timeouts]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/27/"></link>
            <id>https://status.nedap-retail.com/incident/27/</id>
            <summary type="html"><![CDATA[<p>Everything is back to normal.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2017-11-01T15:49:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Timeouts]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/26/"></link>
            <id>https://status.nedap-retail.com/incident/26/</id>
            <summary type="html"><![CDATA[<p>There was a peak load on one of our applications. We manually diverted the load to other servers.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2017-11-01T15:33:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Timeouts]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/25/"></link>
            <id>https://status.nedap-retail.com/incident/25/</id>
            <summary type="html"><![CDATA[<p>We are seeing timeouts in our applications, we are investigating.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2017-11-01T15:10:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Partial outage of web applications]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/31/"></link>
            <id>https://status.nedap-retail.com/incident/31/</id>
            <summary type="html"><![CDATA[<p>All applications are back online and are performing normally again.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2017-08-23T15:01:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Partial outage of web applications]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/30/"></link>
            <id>https://status.nedap-retail.com/incident/30/</id>
            <summary type="html"><![CDATA[<p>Our applications are currently back online and we are monitoring their performance.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2017-08-23T14:54:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Partial outage of web applications]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/29/"></link>
            <id>https://status.nedap-retail.com/incident/29/</id>
            <summary type="html"><![CDATA[<p>Due to problems with one of the servers in our infrastructure, the !D Cloud (including its API's), Cube and Analytics web applications are responding very slowly or not at all. Device Management is currently unaffected by this issue.
We are trying to restart the server, to get it up and running normally again.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2017-08-23T14:26:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Partial outage of web applications]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/28/"></link>
            <id>https://status.nedap-retail.com/incident/28/</id>
            <summary type="html"><![CDATA[<p>We are experiencing elevated levels of errors in our API's and web applications (including Device Management, Analytics and Cube). We are currently looking into the issue.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2017-08-23T14:06:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Data Processing Delays]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/49/"></link>
            <id>https://status.nedap-retail.com/incident/49/</id>
            <summary type="html"><![CDATA[<p>Data processing is back to normal.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2017-08-11T16:13:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Data Processing Delays]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/48/"></link>
            <id>https://status.nedap-retail.com/incident/48/</id>
            <summary type="html"><![CDATA[<p>Data processing has started again and the issue is resolved. We will monitor the data processing in the upcoming hours.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2017-08-11T15:50:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Data Processing Delays]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/47/"></link>
            <id>https://status.nedap-retail.com/incident/47/</id>
            <summary type="html"><![CDATA[<p>Data processing has partially been restored. Still analyzing the root cause.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2017-08-11T15:33:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Data Processing Delays]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/46/"></link>
            <id>https://status.nedap-retail.com/incident/46/</id>
            <summary type="html"><![CDATA[<p>Our data processing infrastructure is running behind. No data has been lost and the system should be caught up shortly.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2017-08-11T13:19:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Data Processing Delays]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/44/"></link>
            <id>https://status.nedap-retail.com/incident/44/</id>
            <summary type="html"><![CDATA[<p>Our data processing infrastructure is running behind. No data has been lost and the system should be caught up shortly.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2017-07-12T09:26:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Data Processing Delays]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/45/"></link>
            <id>https://status.nedap-retail.com/incident/45/</id>
            <summary type="html"><![CDATA[<p>This incident has been resolved.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2017-07-12T09:26:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Data Processing Delays]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/43/"></link>
            <id>https://status.nedap-retail.com/incident/43/</id>
            <summary type="html"><![CDATA[<p>This incident has been resolved.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2017-07-08T16:13:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Data Processing Delays]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/42/"></link>
            <id>https://status.nedap-retail.com/incident/42/</id>
            <summary type="html"><![CDATA[<p>The issue has been identified and a fix is being implemented.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2017-07-08T07:31:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Data Processing Delays]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/41/"></link>
            <id>https://status.nedap-retail.com/incident/41/</id>
            <summary type="html"><![CDATA[<p>We are currently investigating this issue.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2017-07-08T07:18:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Data Processing Delays]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/40/"></link>
            <id>https://status.nedap-retail.com/incident/40/</id>
            <summary type="html"><![CDATA[<p>This incident has been resolved.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2017-06-09T20:28:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Data Processing Delays]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/39/"></link>
            <id>https://status.nedap-retail.com/incident/39/</id>
            <summary type="html"><![CDATA[<p>Our data processing infrastructure is running behind. No data has been lost and the system should be caught up shortly.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2017-06-09T13:50:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Error 500s on !D Cloud web]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/38/"></link>
            <id>https://status.nedap-retail.com/incident/38/</id>
            <summary type="html"><![CDATA[<p>The network issue is resolved and the traffic is routed to both datacenters again.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2017-05-31T13:57:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Error 500s on !D Cloud web]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/37/"></link>
            <id>https://status.nedap-retail.com/incident/37/</id>
            <summary type="html"><![CDATA[<p>There seems to be a networking issues in one of our data-centers, which resulted in errors on !D Cloud web for about 33% of the requests. Our network engineers are working on the issue. In the meantime we have re-routed traffic to the other data center.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2017-05-31T13:52:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Error 500s on !D Cloud web]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/36/"></link>
            <id>https://status.nedap-retail.com/incident/36/</id>
            <summary type="html"><![CDATA[<p>We are currently investigating this issue.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2017-05-31T13:43:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Data Processing Delays - Reporting Tools Affected]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/35/"></link>
            <id>https://status.nedap-retail.com/incident/35/</id>
            <summary type="html"><![CDATA[<p>This incident has been resolved.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2017-05-17T14:04:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Data Processing Delays - Reporting Tools Affected]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/34/"></link>
            <id>https://status.nedap-retail.com/incident/34/</id>
            <summary type="html"><![CDATA[<p>Our data processing infrastructure is running behind which is causing inaccuracies in the reporting tools. No data has been lost and the system should catch up shortly.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2017-05-17T12:26:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Data Processing Delays - Cube Authorizations Affected]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/33/"></link>
            <id>https://status.nedap-retail.com/incident/33/</id>
            <summary type="html"><![CDATA[<p>Processing is back to normal.
This incident has been resolved.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2017-05-05T16:19:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Data Processing Delays - Cube Authorizations Affected]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/32/"></link>
            <id>https://status.nedap-retail.com/incident/32/</id>
            <summary type="html"><![CDATA[<p>Our data processing infrastructure is running behind which is causing that new Cube badge authorizations are not activated directly. No data has been lost.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2017-05-05T13:52:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Timeouts on web applications]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/68/"></link>
            <id>https://status.nedap-retail.com/incident/68/</id>
            <summary type="html"><![CDATA[<p>This incident has been resolved.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2017-03-29T15:23:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Timeouts on web applications]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/67/"></link>
            <id>https://status.nedap-retail.com/incident/67/</id>
            <summary type="html"><![CDATA[<p>Situation is back to normal, we are investigating the cause.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2017-03-29T14:55:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Timeouts on web applications]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/66/"></link>
            <id>https://status.nedap-retail.com/incident/66/</id>
            <summary type="html"><![CDATA[<p>We are currently investigating this issue.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2017-03-29T14:42:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[We are experiencing issues]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/65/"></link>
            <id>https://status.nedap-retail.com/incident/65/</id>
            <summary type="html"><![CDATA[<p>This incident has been resolved.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2017-03-26T11:48:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[We are experiencing issues]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/64/"></link>
            <id>https://status.nedap-retail.com/incident/64/</id>
            <summary type="html"><![CDATA[<p>A fix has been implemented and we are monitoring the results.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2017-03-26T11:34:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[We are experiencing issues]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/63/"></link>
            <id>https://status.nedap-retail.com/incident/63/</id>
            <summary type="html"><![CDATA[<p>The cause for the occasional timeout is network maintenance which should not have had any impact. Our provider is working on the issue.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2017-03-26T11:17:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[We are experiencing issues]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/62/"></link>
            <id>https://status.nedap-retail.com/incident/62/</id>
            <summary type="html"><![CDATA[<p>We are currently investigating this issue.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2017-03-26T11:10:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Backlog in processing customer counter and alarm data]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/61/"></link>
            <id>https://status.nedap-retail.com/incident/61/</id>
            <summary type="html"><![CDATA[<p>This incident has been resolved.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2017-03-15T21:39:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Backlog in processing customer counter and alarm data]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/60/"></link>
            <id>https://status.nedap-retail.com/incident/60/</id>
            <summary type="html"><![CDATA[<p>A fix has been implemented and we are monitoring the results.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2017-03-15T19:43:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Backlog in processing customer counter and alarm data]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/59/"></link>
            <id>https://status.nedap-retail.com/incident/59/</id>
            <summary type="html"><![CDATA[<p>We are currently investigating this issue.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2017-03-15T19:08:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[We are experiencing issues]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/58/"></link>
            <id>https://status.nedap-retail.com/incident/58/</id>
            <summary type="html"><![CDATA[<p>This incident has been resolved.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2017-02-06T15:26:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[We are experiencing issues]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/57/"></link>
            <id>https://status.nedap-retail.com/incident/57/</id>
            <summary type="html"><![CDATA[<p>Everything is back to normal. We are monitoring the situation.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2017-02-06T14:31:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[We are experiencing issues]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/56/"></link>
            <id>https://status.nedap-retail.com/incident/56/</id>
            <summary type="html"><![CDATA[<p>Data processing in !D Cloud is delayed.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2017-02-06T13:47:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[We are experiencing issues]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/55/"></link>
            <id>https://status.nedap-retail.com/incident/55/</id>
            <summary type="html"><![CDATA[<p>We are investigating the cause and will update this page as soon as we know more.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2017-02-06T13:44:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[We are experiencing issues]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/54/"></link>
            <id>https://status.nedap-retail.com/incident/54/</id>
            <summary type="html"><![CDATA[<p>We are currently investigating this issue.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2017-02-06T13:43:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Occasional error on !D Cloud web]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/53/"></link>
            <id>https://status.nedap-retail.com/incident/53/</id>
            <summary type="html"><![CDATA[<p>Cause of the error message was a cached invalid value.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2017-01-23T10:58:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Occasional error on !D Cloud web]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/52/"></link>
            <id>https://status.nedap-retail.com/incident/52/</id>
            <summary type="html"><![CDATA[<p>We are investigating occasional error messages on !D Cloud web.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2017-01-23T10:50:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Connectivity issues]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/70/"></link>
            <id>https://status.nedap-retail.com/incident/70/</id>
            <summary type="html"><![CDATA[<p>Our network provider changed some low level network settings that caused connectivity issues between our servers. We will work with our network provider to avoid these kind of issues in the future.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2016-05-25T12:46:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Connectivity issues]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/69/"></link>
            <id>https://status.nedap-retail.com/incident/69/</id>
            <summary type="html"><![CDATA[<p>We are currently investigating this issue.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2016-05-25T12:01:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Unscheduled upgrade of servers]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/72/"></link>
            <id>https://status.nedap-retail.com/incident/72/</id>
            <summary type="html"><![CDATA[<p>This incident has been resolved.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2016-03-01T16:50:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Unscheduled upgrade of servers]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/71/"></link>
            <id>https://status.nedap-retail.com/incident/71/</id>
            <summary type="html"><![CDATA[<p>We are currently rolling out a high priority upgrade of a critical part of our server infrastructure. !D Cloud APIs and website may be unavailable for a short period of time.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2016-03-01T16:23:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Some stores not visible in !D Cloud]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/51/"></link>
            <id>https://status.nedap-retail.com/incident/51/</id>
            <summary type="html"><![CDATA[<p>This incident has been resolved.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2016-02-29T07:58:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Nedap Retail Statuspage</name>
            </author>
            <title type="text"><![CDATA[Some stores not visible in !D Cloud]]></title>
            <link rel="alternate" type="text/html" href="https://status.nedap-retail.com/incident/50/"></link>
            <id>https://status.nedap-retail.com/incident/50/</id>
            <summary type="html"><![CDATA[<p>Due to a bug in a release some stores are currently not visible in !D Cloud Web. We have identified the problem and are working on a fix right now.</p>
<p>The !D Cloud app is still operational - switching from one store to another might temporarily not be possible.</p>
<p>SFTP and API's are not affected. No data has been lost.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2016-02-29T07:53:00+00:00</updated>
        </entry>
</feed>
