tag:status.bizzon.com,2005:/historyBizzon Status - Incident History2024-03-29T05:23:53ZBizzontag:status.bizzon.com,2005:Incident/202996332024-03-19T10:01:55Z2024-03-19T10:01:55ZMissing features<p><small>Mar <var data-var='date'>19</var>, <var data-var='time'>10:01</var> UTC</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Mar <var data-var='date'>19</var>, <var data-var='time'>09:47</var> UTC</small><br><strong>Monitoring</strong> - The issue has been identified and all functionalities have been restored for all user accounts. We are monitoring the performance.</p><p><small>Mar <var data-var='date'>19</var>, <var data-var='time'>07:24</var> UTC</small><br><strong>Investigating</strong> - We have received reports absence of some features from users' accounts and our team is currently investigating the root cause and restoring the functionalities.</p>tag:status.bizzon.com,2005:Incident/198793592024-02-01T01:36:22Z2024-02-01T01:36:22ZDegraded service<p><small>Feb <var data-var='date'> 1</var>, <var data-var='time'>01:36</var> UTC</small><br><strong>Resolved</strong> - The service has been fully restored and more information on this incident will be posted at a later date.</p><p><small>Jan <var data-var='date'>31</var>, <var data-var='time'>21:28</var> UTC</small><br><strong>Monitoring</strong> - The service has been fully restored and more information on this incident will be posted at a later date.</p>tag:status.bizzon.com,2005:Incident/194051672023-12-12T07:18:35Z2023-12-12T13:04:44ZDegraded service<p><small>Dec <var data-var='date'>12</var>, <var data-var='time'>07:18</var> UTC</small><br><strong>Resolved</strong> - As of December 11.12.2023, 10:40 pm CET, there were no more disruptions. This incident has been resolved.<br /><br />Mews POS experienced an elevated volume of requests from unexpected sources. None of these requests are able to access the system itself, but they do create additional traffic on the network, leading to sporadic service degradation. <br />We can confirm that this is not an attempted data breach nor an attempt to gain access to the system. <br /><br />However, we are still investigating the source of these requests and continue to monitor and remediate as appropriate.</p><p><small>Dec <var data-var='date'>11</var>, <var data-var='time'>20:30</var> UTC</small><br><strong>Investigating</strong> - We're experiencing an elevated level of errors and a service disruption and are currently looking into the issue.<br /><br />Mews is experiencing an elevated volume of requests from unexpected sources. None of these requests are able to access the system itself, but they do create additional traffic on the network, leading to sporadic service degradation. <br />We can confirm that this is not an attempted data breach nor an attempt to gain access to the system. We are investigating the source of these requests and continue to monitor.</p>tag:status.bizzon.com,2005:Incident/191187802023-11-14T16:23:19Z2023-11-14T16:23:19ZDegraded service<p><small>Nov <var data-var='date'>14</var>, <var data-var='time'>16:23</var> UTC</small><br><strong>Resolved</strong> - The service has been fully restored and more information on this incident will be posted at a later date.</p><p><small>Nov <var data-var='date'>14</var>, <var data-var='time'>16:00</var> UTC</small><br><strong>Monitoring</strong> - A fix has been implemented and we are monitoring the results.</p><p><small>Nov <var data-var='date'>14</var>, <var data-var='time'>15:51</var> UTC</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'>15:28</var> UTC</small><br><strong>Investigating</strong> - Our team is identifying the cause and working on a solution. We will provide update as soon as possible.</p>tag:status.bizzon.com,2005:Incident/190623292023-11-08T19:55:31Z2023-11-08T20:59:00ZSeverely degraded app performance<p><small>Nov <var data-var='date'> 8</var>, <var data-var='time'>19:55</var> UTC</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Nov <var data-var='date'> 8</var>, <var data-var='time'>19:15</var> UTC</small><br><strong>Investigating</strong> - Severely degraded POS app performance lasting from 19:15 until 20:55 UTC. The service has been fully restored and more information on this incident will be posted at a later date.</p>tag:status.bizzon.com,2005:Incident/186870712023-10-05T07:06:22Z2023-10-05T07:06:22ZInaccurate sales report<p><small>Oct <var data-var='date'> 5</var>, <var data-var='time'>07:06</var> UTC</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Oct <var data-var='date'> 4</var>, <var data-var='time'>12:13</var> UTC</small><br><strong>Monitoring</strong> - Our team has implemented a fix and the report export functionality has been fully restored. We are monitoring the performance.</p><p><small>Oct <var data-var='date'> 4</var>, <var data-var='time'>10:28</var> UTC</small><br><strong>Investigating</strong> - Our downloadable sales reports are currently displaying inaccurate figures. Our developer team is investigating the root cause and will repair the reports as soon as possible.</p>tag:status.bizzon.com,2005:Incident/182579762023-08-25T14:57:20Z2023-08-25T14:57:20ZIssue with Zagrebačka Banka card reader transactions<p><small>Aug <var data-var='date'>25</var>, <var data-var='time'>14:57</var> UTC</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Aug <var data-var='date'>25</var>, <var data-var='time'>13:14</var> UTC</small><br><strong>Monitoring</strong> - The mPOS payments have been restored and we are now monitoring the behaviour</p><p><small>Aug <var data-var='date'>25</var>, <var data-var='time'>10:38</var> UTC</small><br><strong>Investigating</strong> - We are currently investigating this issue.</p><p><small>Aug <var data-var='date'>25</var>, <var data-var='time'>10:38</var> UTC</small><br><strong>Monitoring</strong> - A fix has been implemented and we are monitoring the results.</p><p><small>Aug <var data-var='date'>25</var>, <var data-var='time'>09:52</var> UTC</small><br><strong>Investigating</strong> - We are currently experiencing an issue that is affecting our ability to accept mPOS card transactions from Zagrebačka Banka card acquirer.<br /><br />We are investigating the root cause of this issue and closely monitoring the situation.</p>tag:status.bizzon.com,2005:Incident/178282062023-07-12T07:26:25Z2023-07-12T07:26:25ZTemporary service degradation<p><small>Jul <var data-var='date'>12</var>, <var data-var='time'>07:26</var> UTC</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Jul <var data-var='date'>11</var>, <var data-var='time'>21:36</var> UTC</small><br><strong>Monitoring</strong> - Temporary service degradation. The incident lasted between 19:44 UTC until 20:34 UTC. The service has been restored and we are monitoring the server performance.</p>tag:status.bizzon.com,2005:Incident/175840262023-06-16T12:31:56Z2023-06-16T12:31:56ZBizzon POS app not available in the Play Store<p><small>Jun <var data-var='date'>16</var>, <var data-var='time'>12:31</var> UTC</small><br><strong>Resolved</strong> - The Bizzon POS application has been restored in the Google Play Store.</p><p><small>Jun <var data-var='date'>16</var>, <var data-var='time'>07:24</var> UTC</small><br><strong>Monitoring</strong> - We have resolved the issue with Google and are now taking steps to make the application visible in the Play Store again.</p><p><small>Jun <var data-var='date'>15</var>, <var data-var='time'>15:33</var> UTC</small><br><strong>Identified</strong> - The Bizzon POS app is temporarily not available in the Play Store. We are working closely with Google to resolve the issue. <br /><br />Please reach out to our support for an alternative solution.</p>tag:status.bizzon.com,2005:Incident/165932062023-03-22T11:01:26Z2023-03-22T11:01:26ZDegraded Mastercard authorizations for Barclaycard merchants<p><small>Mar <var data-var='date'>22</var>, <var data-var='time'>11:01</var> UTC</small><br><strong>Resolved</strong> - This incident has been confirmed as resolved by Barclaycard.</p><p><small>Mar <var data-var='date'>22</var>, <var data-var='time'>08:45</var> UTC</small><br><strong>Monitoring</strong> - As of 00:38 CET this morning, the problem is resolved - Mastercard transactions from affected BINs are no longer declined.<br />We are still investigating the root cause with Barclaycard and will update the status when more info is available.</p><p><small>Mar <var data-var='date'>21</var>, <var data-var='time'>15:43</var> UTC</small><br><strong>Investigating</strong> - We are experiencing issues with Mastercard authorizations processed via Barclaycard. Approximately 30% of transactions of Mastercard are being rejected for all Barclaycard-enabled properties. Visa transactions are not affected, as well as other card acquirers. We have contacted Barclaycard and are investigating the issue on our part and will provide more information soon.</p>tag:status.bizzon.com,2005:Incident/162465852023-02-23T10:58:14Z2023-03-01T07:34:30ZSevere performance degradation<p><small>Feb <var data-var='date'>23</var>, <var data-var='time'>10:58</var> UTC</small><br><strong>Resolved</strong> - This incident has been resolved as there have been no disruptions since 09:36 UTC.</p><p><small>Feb <var data-var='date'>23</var>, <var data-var='time'>09:36</var> UTC</small><br><strong>Monitoring</strong> - We have identified the cause of the service disruption. A database migration caused the increased load on the database. This significantly increased the average duration of web requests which resulted in request queues being filled and the majority of web requests being rejected.<br /><br />The server operation has been fully restored. <br /><br />We will continue to investigate and monitor its performance.</p><p><small>Feb <var data-var='date'>23</var>, <var data-var='time'>09:07</var> UTC</small><br><strong>Investigating</strong> - As of 08:53 UTC, we are noticing a severe performance degradation of our servers.<br /><br />We are investigating the issue and will provide an update as soon as more information is available.</p>tag:status.bizzon.com,2005:Incident/159333762023-01-26T08:45:20Z2023-01-26T08:45:20ZBizzon app rollout 4.1.2 stopped<p><small>Jan <var data-var='date'>26</var>, <var data-var='time'>08:45</var> UTC</small><br><strong>Resolved</strong> - Bizzon v4.1.2.1 containing the hotfix for the layout display bug on phones is available on Play Store</p><p><small>Jan <var data-var='date'>25</var>, <var data-var='time'>16:26</var> UTC</small><br><strong>Update</strong> - We are continuing to investigate this issue.</p><p><small>Jan <var data-var='date'>25</var>, <var data-var='time'>16:08</var> UTC</small><br><strong>Investigating</strong> - Bizzon app rollout 4.1.2 stopped due to a bug in the layout display on Android phones. Tablet devices are not affected. The hotfix will be available as soon as possible.</p>tag:status.bizzon.com,2005:Incident/158717632023-01-25T10:00:48Z2023-01-25T10:00:48ZVersion 4.1.1.5 released<p><small>Jan <var data-var='date'>25</var>, <var data-var='time'>10:00</var> UTC</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Jan <var data-var='date'>18</var>, <var data-var='time'>11:47</var> UTC</small><br><strong>Monitoring</strong> - A new 4.1.1.5 version has been submitted to Play Store. This version contains improvements to the printing logic.</p>tag:status.bizzon.com,2005:Incident/158537372023-01-18T11:46:49Z2023-01-18T11:46:49ZBizzon app rollout 4.1.1.4 stopped<p><small>Jan <var data-var='date'>18</var>, <var data-var='time'>11:46</var> UTC</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Jan <var data-var='date'>16</var>, <var data-var='time'>12:50</var> UTC</small><br><strong>Update</strong> - We are continuing to monitor for any further issues.</p><p><small>Jan <var data-var='date'>16</var>, <var data-var='time'>12:49</var> UTC</small><br><strong>Update</strong> - We are continuing to monitor for any further issues.</p><p><small>Jan <var data-var='date'>16</var>, <var data-var='time'>12:16</var> UTC</small><br><strong>Monitoring</strong> - Due to previously unidentified side effects on certain devices, the rollout for the app v4.1.1.4 has been stopped and is not available on Google Play. Should any properties encounter blank printouts or any other order ticket printing issues after the update to versions 4.1.1.3 or 4.1.1.4 they are advised to immediately reach out to Bizzon support, so they can be provided with a rollback workaround.</p>tag:status.bizzon.com,2005:Incident/158366102023-01-16T12:15:36Z2023-01-16T12:15:36Z4.1.1.3 hotfix rollout stopped<p><small>Jan <var data-var='date'>16</var>, <var data-var='time'>12:15</var> UTC</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Jan <var data-var='date'>13</var>, <var data-var='time'>14:51</var> UTC</small><br><strong>Investigating</strong> - Due to previously unidentified side effects on certain devices, the rollout for the app v4.1.1.3 has been stopped and is not available on Google Play. Should any properties encounter blank printouts or any other order ticket printing issues after the update to version 4.1.1.3 they are advised to immediately reach out to Bizzon support, so they can be provided with a rollback workaround.</p>tag:status.bizzon.com,2005:Incident/158264122023-01-12T09:44:20Z2023-01-12T09:44:20ZWebView Printer issues update<p><small>Jan <var data-var='date'>12</var>, <var data-var='time'>09:44</var> UTC</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Jan <var data-var='date'>12</var>, <var data-var='time'>09:44</var> UTC</small><br><strong>Investigating</strong> - Bizzon version 4.1.1.3 has been submitted to the Play Store. This version contains the permanent fix for all issues caused by the recent WebView update by Google. All users are advised to update all Android devices as soon as possible, as this version guarantees to significantly increase the printing tasks' speed and prevent blank, supersized, or missent printouts. <br />Along with this feature, we've enabled the print progress dialog screen on all accounts. The print progress dialog screen increases the reliability of all printing tasks and enables all users to retry the printing tasks in case of failures due to temporary connectivity issues or any other external factor.</p>tag:status.bizzon.com,2005:Incident/157964622023-01-12T08:18:16Z2023-01-12T08:18:16ZWebView Printer issues update<p><small>Jan <var data-var='date'>12</var>, <var data-var='time'>08:18</var> UTC</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Jan <var data-var='date'> 7</var>, <var data-var='time'>12:00</var> UTC</small><br><strong>Monitoring</strong> - While we can confirm that the hotfix contained in the Bizzon version 4.1.1.2 minimizes the possibility of the recurrence of the printing issues caused by the recent WebView update by Google, there is a minimal possibility of this issue emerging due to various external factors on certain Android devices. <br />To prevent blank, supersized, or missent printouts, we advise restarting the app several times during the day, especially before or after the busiest hours. The clients who encounter the issues mentioned above on app version 4.1.1.2 are advised to immediately close and restart the app on all devices, as this will restore the correct printing behavior initiated from these devices.</p>tag:status.bizzon.com,2005:Incident/157836402023-01-05T22:00:56Z2023-01-06T08:54:24ZBizzon 4.1.1.2 version released containing the hotfix for the printing issue caused by WebView update<p><small>Jan <var data-var='date'> 5</var>, <var data-var='time'>22:00</var> UTC</small><br><strong>Resolved</strong> - A new 4.1.1.2 version was released containing the hotfix for the printing issue caused by the WebView update by Google, as the 4.1.1.1 version did not completely resolve the issue:<br />https://status.bizzon.com/incidents/3cgfwyq0ss87</p>tag:status.bizzon.com,2005:Incident/155695822022-12-16T17:00:16Z2022-12-19T12:40:28ZPrinting issues caused by Android WebView update<p><small>Dec <var data-var='date'>16</var>, <var data-var='time'>17:00</var> UTC</small><br><strong>Resolved</strong> - The problem: Google released the latest version of the Android WebView component (108) on the 30th of November. This version changed how web pages are cached, causing issues with Bizzon printing. As Google Play automatically started upgrading the WebView component on devices in your hotel, your staff started experiencing problems with printing.<br /><br />The Solution: We updated the part of the app that deals with printing to circumvent the new behavior of the WebView and released the hotfix version of the Bizzon app (v4.1.1.1) on Friday 16/12/2022.<br /><br />The cause: Bizzon uses the Android WebView component to print orders, receipts, and reports. The newest WebView broke the compatibility with the Bizzon app, causing the previously printed document sometimes to get printed on another printer. For example, the order printed on a receipt printer would afterward be printed on a kitchen printer and vice versa. Because of the lower resolution of kitchen printers, the order on the kitchen printer would appear magnified or empty.<br /><br />Since there was no warning from Google that breaking changes would be released, it took us some time to find the problem and fix it retroactively. We apologize for the problems that this has caused.</p>tag:status.bizzon.com,2005:Incident/132067562022-11-16T16:13:16Z2022-11-16T16:13:16ZPhone support not available<p><small>Nov <var data-var='date'>16</var>, <var data-var='time'>16:13</var> UTC</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Nov <var data-var='date'>16</var>, <var data-var='time'>15:30</var> UTC</small><br><strong>Monitoring</strong> - The root cause of the issue has been identified and the phone provider is restoring its service.</p><p><small>Nov <var data-var='date'>16</var>, <var data-var='time'>14:09</var> UTC</small><br><strong>Update</strong> - The root cause of the issue has been identified and the phone provider is restoring its service.</p><p><small>Nov <var data-var='date'>16</var>, <var data-var='time'>13:56</var> UTC</small><br><strong>Identified</strong> - Phone provider is currently investigating the issue</p><p><small>Nov <var data-var='date'>16</var>, <var data-var='time'>13:56</var> UTC</small><br><strong>Investigating</strong> - Phone support not available due to temporary phone provider issues</p>tag:status.bizzon.com,2005:Incident/122984132022-10-18T22:48:47Z2022-10-24T12:45:04ZSevere performance degradation<p><small>Oct <var data-var='date'>18</var>, <var data-var='time'>22:48</var> UTC</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Oct <var data-var='date'>18</var>, <var data-var='time'>22:19</var> UTC</small><br><strong>Monitoring</strong> - The server operation has been fully restored. We will continue to investigate and monitor its performance.</p><p><small>Oct <var data-var='date'>18</var>, <var data-var='time'>22:00</var> UTC</small><br><strong>Identified</strong> - We have identified the root cause for the issue.</p><p><small>Oct <var data-var='date'>18</var>, <var data-var='time'>21:34</var> UTC</small><br><strong>Update</strong> - We are continuing to investigate this issue.</p><p><small>Oct <var data-var='date'>18</var>, <var data-var='time'>20:50</var> UTC</small><br><strong>Investigating</strong> - As of 20:41 UTC, we are noticing a severe performance degradation of our servers. <br />We are investigating the issue and will provide an update as soon as more information is available.</p>tag:status.bizzon.com,2005:Incident/121987962022-10-17T19:05:26Z2022-10-24T12:44:32ZSevere performance degradation<p><small>Oct <var data-var='date'>17</var>, <var data-var='time'>19:05</var> UTC</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Oct <var data-var='date'>17</var>, <var data-var='time'>18:45</var> UTC</small><br><strong>Monitoring</strong> - The server operation has been fully restored. We will continue to investigate and monitor its performance.</p><p><small>Oct <var data-var='date'>17</var>, <var data-var='time'>17:45</var> UTC</small><br><strong>Update</strong> - We are continuing to investigate this issue.</p><p><small>Oct <var data-var='date'>17</var>, <var data-var='time'>16:26</var> UTC</small><br><strong>Investigating</strong> - As of 16:03 UTC, we are noticing a severe performance degradation of our servers. <br />We are investigating the issue and will provide an update as soon as more information is available.</p>tag:status.bizzon.com,2005:Incident/113151562022-09-29T18:28:46Z2022-09-29T18:28:46ZCard payment processing through Bambora is currently experiencing problems<p><small>Sep <var data-var='date'>29</var>, <var data-var='time'>18:28</var> UTC</small><br><strong>Resolved</strong> - We confirm that the service has been resumed. Payment functionality is now fully operational for all acquirers.<br /><br />This incident has been resolved. We apologize for any inconvenience caused by the service disruption.</p><p><small>Sep <var data-var='date'>29</var>, <var data-var='time'>16:57</var> UTC</small><br><strong>Monitoring</strong> - As of 18:47 CET, we see the transactions being approved again, but we still don't have an official update from the vendor.<br />We are monitoring the situation and will update you as soon as more information becomes available.</p><p><small>Sep <var data-var='date'>29</var>, <var data-var='time'>16:39</var> UTC</small><br><strong>Update</strong> - The vendor is still working on the solution. We will provide an update as soon as more information is available.</p><p><small>Sep <var data-var='date'>29</var>, <var data-var='time'>16:08</var> UTC</small><br><strong>Update</strong> - The vendor used by Bambora is confirming the issue:<br />Description: We have noticed that there are interruptions in the network connections that may affect our authorization service. Some of our customers may experience sporadic interruptions.<br />Status: Troubleshooting is ongoing, next status at 18:20 CET</p><p><small>Sep <var data-var='date'>29</var>, <var data-var='time'>15:48</var> UTC</small><br><strong>Update</strong> - Bambora confirms an ongoing issue with an external payment provider.</p><p><small>Sep <var data-var='date'>29</var>, <var data-var='time'>15:44</var> UTC</small><br><strong>Identified</strong> - Processing through Bambora is currently experiencing problems due to unavailability of downstream services. We monitor the situation and will provide more information when we receive updates from Bambora. Other acquirers are not affected.</p>tag:status.bizzon.com,2005:Incident/108819032022-08-23T07:44:29Z2022-08-23T07:44:29ZInvoice fiscalization not working in Croatia<p><small>Aug <var data-var='date'>23</var>, <var data-var='time'>07:44</var> UTC</small><br><strong>Resolved</strong> - The issue has been fixed.</p><p><small>Aug <var data-var='date'>23</var>, <var data-var='time'>05:57</var> UTC</small><br><strong>Monitoring</strong> - The hotfix has been released and we are seeing transaction submissions going through to Fina again.</p><p><small>Aug <var data-var='date'>22</var>, <var data-var='time'>09:24</var> UTC</small><br><strong>Update</strong> - We have narrowed down the root cause to an underlying HTTP library update, which broke the TLS validation when submitting invoice data to the tax office (Fina).<br /><br />A hotfix release is being prepared and it is scheduled for tomorrow morning (23 August 2022).<br /><br />All non-fiscalized invoices will be submitted automatically after the hotfix release.</p><p><small>Aug <var data-var='date'>22</var>, <var data-var='time'>09:15</var> UTC</small><br><strong>Identified</strong> - We are looking into the increased error count around fiscalization in Croatia.<br /><br />All non-fiscalized invoices will be submitted automatically after a hotfix release.</p>tag:status.bizzon.com,2005:Incident/108812962022-08-22T06:15:00Z2022-08-22T07:23:21ZPerformance degradation after a server update<p><small>Aug <var data-var='date'>22</var>, <var data-var='time'>06:15</var> UTC</small><br><strong>Resolved</strong> - Performance degradation after a server update 6:15 - 6:35 UTC</p>