Mobi2Go - Status of Services
All Systems Operational

About This Site

This page provides an overview of Mobi2Go's core systems and their current status. Subscribe above to be automatically notified of any system issues.

Admin   ? Operational
Customer storefront and apps   Operational
API   Operational
Email and notifications   Operational
POS integrations   Operational
Payment Gateways Operational
Payment Express   Operational
Paystation   Operational
Stripe   Operational
Braintree   Operational
Add-Ons   Operational
Partner Portal   Operational
Support Portal   Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
System Metrics Month Week Day
Request Volume
Fetching
Response Time
Fetching
Past Incidents
Dec 17, 2017

No incidents reported today.

Dec 16, 2017

No incidents reported.

Dec 15, 2017

No incidents reported.

Dec 14, 2017

No incidents reported.

Dec 13, 2017

No incidents reported.

Dec 12, 2017

No incidents reported.

Dec 11, 2017

No incidents reported.

Dec 10, 2017

No incidents reported.

Dec 9, 2017

No incidents reported.

Dec 8, 2017

No incidents reported.

Dec 7, 2017

No incidents reported.

Dec 6, 2017

No incidents reported.

Dec 5, 2017
Resolved - On Dec 4 at 15:32pm NZT, and for approximately 5 minutes, we experienced elevated error rates on our API. Unfortunately, some failed API requests were incorrectly returning a header which indicated the request had succeeded (an HTTP 200 response code), rather than the HTTP 500 response code that should have accompanied these errors.

A number of Orders for Windows clients received these incorrect responses to their request for dispatcher settings, and understood this response to mean they should reset their settings, and switch to the default printing mode.

To resolve the issue at the time we had to either update the Orders for Windows settings or remotely force a full settings refresh.

We have resolved the core system issue to ensure all API responses return the correct response code, which will ensure this particular issue cannot re-occur. We've also begun additional mitigations to ensure no other, related issues will happen in future:
1) Update Orders for Windows to ensure it only change when explicitly told to change to Print mode
2) Improve our ability to trigger a remote settings refresh for connected clients.
3) Add dispatcher status to your dashboards
Dec 5, 21:58 NZDT
Identified - Please check the Orders for Windows application in your stores to ensure that it is correctly printing or sending the orders to Pixelpoint. In particular, note that some PixelPoint stores may have been switched to printer settings.

We are investigating how this happened and will update when we have more information. We apologise for the inconvenience.
Dec 4, 18:01 NZDT
Dec 3, 2017

No incidents reported.