Incidents reported on status page for cm https://status.cmd.tw/zh https://d1lppblt9t2x15.cloudfront.net/logos/0114faeacc84449da86c39c9ad9ef02a.png https://status.cmd.tw/zh zh https://status.cmd.tw/zh Sat, 18 Oct 2025 04:43:15 +0000 https://status.cmd.tw/zh#66e95559b77c2f03ba552fd4a5362939780236a830bf8e3ac97ce2146377e973 AWS Tokyo went down https://status.cmd.tw/zh Sat, 18 Oct 2025 04:25:08 +0000 https://status.cmd.tw/zh#2fc831ea29219118550d923c8cf167c04fac9149c4456a70925edf94edf49b9f AWS Tokyo recovered https://status.cmd.tw/zh Wed, 15 Oct 2025 23:37:20 +0000 https://status.cmd.tw/zh#2fc831ea29219118550d923c8cf167c04fac9149c4456a70925edf94edf49b9f AWS Tokyo went down https://status.cmd.tw/zh Wed, 15 Oct 2025 21:43:13 +0000 https://status.cmd.tw/zh#ec09acf5c3859eb4ad3a9c395ddaed7f5392c6528161d4b9ae27859fb0cd364e AWS Tokyo recovered https://status.cmd.tw/zh Wed, 15 Oct 2025 11:01:10 +0000 https://status.cmd.tw/zh#ec09acf5c3859eb4ad3a9c395ddaed7f5392c6528161d4b9ae27859fb0cd364e AWS Tokyo went down https://status.cmd.tw/zh Wed, 15 Oct 2025 10:04:12 +0000 https://status.cmd.tw/zh#9eef3510df80aa98ed913f58b7a7f0522b471ec844ac2291626862709cbaafd1 AWS Tokyo recovered https://status.cmd.tw/zh Wed, 15 Oct 2025 02:42:02 +0000 https://status.cmd.tw/zh#9eef3510df80aa98ed913f58b7a7f0522b471ec844ac2291626862709cbaafd1 AWS Tokyo went down https://status.cmd.tw/zh Wed, 15 Oct 2025 02:24:44 +0000 https://status.cmd.tw/zh#580c07dbe6dbf4ede206bab80b7f9e6dc3aee4d9dd5843d8492833ea1bcccc4f AWS Tokyo recovered https://status.cmd.tw/zh Sat, 20 Sep 2025 14:54:58 +0000 https://status.cmd.tw/zh#580c07dbe6dbf4ede206bab80b7f9e6dc3aee4d9dd5843d8492833ea1bcccc4f AWS Tokyo went down https://status.cmd.tw/zh Sat, 20 Sep 2025 14:48:49 +0000 https://status.cmd.tw/zh#f53341e40b456e4fb12c8f032f09582a110d075343e0307637b19466ce6ed7fd AWS Tokyo recovered https://status.cmd.tw/zh Sat, 20 Sep 2025 04:39:47 +0000 https://status.cmd.tw/zh#f53341e40b456e4fb12c8f032f09582a110d075343e0307637b19466ce6ed7fd AWS Tokyo went down https://status.cmd.tw/zh Sat, 20 Sep 2025 04:21:39 +0000 https://status.cmd.tw/zh#66a7cb3bd18a349c84f3a1c34c9033ebe200c798db3d3fe7d99b5a9696f377c9 AWS Tokyo recovered https://status.cmd.tw/zh Thu, 18 Sep 2025 13:15:52 +0000 https://status.cmd.tw/zh#66a7cb3bd18a349c84f3a1c34c9033ebe200c798db3d3fe7d99b5a9696f377c9 AWS Tokyo went down https://status.cmd.tw/zh Thu, 18 Sep 2025 13:00:44 +0000 https://status.cmd.tw/zh#2fc87fe3c79a7e4cae015bf403b4a7f5000ffcdbfc0b39e4b43d9fc2245dcadd AWS Tokyo recovered https://status.cmd.tw/zh Mon, 15 Sep 2025 05:45:56 +0000 https://status.cmd.tw/zh#2fc87fe3c79a7e4cae015bf403b4a7f5000ffcdbfc0b39e4b43d9fc2245dcadd AWS Tokyo went down https://status.cmd.tw/zh Mon, 15 Sep 2025 05:42:38 +0000 https://status.cmd.tw/zh#cf2dddfe86bfe10a18b18dc422596b5826efa385a81adef208bc799c677a39b7 AWS Tokyo recovered https://status.cmd.tw/zh Sun, 14 Sep 2025 16:51:42 +0000 https://status.cmd.tw/zh#cf2dddfe86bfe10a18b18dc422596b5826efa385a81adef208bc799c677a39b7 AWS Tokyo went down https://status.cmd.tw/zh Tue, 09 Sep 2025 05:20:08 +0000 https://status.cmd.tw/zh#ca50f33a850fcf96b086213d80b4d8f88758b6d82dbca6daff12fbd46329b4a9 AWS Tokyo recovered https://status.cmd.tw/zh Sun, 07 Sep 2025 05:44:44 +0000 https://status.cmd.tw/zh#ca50f33a850fcf96b086213d80b4d8f88758b6d82dbca6daff12fbd46329b4a9 AWS Tokyo went down https://status.cmd.tw/zh Sun, 07 Sep 2025 00:43:48 +0000 https://status.cmd.tw/zh#41f6b9122f27c1a0d8232b69688705053e0d15862d2983110b74ce59eba2f63c AWS Tokyo recovered https://status.cmd.tw/zh Sat, 06 Sep 2025 01:25:44 +0000 https://status.cmd.tw/zh#41f6b9122f27c1a0d8232b69688705053e0d15862d2983110b74ce59eba2f63c AWS Tokyo went down https://status.cmd.tw/zh Sat, 06 Sep 2025 01:13:31 +0000 https://status.cmd.tw/zh#4e2437b1a7fa0954d9da631b5993ecf33072afc23346f53a0655367ef5e2c8d8 AWS Tokyo recovered https://status.cmd.tw/zh Thu, 04 Sep 2025 00:51:42 +0000 https://status.cmd.tw/zh#4e2437b1a7fa0954d9da631b5993ecf33072afc23346f53a0655367ef5e2c8d8 AWS Tokyo went down https://status.cmd.tw/zh Thu, 04 Sep 2025 00:36:39 +0000 https://status.cmd.tw/zh#287924896b53a3f026f71c60e8e721cdcdda2bcbd7c0a609c36ffb52c4ff05e4 AWS Tokyo recovered https://status.cmd.tw/zh Tue, 02 Sep 2025 01:11:51 +0000 https://status.cmd.tw/zh#287924896b53a3f026f71c60e8e721cdcdda2bcbd7c0a609c36ffb52c4ff05e4 AWS Tokyo went down https://status.cmd.tw/zh Tue, 02 Sep 2025 01:05:38 +0000 https://status.cmd.tw/zh#3f34c2ffbab9c785ca9c62bba43f555c10ba280a1c828696979086653b47a5dd AWS Tokyo recovered https://status.cmd.tw/zh Sun, 31 Aug 2025 12:34:00 +0000 https://status.cmd.tw/zh#3f34c2ffbab9c785ca9c62bba43f555c10ba280a1c828696979086653b47a5dd AWS Tokyo went down https://status.cmd.tw/zh Sun, 31 Aug 2025 11:15:48 +0000 https://status.cmd.tw/zh#172ffae803a4c9a9b6d40fdcf7c7573660833091b4a236183a3411b1e7c7d656 AWS Tokyo recovered https://status.cmd.tw/zh Sat, 30 Aug 2025 06:51:56 +0000 https://status.cmd.tw/zh#172ffae803a4c9a9b6d40fdcf7c7573660833091b4a236183a3411b1e7c7d656 AWS Tokyo went down https://status.cmd.tw/zh Sat, 30 Aug 2025 06:48:44 +0000 https://status.cmd.tw/zh#bcb82374766e8e28f4ef63e366a4c8ba069486fcc9f12337d355ccca256d8e0c AWS Tokyo recovered https://status.cmd.tw/zh Sat, 30 Aug 2025 02:33:42 +0000 https://status.cmd.tw/zh#bcb82374766e8e28f4ef63e366a4c8ba069486fcc9f12337d355ccca256d8e0c AWS Tokyo went down https://status.cmd.tw/zh Sat, 30 Aug 2025 02:21:42 +0000 https://status.cmd.tw/zh#8e790443c60febe93b0dad30b9bef1f76c39ee1b28cbb9c6808beea4c2765ed8 AWS Tokyo recovered https://status.cmd.tw/zh Thu, 28 Aug 2025 20:10:40 +0000 https://status.cmd.tw/zh#8e790443c60febe93b0dad30b9bef1f76c39ee1b28cbb9c6808beea4c2765ed8 AWS Tokyo went down https://status.cmd.tw/zh Thu, 28 Aug 2025 19:58:34 +0000 https://status.cmd.tw/zh#d1065b20e7ede25e9f8f1045172b97ff7ab508633848eb566b565cae4a3387ed AWS Tokyo recovered https://status.cmd.tw/zh Thu, 28 Aug 2025 04:04:04 +0000 https://status.cmd.tw/zh#d1065b20e7ede25e9f8f1045172b97ff7ab508633848eb566b565cae4a3387ed AWS Tokyo went down https://status.cmd.tw/zh Thu, 28 Aug 2025 03:42:46 +0000 https://status.cmd.tw/zh#91caeb27137732693972d3b314344e49d862e7d0ba7db99f16d531fd1e9e0a3f AWS Tokyo recovered https://status.cmd.tw/zh Mon, 25 Aug 2025 18:45:09 +0000 https://status.cmd.tw/zh#91caeb27137732693972d3b314344e49d862e7d0ba7db99f16d531fd1e9e0a3f AWS Tokyo went down https://status.cmd.tw/zh Mon, 25 Aug 2025 18:41:54 +0000 https://status.cmd.tw/zh#3658a255f19bd5dbb21e03a6ea4131591faaed72aceb488cbc295bc8cf9f58f0 AWS Tokyo recovered https://status.cmd.tw/zh Sun, 24 Aug 2025 08:13:19 +0000 https://status.cmd.tw/zh#3658a255f19bd5dbb21e03a6ea4131591faaed72aceb488cbc295bc8cf9f58f0 AWS Tokyo went down https://status.cmd.tw/zh Sun, 24 Aug 2025 07:55:10 +0000 https://status.cmd.tw/zh#4a6f84194896fc2b4eb6764b0a756027853f650ec98f2a4e9ab1d3c519ff2ccf AWS Tokyo recovered https://status.cmd.tw/zh Sun, 24 Aug 2025 00:28:15 +0000 https://status.cmd.tw/zh#4a6f84194896fc2b4eb6764b0a756027853f650ec98f2a4e9ab1d3c519ff2ccf AWS Tokyo went down https://status.cmd.tw/zh Sun, 24 Aug 2025 00:22:11 +0000 https://status.cmd.tw/zh#ab64b2f210ec61f0afe0bc30a6e273bca87c0f5b7a7f71d7c4d651527c4566c0 AWS Tokyo recovered https://status.cmd.tw/zh Sat, 16 Aug 2025 19:00:10 +0000 https://status.cmd.tw/zh#ab64b2f210ec61f0afe0bc30a6e273bca87c0f5b7a7f71d7c4d651527c4566c0 AWS Tokyo went down https://status.cmd.tw/zh Sat, 16 Aug 2025 18:56:59 +0000 https://status.cmd.tw/zh#c78d94986898bbad36fcdc3e75107601f4331decca4f414a6de5136a78588c61 AWS Tokyo recovered https://status.cmd.tw/zh Sat, 16 Aug 2025 12:12:09 +0000 https://status.cmd.tw/zh#c78d94986898bbad36fcdc3e75107601f4331decca4f414a6de5136a78588c61 AWS Tokyo went down https://status.cmd.tw/zh Sat, 16 Aug 2025 12:08:59 +0000 https://status.cmd.tw/zh#9c337372d339db56dd1a5faa2e89736b607fdbe3c29f647bc949c2a3a54bf9be AWS Tokyo recovered https://status.cmd.tw/zh Sun, 20 Jul 2025 08:34:44 +0000 https://status.cmd.tw/zh#9c337372d339db56dd1a5faa2e89736b607fdbe3c29f647bc949c2a3a54bf9be AWS Tokyo went down