Incidents reported on status page for AfterTicket Team https://status.afterticket.org/ en https://status.afterticket.org/ Thu, 16 Jul 2026 02:05:36 +0000 https://status.afterticket.org/#e39fa01aca5290b2fa9223a887f83d6e5eccbfe8a708d61a3d22b8b8c300feed Dashboard went down https://status.afterticket.org/ Thu, 16 Jul 2026 02:03:38 +0000 https://status.afterticket.org/#40fc809c5802f7adcb4f0ec6855e0b584c581f9708a861cdba19a2554b454a39 Hong Kong went down https://status.afterticket.org/ Thu, 16 Jul 2026 02:02:25 +0000 https://status.afterticket.org/#e7c37e5da41862f8fe5e2b91f06e78fd1ba01eea4a961886d43a1dfcbd8c9a86 API went down https://status.afterticket.org/ Wed, 15 Jul 2026 15:27:42 +0000 https://status.afterticket.org/#bc972fac214d495a6b5364744c1be718b320b619a728ac0773213e7f1895af09 API recovered https://status.afterticket.org/ Wed, 15 Jul 2026 15:23:28 +0000 https://status.afterticket.org/#bc972fac214d495a6b5364744c1be718b320b619a728ac0773213e7f1895af09 API went down https://status.afterticket.org/ Wed, 15 Jul 2026 15:15:02 +0000 https://status.afterticket.org/#46062ec77f731675da512d60942575dbba4b57263630ce2aaff853740324d93a Dashboard recovered https://status.afterticket.org/ Wed, 15 Jul 2026 15:10:50 +0000 https://status.afterticket.org/#46062ec77f731675da512d60942575dbba4b57263630ce2aaff853740324d93a Dashboard went down https://status.afterticket.org/ Thu, 09 Jul 2026 12:00:03 +0000 https://status.afterticket.org/#067995cb0797409d6246b7f30d931b2a43316a4cbf889fbd1c59286c40f6a4c8 Dashboard recovered https://status.afterticket.org/ Thu, 09 Jul 2026 11:58:58 +0000 https://status.afterticket.org/#2a573f3748a32cb2c82cd5ed696a7a1ff7759df73ae1befbb258880812d0e577 API recovered https://status.afterticket.org/ Thu, 09 Jul 2026 11:57:27 +0000 https://status.afterticket.org/#f6353a20231eb82d7406cba2fc47192fd2b4b87c768701da91142bf3d515d360 Hong Kong recovered https://status.afterticket.org/ Thu, 09 Jul 2026 06:21:43 +0000 https://status.afterticket.org/#f6353a20231eb82d7406cba2fc47192fd2b4b87c768701da91142bf3d515d360 Hong Kong went down https://status.afterticket.org/ Thu, 09 Jul 2026 06:20:36 +0000 https://status.afterticket.org/#2a573f3748a32cb2c82cd5ed696a7a1ff7759df73ae1befbb258880812d0e577 API went down https://status.afterticket.org/ Thu, 09 Jul 2026 06:20:33 +0000 https://status.afterticket.org/#067995cb0797409d6246b7f30d931b2a43316a4cbf889fbd1c59286c40f6a4c8 Dashboard went down https://status.afterticket.org/ Wed, 08 Jul 2026 08:00:08 +0000 https://status.afterticket.org/#055bdf4bcf41dc8b85ff21c9706de3d6b6ab9ab0608d662ab20f3142ba1d28ac Dashboard recovered https://status.afterticket.org/ Wed, 08 Jul 2026 07:55:36 +0000 https://status.afterticket.org/#055bdf4bcf41dc8b85ff21c9706de3d6b6ab9ab0608d662ab20f3142ba1d28ac Dashboard went down https://status.afterticket.org/ Sun, 05 Jul 2026 06:43:51 +0000 https://status.afterticket.org/#1f2c996878fe1815fc9efb507cd92b03baabecd16fcda6934717b917a8c9caf0 API recovered https://status.afterticket.org/ Sun, 05 Jul 2026 06:40:50 +0000 https://status.afterticket.org/#1f2c996878fe1815fc9efb507cd92b03baabecd16fcda6934717b917a8c9caf0 API went down https://status.afterticket.org/ Fri, 03 Jul 2026 00:35:23 +0000 https://status.afterticket.org/#70dba275a6ad4f14b1f0e5e97d530504a1956fb0e73b53cbc6555272b71256a1 API recovered https://status.afterticket.org/ Fri, 03 Jul 2026 00:32:31 +0000 https://status.afterticket.org/#70dba275a6ad4f14b1f0e5e97d530504a1956fb0e73b53cbc6555272b71256a1 API went down https://status.afterticket.org/ Thu, 02 Jul 2026 23:59:05 +0000 https://status.afterticket.org/#6b70b160b03322a15bbcb36b0adcc6b9a550ca2c3caef127eb680562ffcf4762 API recovered https://status.afterticket.org/ Thu, 02 Jul 2026 23:56:26 +0000 https://status.afterticket.org/#6b70b160b03322a15bbcb36b0adcc6b9a550ca2c3caef127eb680562ffcf4762 API went down https://status.afterticket.org/ Thu, 02 Jul 2026 16:55:49 +0000 https://status.afterticket.org/#480d2cadf7fab67b4a013996b9c9a05b69700017df7bd2b13e48d482eb6838e0 API recovered https://status.afterticket.org/ Thu, 02 Jul 2026 16:53:28 +0000 https://status.afterticket.org/#480d2cadf7fab67b4a013996b9c9a05b69700017df7bd2b13e48d482eb6838e0 API went down https://status.afterticket.org/ Wed, 01 Jul 2026 08:40:06 +0000 https://status.afterticket.org/#cbdbd0030a08358e6e61b22025b0a9346b0cd0687cb77149c3d8a00331b958e0 Dashboard recovered https://status.afterticket.org/ Wed, 01 Jul 2026 08:36:05 +0000 https://status.afterticket.org/#cbdbd0030a08358e6e61b22025b0a9346b0cd0687cb77149c3d8a00331b958e0 Dashboard went down https://status.afterticket.org/ Sun, 28 Jun 2026 12:27:28 +0000 https://status.afterticket.org/#1a1ed99d420faa6a5f71b54ba7114cc5d86534e5683846c4e488a28755766182 Hong Kong recovered https://status.afterticket.org/ Sun, 28 Jun 2026 12:24:39 +0000 https://status.afterticket.org/#1a1ed99d420faa6a5f71b54ba7114cc5d86534e5683846c4e488a28755766182 Hong Kong went down https://status.afterticket.org/ Mon, 22 Jun 2026 08:57:25 +0000 https://status.afterticket.org/#b83c99ebb3944ac39d8de57c88b1761e1682232b9f3c0ff5bf926f54c82a0ff2 API recovered https://status.afterticket.org/ Mon, 22 Jun 2026 08:47:28 +0000 https://status.afterticket.org/#b83c99ebb3944ac39d8de57c88b1761e1682232b9f3c0ff5bf926f54c82a0ff2 API went down https://status.afterticket.org/ Sun, 21 Jun 2026 11:42:10 +0000 https://status.afterticket.org/#cf19070895af86cbc1a149221c07583e6bd4b7c1fc583ff8488eddd28bd9020d Dashboard recovered https://status.afterticket.org/ Sun, 21 Jun 2026 11:40:46 +0000 https://status.afterticket.org/#61d25e6dd1d8ed6a4442ee66e7313d385b093fa9bc6942e3d35153b82408efc7 API recovered https://status.afterticket.org/ Sun, 21 Jun 2026 11:35:48 +0000 https://status.afterticket.org/#61d25e6dd1d8ed6a4442ee66e7313d385b093fa9bc6942e3d35153b82408efc7 API went down https://status.afterticket.org/ Sun, 21 Jun 2026 11:35:42 +0000 https://status.afterticket.org/#cf19070895af86cbc1a149221c07583e6bd4b7c1fc583ff8488eddd28bd9020d Dashboard went down https://status.afterticket.org/ Fri, 19 Jun 2026 20:55:08 +0000 https://status.afterticket.org/#512d97d5cb461eff019f352f3eeab706da6f25d9476403a319c8f0b9bae9f144 Dashboard recovered https://status.afterticket.org/ Fri, 19 Jun 2026 20:50:04 +0000 https://status.afterticket.org/#512d97d5cb461eff019f352f3eeab706da6f25d9476403a319c8f0b9bae9f144 Dashboard went down https://status.afterticket.org/ Thu, 18 Jun 2026 17:16:50 +0000 https://status.afterticket.org/#9c4e57eca64a0f94d72ebd2bbc875d6fec533aae27590eac4a2dd1528d27fb6e API recovered https://status.afterticket.org/ Thu, 18 Jun 2026 17:14:18 +0000 https://status.afterticket.org/#9c4e57eca64a0f94d72ebd2bbc875d6fec533aae27590eac4a2dd1528d27fb6e API went down https://status.afterticket.org/ Sun, 14 Jun 2026 09:01:49 +0000 https://status.afterticket.org/#ede2bbe6947c451a79c9119681cf501ab9dc5d785b76da4bf88311fbab5dcf12 API recovered https://status.afterticket.org/ Sun, 14 Jun 2026 09:00:18 +0000 https://status.afterticket.org/#f42bbb83f802ccd669f92dc66c149dfe80710d20248f4af85b97c0d493b3dee8 Hong Kong recovered https://status.afterticket.org/ Sun, 14 Jun 2026 09:00:01 +0000 https://status.afterticket.org/#d16e3d7083ce543f2e80bcab17f222011260d4340f8bd88b80ad9a43d93817fc Dashboard recovered https://status.afterticket.org/ Sun, 14 Jun 2026 08:55:37 +0000 https://status.afterticket.org/#d16e3d7083ce543f2e80bcab17f222011260d4340f8bd88b80ad9a43d93817fc Dashboard went down https://status.afterticket.org/ Sun, 14 Jun 2026 08:54:41 +0000 https://status.afterticket.org/#f42bbb83f802ccd669f92dc66c149dfe80710d20248f4af85b97c0d493b3dee8 Hong Kong went down https://status.afterticket.org/ Sun, 14 Jun 2026 08:53:24 +0000 https://status.afterticket.org/#ede2bbe6947c451a79c9119681cf501ab9dc5d785b76da4bf88311fbab5dcf12 API went down