tag:jamezz1.statuspage.io,2005:/historyJamezz Status - Incident History2024-03-23T06:54:57+01:00Jamezztag:jamezz1.statuspage.io,2005:Incident/193500022023-12-06T12:50:00+01:002023-12-06T12:50:00+01:00Order delay<p><small>Dec <var data-var='date'> 6</var>, <var data-var='time'>12:50</var> CET</small><br><strong>Resolved</strong> - The incident is resolved, all systems are operational again.</p><p><small>Dec <var data-var='date'> 6</var>, <var data-var='time'>12:36</var> CET</small><br><strong>Update</strong> - We are continuing to investigate this issue.</p><p><small>Dec <var data-var='date'> 6</var>, <var data-var='time'>12:34</var> CET</small><br><strong>Investigating</strong> - We are currently experiencing some delay in the order dispatching due to abnormally high CPU usage, we are investigating the issue</p>tag:jamezz1.statuspage.io,2005:Incident/191373712023-11-16T20:46:37+01:002023-11-16T20:46:37+01:00Mollie Point of Sale minor outage<p><small>Nov <var data-var='date'>16</var>, <var data-var='time'>20:46</var> CET</small><br><strong>Resolved</strong> - This incident has been resolved</p><p><small>Nov <var data-var='date'>16</var>, <var data-var='time'>14:18</var> CET</small><br><strong>Monitoring</strong> - Mollie is experiencing minor outage on the payment terminals. They have found the issue and are actively monitoring if new issues occur</p>tag:jamezz1.statuspage.io,2005:Incident/191193892023-11-14T18:41:05+01:002023-11-14T18:41:05+01:00Pusher websocket client total outage<p><small>Nov <var data-var='date'>14</var>, <var data-var='time'>18:41</var> CET</small><br><strong>Resolved</strong> - Pusher has resolved the issue, all systems are operational again</p><p><small>Nov <var data-var='date'>14</var>, <var data-var='time'>17:31</var> CET</small><br><strong>Update</strong> - We are continuing to investigate this issue.</p><p><small>Nov <var data-var='date'>14</var>, <var data-var='time'>17:29</var> CET</small><br><strong>Investigating</strong> - Due to a total outage at a 3th party websocket tooling, the following is disrupted:<br /><br />- Jamezz print services<br />- Jamezz shared basked<br /><br />Pusher is investigating this problem. For latest updates go to https://status.pusher.com/</p>tag:jamezz1.statuspage.io,2005:Incident/182456582023-08-24T15:49:29+02:002023-08-24T15:49:29+02:00CM Payments disrupted<p><small>Aug <var data-var='date'>24</var>, <var data-var='time'>15:49</var> CEST</small><br><strong>Resolved</strong> - The incident has been resolved and CM payments is back up.</p><p><small>Aug <var data-var='date'>24</var>, <var data-var='time'>14:37</var> CEST</small><br><strong>Investigating</strong> - CM Payments is currently experiencing disruption on their payment platform. Customers using CM payments as a payment provider will not be able to process payed orders. CM payments is investigating the issue.</p>tag:jamezz1.statuspage.io,2005:Incident/124172332022-10-20T08:40:57+02:002022-10-21T08:24:58+02:00This is an example incident<p><small>Oct <var data-var='date'>20</var>, <var data-var='time'>08:40</var> CEST</small><br><strong>Resolved</strong> - Empathize with those affected and let them know everything is operating as normal.</p><p><small>Oct <var data-var='date'>20</var>, <var data-var='time'>08:30</var> CEST</small><br><strong>Monitoring</strong> - Let your users know once a fix is in place, and keep communication clear and precise.</p><p><small>Oct <var data-var='date'>20</var>, <var data-var='time'>08:36</var> CEST</small><br><strong>Identified</strong> - As you continue to work through the incident, update your customers frequently.</p><p><small>Oct <var data-var='date'>20</var>, <var data-var='time'>09:06</var> CEST</small><br><strong>Investigating</strong> - When your product or service isn’t functioning as expected, let your customers know by creating an incident. Communicate early, even if you don’t know exactly what’s going on.</p>