<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>pinvandaag Status - Incident history</title>
    <link>https://pinvandaag.instatus.com</link>
    <description>pinvandaag</description>
    <pubDate>Sat, 29 Aug 2026 15:44:11 +0000</pubDate>
    
<item>
  <title>optimumpos.nl is back up</title>
  <description>
    Type: Incident
    

    Affected Components: Optimum POS website (optimumpos.nl)
    Aug 29, 15:44:11 GMT+0 - Investigating - Optimum POS website (optimumpos.nl) is down at the moment. This incident was automatically created by Instatus monitoring. Aug 29, 15:53:53 GMT+0 - Resolved - Optimum POS website (optimumpos.nl) is back up. This incident was automatically resolved by Instatus monitoring. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 29&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:44:11&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  Optimum POS website (optimumpos.nl) is down at the moment. This incident was automatically created by Instatus monitoring..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 29&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:53:53&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  Optimum POS website (optimumpos.nl) is back up. This incident was automatically resolved by Instatus monitoring..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Sat, 29 Aug 2026 15:44:11 +0000</pubDate>
  <link>https://pinvandaag.instatus.com/incident/cmtejwhs500y107jjagl8z45w</link>
  <guid>https://pinvandaag.instatus.com/incident/cmtejwhs500y107jjagl8z45w</guid>
</item>

<item>
  <title>https://www.pinportal.nl is back up</title>
  <description>
    Type: Incident
    

    Affected Components: Pin Portal Dashboard (pinportal.nl)
    Aug 22, 14:00:54 GMT+0 - Investigating - Pin Portal Dashboard (pinportal.nl) is down at the moment. This incident was automatically created by Instatus monitoring. Aug 22, 14:10:40 GMT+0 - Resolved - Pin Portal Dashboard (pinportal.nl) is back up. This incident was automatically resolved by Instatus monitoring. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 22&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;14:00:54&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  Pin Portal Dashboard (pinportal.nl) is down at the moment. This incident was automatically created by Instatus monitoring..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 22&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;14:10:40&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  Pin Portal Dashboard (pinportal.nl) is back up. This incident was automatically resolved by Instatus monitoring..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Sat, 22 Aug 2026 14:00:54 +0000</pubDate>
  <link>https://pinvandaag.instatus.com/incident/cmt4g4p6c01hb07mj4079o2yy</link>
  <guid>https://pinvandaag.instatus.com/incident/cmt4g4p6c01hb07mj4079o2yy</guid>
</item>

<item>
  <title>https://www.pinportal.nl is back up</title>
  <description>
    Type: Incident
    

    Affected Components: Pin Portal Dashboard (pinportal.nl)
    Aug 19, 10:05:49 GMT+0 - Investigating - Pin Portal Dashboard (pinportal.nl) is down at the moment. This incident was automatically created by Instatus monitoring. Aug 19, 10:25:30 GMT+0 - Resolved - Pin Portal Dashboard (pinportal.nl) is back up. This incident was automatically resolved by Instatus monitoring. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 19&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;10:05:49&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  Pin Portal Dashboard (pinportal.nl) is down at the moment. This incident was automatically created by Instatus monitoring..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 19&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;10:25:30&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  Pin Portal Dashboard (pinportal.nl) is back up. This incident was automatically resolved by Instatus monitoring..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Wed, 19 Aug 2026 10:05:49 +0000</pubDate>
  <link>https://pinvandaag.instatus.com/incident/cmszxetmf04ed07mcejbod1ms</link>
  <guid>https://pinvandaag.instatus.com/incident/cmszxetmf04ed07mcejbod1ms</guid>
</item>

<item>
  <title>optimumpos.nl is back up</title>
  <description>
    Type: Incident
    

    Affected Components: Optimum POS website (optimumpos.nl)
    Aug 18, 13:58:43 GMT+0 - Investigating - Optimum POS website (optimumpos.nl) is down at the moment. This incident was automatically created by Instatus monitoring. Aug 18, 14:38:56 GMT+0 - Resolved - Optimum POS website (optimumpos.nl) is back up. This incident was automatically resolved by Instatus monitoring. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 18&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;13:58:43&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  Optimum POS website (optimumpos.nl) is down at the moment. This incident was automatically created by Instatus monitoring..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 18&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;14:38:56&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  Optimum POS website (optimumpos.nl) is back up. This incident was automatically resolved by Instatus monitoring..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 18 Aug 2026 13:58:43 +0000</pubDate>
  <link>https://pinvandaag.instatus.com/incident/cmsyqat1503tr07pexgghd42g</link>
  <guid>https://pinvandaag.instatus.com/incident/cmsyqat1503tr07pexgghd42g</guid>
</item>

<item>
  <title>https://www.pinvandaag.nl is back up</title>
  <description>
    Type: Incident
    

    Affected Components: Pin Vandaag Website (pinvandaag.nl)
    Aug 18, 13:58:32 GMT+0 - Investigating - Pin Vandaag Website (pinvandaag.nl) is down at the moment. This incident was automatically created by Instatus monitoring. Aug 18, 14:38:43 GMT+0 - Resolved - Pin Vandaag Website (pinvandaag.nl) is back up. This incident was automatically resolved by Instatus monitoring. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 18&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;13:58:32&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  Pin Vandaag Website (pinvandaag.nl) is down at the moment. This incident was automatically created by Instatus monitoring..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 18&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;14:38:43&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  Pin Vandaag Website (pinvandaag.nl) is back up. This incident was automatically resolved by Instatus monitoring..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 18 Aug 2026 13:58:32 +0000</pubDate>
  <link>https://pinvandaag.instatus.com/incident/cmsyqa975043b07oega3ez8fg</link>
  <guid>https://pinvandaag.instatus.com/incident/cmsyqa975043b07oega3ez8fg</guid>
</item>

<item>
  <title>https://www.pinvandaag.nl is back up</title>
  <description>
    Type: Incident
    

    Affected Components: Pin Vandaag Website (pinvandaag.nl)
    Aug 18, 08:36:49 GMT+0 - Investigating - Pin Vandaag Website (pinvandaag.nl) is down at the moment. This incident was automatically created by Instatus monitoring. Aug 18, 08:46:48 GMT+0 - Resolved - Pin Vandaag Website (pinvandaag.nl) is back up. This incident was automatically resolved by Instatus monitoring. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 18&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;08:36:49&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  Pin Vandaag Website (pinvandaag.nl) is down at the moment. This incident was automatically created by Instatus monitoring..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 18&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;08:46:48&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  Pin Vandaag Website (pinvandaag.nl) is back up. This incident was automatically resolved by Instatus monitoring..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 18 Aug 2026 08:36:49 +0000</pubDate>
  <link>https://pinvandaag.instatus.com/incident/cmsyesmg703yo07oe1pmjm0z9</link>
  <guid>https://pinvandaag.instatus.com/incident/cmsyesmg703yo07oe1pmjm0z9</guid>
</item>

<item>
  <title>https://www.pinvandaag.nl is back up</title>
  <description>
    Type: Incident
    

    Affected Components: Pin Vandaag Website (pinvandaag.nl)
    Aug 17, 13:30:04 GMT+0 - Investigating - Pin Vandaag Website (pinvandaag.nl) is down at the moment. This incident was automatically created by Instatus monitoring. Aug 17, 13:39:46 GMT+0 - Resolved - Pin Vandaag Website (pinvandaag.nl) is back up. This incident was automatically resolved by Instatus monitoring. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 17&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;13:30:04&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  Pin Vandaag Website (pinvandaag.nl) is down at the moment. This incident was automatically created by Instatus monitoring..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 17&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;13:39:46&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  Pin Vandaag Website (pinvandaag.nl) is back up. This incident was automatically resolved by Instatus monitoring..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Mon, 17 Aug 2026 13:30:04 +0000</pubDate>
  <link>https://pinvandaag.instatus.com/incident/cmsx9ts8d039v07s8fne403zh</link>
  <guid>https://pinvandaag.instatus.com/incident/cmsx9ts8d039v07s8fne403zh</guid>
</item>

<item>
  <title>https://www.pinvandaag.nl is back up</title>
  <description>
    Type: Incident
    

    Affected Components: Pin Vandaag Website (pinvandaag.nl)
    Aug 16, 23:15:15 GMT+0 - Investigating - Pin Vandaag Website (pinvandaag.nl) is down at the moment. This incident was automatically created by Instatus monitoring. Aug 16, 23:24:58 GMT+0 - Resolved - Pin Vandaag Website (pinvandaag.nl) is back up. This incident was automatically resolved by Instatus monitoring. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 16&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;23:15:15&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  Pin Vandaag Website (pinvandaag.nl) is down at the moment. This incident was automatically created by Instatus monitoring..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 16&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;23:24:58&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  Pin Vandaag Website (pinvandaag.nl) is back up. This incident was automatically resolved by Instatus monitoring..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Sun, 16 Aug 2026 23:15:15 +0000</pubDate>
  <link>https://pinvandaag.instatus.com/incident/cmswfai0k031107oemdmi8y33</link>
  <guid>https://pinvandaag.instatus.com/incident/cmswfai0k031107oemdmi8y33</guid>
</item>

<item>
  <title>optimumpos.nl is back up</title>
  <description>
    Type: Incident
    

    Affected Components: Optimum POS website (optimumpos.nl)
    Aug 14, 18:34:09 GMT+0 - Investigating - Optimum POS website (optimumpos.nl) is down at the moment. This incident was automatically created by Instatus monitoring. Aug 14, 18:43:51 GMT+0 - Resolved - Optimum POS website (optimumpos.nl) is back up. This incident was automatically resolved by Instatus monitoring. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 14&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;18:34:09&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  Optimum POS website (optimumpos.nl) is down at the moment. This incident was automatically created by Instatus monitoring..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 14&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;18:43:51&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  Optimum POS website (optimumpos.nl) is back up. This incident was automatically resolved by Instatus monitoring..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Fri, 14 Aug 2026 18:34:09 +0000</pubDate>
  <link>https://pinvandaag.instatus.com/incident/cmstadapj01qz07peub98663q</link>
  <guid>https://pinvandaag.instatus.com/incident/cmstadapj01qz07peub98663q</guid>
</item>

<item>
  <title>https://www.pinportal.nl is back up</title>
  <description>
    Type: Incident
    

    Affected Components: Pin Portal Dashboard (pinportal.nl)
    Aug 14, 09:22:09 GMT+0 - Investigating - Pin Portal Dashboard (pinportal.nl) is down at the moment. This incident was automatically created by Instatus monitoring. Aug 14, 09:31:51 GMT+0 - Resolved - Pin Portal Dashboard (pinportal.nl) is back up. This incident was automatically resolved by Instatus monitoring. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 14&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;09:22:09&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  Pin Portal Dashboard (pinportal.nl) is down at the moment. This incident was automatically created by Instatus monitoring..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 14&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;09:31:51&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  Pin Portal Dashboard (pinportal.nl) is back up. This incident was automatically resolved by Instatus monitoring..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Fri, 14 Aug 2026 09:22:09 +0000</pubDate>
  <link>https://pinvandaag.instatus.com/incident/cmssqnf1n01l607o6y81ynwg9</link>
  <guid>https://pinvandaag.instatus.com/incident/cmssqnf1n01l607o6y81ynwg9</guid>
</item>

<item>
  <title>https://www.pinportal.nl is back up</title>
  <description>
    Type: Incident
    

    Affected Components: Pin Portal Dashboard (pinportal.nl)
    Aug 13, 09:23:50 GMT+0 - Investigating - Pin Portal Dashboard (pinportal.nl) is down at the moment. This incident was automatically created by Instatus monitoring. Aug 13, 09:33:34 GMT+0 - Resolved - Pin Portal Dashboard (pinportal.nl) is back up. This incident was automatically resolved by Instatus monitoring. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 13&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;09:23:50&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  Pin Portal Dashboard (pinportal.nl) is down at the moment. This incident was automatically created by Instatus monitoring..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 13&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;09:33:34&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  Pin Portal Dashboard (pinportal.nl) is back up. This incident was automatically resolved by Instatus monitoring..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Thu, 13 Aug 2026 09:23:50 +0000</pubDate>
  <link>https://pinvandaag.instatus.com/incident/cmsrb9qbt013807mchteavg14</link>
  <guid>https://pinvandaag.instatus.com/incident/cmsrb9qbt013807mchteavg14</guid>
</item>

<item>
  <title>https://www.pinvandaag.nl is back up</title>
  <description>
    Type: Incident
    

    Affected Components: Pin Vandaag Website (pinvandaag.nl)
    Aug 12, 19:35:46 GMT+0 - Investigating - Pin Vandaag Website (pinvandaag.nl) is down at the moment. This incident was automatically created by Instatus monitoring. Aug 12, 19:45:29 GMT+0 - Resolved - Pin Vandaag Website (pinvandaag.nl) is back up. This incident was automatically resolved by Instatus monitoring. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 12&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;19:35:46&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  Pin Vandaag Website (pinvandaag.nl) is down at the moment. This incident was automatically created by Instatus monitoring..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 12&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;19:45:29&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  Pin Vandaag Website (pinvandaag.nl) is back up. This incident was automatically resolved by Instatus monitoring..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Wed, 12 Aug 2026 19:35:46 +0000</pubDate>
  <link>https://pinvandaag.instatus.com/incident/cmsqhp6fd00s207oednvfsvyg</link>
  <guid>https://pinvandaag.instatus.com/incident/cmsqhp6fd00s207oednvfsvyg</guid>
</item>

<item>
  <title>optimumpos.nl is back up</title>
  <description>
    Type: Incident
    

    Affected Components: Optimum POS website (optimumpos.nl)
    Aug 12, 19:35:42 GMT+0 - Investigating - Optimum POS website (optimumpos.nl) is down at the moment. This incident was automatically created by Instatus monitoring. Aug 12, 19:45:26 GMT+0 - Resolved - Optimum POS website (optimumpos.nl) is back up. This incident was automatically resolved by Instatus monitoring. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 12&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;19:35:42&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  Optimum POS website (optimumpos.nl) is down at the moment. This incident was automatically created by Instatus monitoring..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 12&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;19:45:26&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  Optimum POS website (optimumpos.nl) is back up. This incident was automatically resolved by Instatus monitoring..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Wed, 12 Aug 2026 19:35:42 +0000</pubDate>
  <link>https://pinvandaag.instatus.com/incident/cmsqhoqyk00oj07o6wqn931ne</link>
  <guid>https://pinvandaag.instatus.com/incident/cmsqhoqyk00oj07o6wqn931ne</guid>
</item>

<item>
  <title>https://www.pinportal.nl is back up</title>
  <description>
    Type: Incident
    

    Affected Components: Pin Portal Dashboard (pinportal.nl)
    Aug 12, 12:56:37 GMT+0 - Investigating - Pin Portal Dashboard (pinportal.nl) is down at the moment. This incident was automatically created by Instatus monitoring. Aug 12, 13:06:19 GMT+0 - Resolved - Pin Portal Dashboard (pinportal.nl) is back up. This incident was automatically resolved by Instatus monitoring. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 12&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;12:56:37&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  Pin Portal Dashboard (pinportal.nl) is down at the moment. This incident was automatically created by Instatus monitoring..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 12&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;13:06:19&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  Pin Portal Dashboard (pinportal.nl) is back up. This incident was automatically resolved by Instatus monitoring..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Wed, 12 Aug 2026 12:56:37 +0000</pubDate>
  <link>https://pinvandaag.instatus.com/incident/cmsq3fiaf00gp07o6ijdwgnb2</link>
  <guid>https://pinvandaag.instatus.com/incident/cmsq3fiaf00gp07o6ijdwgnb2</guid>
</item>

<item>
  <title>https://www.pinportal.nl is back up</title>
  <description>
    Type: Incident
    

    Affected Components: Pin Portal Dashboard (pinportal.nl)
    Aug 12, 12:15:53 GMT+0 - Investigating - Pin Portal Dashboard (pinportal.nl) is down at the moment. This incident was automatically created by Instatus monitoring. Aug 12, 12:25:35 GMT+0 - Resolved - Pin Portal Dashboard (pinportal.nl) is back up. This incident was automatically resolved by Instatus monitoring. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 12&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;12:15:53&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  Pin Portal Dashboard (pinportal.nl) is down at the moment. This incident was automatically created by Instatus monitoring..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 12&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;12:25:35&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  Pin Portal Dashboard (pinportal.nl) is back up. This incident was automatically resolved by Instatus monitoring..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Wed, 12 Aug 2026 12:15:53 +0000</pubDate>
  <link>https://pinvandaag.instatus.com/incident/cmsq1z6el00fx07s8j3euwf9h</link>
  <guid>https://pinvandaag.instatus.com/incident/cmsq1z6el00fx07s8j3euwf9h</guid>
</item>

<item>
  <title>Gepland onderhoud – Migratie websites</title>
  <description>
    Type: Maintenance
    Duration: 16 hours and 14 minutes

    Affected Components: Optimum POS website (optimumpos.nl), Pin Vandaag Website (pinvandaag.nl)
    Aug 10, 08:45:12 GMT+0 - Identified - Vanwege gepland onderhoud worden [**PinVandaag.nl**](http://PinVandaag.nl) en [**OptimumPOS.nl**](http://OptimumPOS.nl) verhuisd naar een nieuwe serveromgeving.

Met deze migratie verbeteren we de **prestaties, stabiliteit en betrouwbaarheid** van onze websites.

Tijdens de migratie kunnen [PinVandaag.nl](http://PinVandaag.nl) en [OptimumPOS.nl](http://OptimumPOS.nl) tijdelijk minder goed bereikbaar zijn. We proberen de onderbreking zo kort mogelijk te houden.

**Betalingsverkeer en pinautomaten worden hierdoor niet beïnvloed.**

Na afronding van de migratie zullen beide websites weer volledig beschikbaar zijn.

Onze excuses voor het eventuele ongemak en bedankt voor uw begrip. Aug 10, 09:01:26 GMT+0 - Completed - Werkzaamheden zijn gestart migratie is bezig 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 16 hours and 14 minutes</p>
    <p><strong>Affected Components:</strong> , </p>
    &lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 10&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;08:45:12&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Vanwege gepland onderhoud worden [**PinVandaag.nl**](http://PinVandaag.nl) en [**OptimumPOS.nl**](http://OptimumPOS.nl) verhuisd naar een nieuwe serveromgeving.

Met deze migratie verbeteren we de **prestaties, stabiliteit en betrouwbaarheid** van onze websites.

Tijdens de migratie kunnen [PinVandaag.nl](http://PinVandaag.nl) en [OptimumPOS.nl](http://OptimumPOS.nl) tijdelijk minder goed bereikbaar zijn. We proberen de onderbreking zo kort mogelijk te houden.

**Betalingsverkeer en pinautomaten worden hierdoor niet beïnvloed.**

Na afronding van de migratie zullen beide websites weer volledig beschikbaar zijn.

Onze excuses voor het eventuele ongemak en bedankt voor uw begrip..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 10&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;09:01:26&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  Werkzaamheden zijn gestart migratie is bezig.&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 11 Aug 2026 07:00:00 +0000</pubDate>
  <link>https://pinvandaag.instatus.com/maintenance/cmsmzkgvp16p70rpqgzgnns01</link>
  <guid>https://pinvandaag.instatus.com/maintenance/cmsmzkgvp16p70rpqgzgnns01</guid>
</item>

<item>
  <title>Migratie REST API-server naar nieuwe infrastructuur</title>
  <description>
    Type: Maintenance
    Duration: 2 days, 22 hours and 30 minutes

    Affected Components: REST-API (rest-api.pinvandaag.com), Rest API POS (pos.pinvandaag.com)
    Aug 10, 06:29:00 GMT+0 - Completed - Migratie naar nieuwe server volledig afgerond en getest! Aug 7, 07:59:20 GMT+0 - Identified - Op **maandag 10 augustus 2026 van 04:00 tot uiterlijk 09:00 uur** voeren wij gepland onderhoud uit aan onze REST API-infrastructuur.

Tijdens dit onderhoud migreren wij onze REST API-server naar een nieuwe serveromgeving bij Cloud86\. Met deze migratie willen wij de **performance, stabiliteit en betrouwbaarheid** van onze dienstverlening verder verbeteren. De afgelopen periode hebben wij meerdere verstoringen ervaren op de huidige serveromgeving. Met de nieuwe infrastructuur verwachten wij de kans op dergelijke verstoringen aanzienlijk te verkleinen.

### Mogelijke impact

Tijdens de migratie kunnen de volgende diensten tijdelijk minder goed bereikbaar zijn of korte onderbrekingen ervaren:

* REST API (`rest-api.pinvandaag.com`)
* REST API POS (`pos.pinvandaag.com`)
* Diensten en koppelingen die afhankelijk zijn van deze API&#039;s

Wij proberen de daadwerkelijke onderbreking zo kort mogelijk te houden. Het onderhoudsvenster van vier uur is gereserveerd om de migratie, controles en eventuele noodzakelijke aanpassingen zorgvuldig uit te kunnen voeren.

Na de migratie controleren wij alle betrokken diensten voordat het onderhoud als afgerond wordt gemeld.

Onze excuses voor eventueel ongemak en bedankt voor uw beg 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 2 days, 22 hours and 30 minutes</p>
    <p><strong>Affected Components:</strong> , </p>
    &lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 10&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;06:29:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  Migratie naar nieuwe server volledig afgerond en getest!.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 7&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;07:59:20&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Op **maandag 10 augustus 2026 van 04:00 tot uiterlijk 09:00 uur** voeren wij gepland onderhoud uit aan onze REST API-infrastructuur.

Tijdens dit onderhoud migreren wij onze REST API-server naar een nieuwe serveromgeving bij Cloud86\. Met deze migratie willen wij de **performance, stabiliteit en betrouwbaarheid** van onze dienstverlening verder verbeteren. De afgelopen periode hebben wij meerdere verstoringen ervaren op de huidige serveromgeving. Met de nieuwe infrastructuur verwachten wij de kans op dergelijke verstoringen aanzienlijk te verkleinen.

### Mogelijke impact

Tijdens de migratie kunnen de volgende diensten tijdelijk minder goed bereikbaar zijn of korte onderbrekingen ervaren:

* REST API (`rest-api.pinvandaag.com`)
* REST API POS (`pos.pinvandaag.com`)
* Diensten en koppelingen die afhankelijk zijn van deze API&#039;s

Wij proberen de daadwerkelijke onderbreking zo kort mogelijk te houden. Het onderhoudsvenster van vier uur is gereserveerd om de migratie, controles en eventuele noodzakelijke aanpassingen zorgvuldig uit te kunnen voeren.

Na de migratie controleren wij alle betrokken diensten voordat het onderhoud als afgerond wordt gemeld.

Onze excuses voor eventueel ongemak en bedankt voor uw beg.&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Mon, 10 Aug 2026 07:00:00 +0000</pubDate>
  <link>https://pinvandaag.instatus.com/maintenance/cmsinlxd209qr0kpq9zr2tx7j</link>
  <guid>https://pinvandaag.instatus.com/maintenance/cmsinlxd209qr0kpq9zr2tx7j</guid>
</item>

<item>
  <title>WIPAY DISTURBANCE</title>
  <description>
    Type: Incident
    Duration: 6 days, 14 hours and 18 minutes

    Affected Components: REST-API (rest-api.pinvandaag.com)
    Jul 22, 15:58:00 GMT+0 - Identified - Affected system: WIPay host (ECR protocol)

Impact: Recurring interruptions of Callback service.  
  
Planned action: ROLLBACK to the previous WIPay version, as a new WIPay version was installed on Sunday, 19 July.

  
When: Services will be down for 30 minutes on Thursday, 23 July, starting at 05:30 AM.  
  
Extra information: In the meantime, our engineers are continuously monitoring the system. Should any disruptions occur, services will be restarted as soon as possible. Please note that short interruptions may be noticeable from now until the rollback is complete. No need to report further issues between now and tomorrow 06:00 AM.

Next update notification: Thursday, 23 July. Jul 23, 15:58:01 GMT+0 - Monitoring - Affected system: WIPay host (ECR protocol)

  
Status: No errors to report after 12:00 AM till now. Steady for more than 1 hour. We keep monitoring and will act directly as disruptions are recurring. No need to report this.  
  
Extra information: A possible root cause has been found. Tests are carried out on the WIPay acceptance environment. When OK, the fix will be rolled out (as soon as possible) on our production environment. This may be done during merchant opening hours. Time and duration of the roll out on production will be communicated duly. 

Next update notification: Thursday, 23 July, 15:30 PM (or sooner when needed) Jul 23, 15:58:00 GMT+0 - Identified - Affected system: WIPay host (ECR protocol)

Impact: Recurring interruptions of Callback service. Still partly persisting. Transactions are still possible, but feedback with transaction result may be correctly received, delayed, or not received at all. This differs per terminal. When the system is 100% up, the not received transaction results can be requested via a status request (accompanied by a SSAI, reference or transaction ID).

  
Extra information: The rollback last night was successful. Apparently, this action failed to provide the expected solution, despite positive initial indicators. Analyses are ongoing to identify a structural fix.

Next update notification: Thursday, 23 July, 14:00 PM Jul 22, 15:00:00 GMT+0 - Monitoring - Affected system: WIPay host (ECR protocol)

Impact: Partially down. Transactions are possible, Callbacks are not sent to ECR/POS server.

Resolve time: to be determined

Next update notification: within 2 hours (or sooner when more additional information is available and/or the situation has changed) Jul 23, 15:58:02 GMT+0 - Monitoring - Affected system: WIPay host (ECR protocol)

  
Status: We keep monitoring the service and will act directly when disruptions are occurring. No need to report this.  
  
Next step: An intervention is scheduled for tomorrow morning July 24, 2026, at 05:30 AM. You may experience a brief service interruption during this time. Jul 27, 05:17:00 GMT+0 - Resolved - Uit ons onderzoek is gebleken dat de WIPay-applicatie tijdens een aantal piekmomenten met een hoog transactievolume moeilijkheden ondervond bij het beheren van bestaande verbindingen, waardoor inkomende berichten niet altijd tijdig konden worden verwerkt. De impact hiervan werd vergroot door uitzonderlijk hoge activiteit van een beperkt aantal terminals.

Onze technische teams hebben een eerste workaround geïmplementeerd om specifieke activiteitspatronen aan te pakken, gevolgd door een bredere oplossing om de robuustheid van het platform bij onverwacht hoge berichtvolumes te vergroten. Daarnaast hebben we onze monitoring- en waarschuwingsmechanismen verfijnd om snellere detectie en interventie te faciliteren mocht dergelijk gedrag zich opnieuw voordoen.

Onze teams blijven onverminderd werken aan een permanente oplossing. We blijven de omgeving nauwlettend monitoren en zullen u, waar nodig, verder informeren.

Wij onderkennen het belang van een stabiele dienstverlening voor uw bedrijf en betreuren de eventuele hinder die u zou kunnen ondervinden. We danken u voor uw geduld en het vertrouwen dat u in ons stelt. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 6 days, 14 hours and 18 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 22&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:58:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Affected system: WIPay host (ECR protocol)

Impact: Recurring interruptions of Callback service.  
  
Planned action: ROLLBACK to the previous WIPay version, as a new WIPay version was installed on Sunday, 19 July.

  
When: Services will be down for 30 minutes on Thursday, 23 July, starting at 05:30 AM.  
  
Extra information: In the meantime, our engineers are continuously monitoring the system. Should any disruptions occur, services will be restarted as soon as possible. Please note that short interruptions may be noticeable from now until the rollback is complete. No need to report further issues between now and tomorrow 06:00 AM.

Next update notification: Thursday, 23 July..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 23&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:58:01&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  Affected system: WIPay host (ECR protocol)

  
Status: No errors to report after 12:00 AM till now. Steady for more than 1 hour. We keep monitoring and will act directly as disruptions are recurring. No need to report this.  
  
Extra information: A possible root cause has been found. Tests are carried out on the WIPay acceptance environment. When OK, the fix will be rolled out (as soon as possible) on our production environment. This may be done during merchant opening hours. Time and duration of the roll out on production will be communicated duly. 

Next update notification: Thursday, 23 July, 15:30 PM (or sooner when needed).&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 23&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:58:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Affected system: WIPay host (ECR protocol)

Impact: Recurring interruptions of Callback service. Still partly persisting. Transactions are still possible, but feedback with transaction result may be correctly received, delayed, or not received at all. This differs per terminal. When the system is 100% up, the not received transaction results can be requested via a status request (accompanied by a SSAI, reference or transaction ID).

  
Extra information: The rollback last night was successful. Apparently, this action failed to provide the expected solution, despite positive initial indicators. Analyses are ongoing to identify a structural fix.

Next update notification: Thursday, 23 July, 14:00 PM.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 22&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  Affected system: WIPay host (ECR protocol)

Impact: Partially down. Transactions are possible, Callbacks are not sent to ECR/POS server.

Resolve time: to be determined

Next update notification: within 2 hours (or sooner when more additional information is available and/or the situation has changed).&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 23&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:58:02&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  Affected system: WIPay host (ECR protocol)

  
Status: We keep monitoring the service and will act directly when disruptions are occurring. No need to report this.  
  
Next step: An intervention is scheduled for tomorrow morning July 24, 2026, at 05:30 AM. You may experience a brief service interruption during this time..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 27&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;05:17:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  Uit ons onderzoek is gebleken dat de WIPay-applicatie tijdens een aantal piekmomenten met een hoog transactievolume moeilijkheden ondervond bij het beheren van bestaande verbindingen, waardoor inkomende berichten niet altijd tijdig konden worden verwerkt. De impact hiervan werd vergroot door uitzonderlijk hoge activiteit van een beperkt aantal terminals.

Onze technische teams hebben een eerste workaround geïmplementeerd om specifieke activiteitspatronen aan te pakken, gevolgd door een bredere oplossing om de robuustheid van het platform bij onverwacht hoge berichtvolumes te vergroten. Daarnaast hebben we onze monitoring- en waarschuwingsmechanismen verfijnd om snellere detectie en interventie te faciliteren mocht dergelijk gedrag zich opnieuw voordoen.

Onze teams blijven onverminderd werken aan een permanente oplossing. We blijven de omgeving nauwlettend monitoren en zullen u, waar nodig, verder informeren.

Wij onderkennen het belang van een stabiele dienstverlening voor uw bedrijf en betreuren de eventuele hinder die u zou kunnen ondervinden. We danken u voor uw geduld en het vertrouwen dat u in ons stelt..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Wed, 22 Jul 2026 15:00:00 +0000</pubDate>
  <link>https://pinvandaag.instatus.com/incident/cmrz5prh900ik1arut0msvzq2</link>
  <guid>https://pinvandaag.instatus.com/incident/cmrz5prh900ik1arut0msvzq2</guid>
</item>

  </channel>
  </rss>