Incidents | AfterTicket Team Incidents reported on status page for AfterTicket Team https://status.afterticket.org/ en API recovered https://status.afterticket.org/ Sun, 14 Jun 2026 09:01:49 +0000 https://status.afterticket.org/#ede2bbe6947c451a79c9119681cf501ab9dc5d785b76da4bf88311fbab5dcf12 API recovered Hong Kong recovered https://status.afterticket.org/ Sun, 14 Jun 2026 09:00:18 +0000 https://status.afterticket.org/#f42bbb83f802ccd669f92dc66c149dfe80710d20248f4af85b97c0d493b3dee8 Hong Kong recovered Dashboard recovered https://status.afterticket.org/ Sun, 14 Jun 2026 09:00:01 +0000 https://status.afterticket.org/#d16e3d7083ce543f2e80bcab17f222011260d4340f8bd88b80ad9a43d93817fc Dashboard recovered Dashboard went down https://status.afterticket.org/ Sun, 14 Jun 2026 08:55:37 +0000 https://status.afterticket.org/#d16e3d7083ce543f2e80bcab17f222011260d4340f8bd88b80ad9a43d93817fc Dashboard went down Hong Kong went down https://status.afterticket.org/ Sun, 14 Jun 2026 08:54:41 +0000 https://status.afterticket.org/#f42bbb83f802ccd669f92dc66c149dfe80710d20248f4af85b97c0d493b3dee8 Hong Kong went down API went down https://status.afterticket.org/ Sun, 14 Jun 2026 08:53:24 +0000 https://status.afterticket.org/#ede2bbe6947c451a79c9119681cf501ab9dc5d785b76da4bf88311fbab5dcf12 API went down