MATCHi AB Status Page

Apr 9, 2026 · resolved Apr 10

All bookings have now reach the hardware and the incident is resolved.

Mar 29, 2026 · resolved Mar 29

The issue has been identified and resolved. A recent update to one of our payment processing components was responsible for the disruption experienced by Android users. Google Pay should now be working as expected. We apologise for any inconvenience caused.

Mar 15, 2026 · resolved Mar 15

## **Additional information on the incident regarding Android login issues** After further investigation, we have tracked down the root cause of the login issues affecting Android users recently. ### **Here's what caused the recent login issues and what we've done about it** The problem was caused by an update we made to our login system which unintentionally logged users out of their existing sessions. Some Android users then got stuck in a login loop when trying to sign back in. Most affected users were able to log back in normally, and the issue has been resolving itself as new sessions are created. We have now put a fix in place to prevent Android users from getting stuck in a login loop, and are monitoring it closely. We have also taken steps to ensure that a similar update cannot cause this kind of disruption in the future. We apologise for the inconvenience and for the confusion caused by our initial update. Thank you for your patience.

Feb 28, 2026 · resolved Feb 28

The issue affecting membership auto-renewals scheduled for yesterday has now been resolved. Following recent system-wide improvements, an unintended malfunction occurred in the automated membership renewal job beginning on the 25th and resulted in some renewals not being processed as expected. While the number of impacted renewals was initially very small, the issue also affected some more renewals scheduled yesterday. We have since identified the root cause, deployed the necessary fixes, and verified that the renewal process is now functioning correctly. All affected memberships have now been updated automatically. We sincerely apologize for the disruption and appreciate your understanding.

Feb 20, 2026 · resolved Feb 20

This incident has been resolved.