Incidents reported on status page for cm https://status.cmd.tw/en https://d1lppblt9t2x15.cloudfront.net/logos/0114faeacc84449da86c39c9ad9ef02a.png https://status.cmd.tw/en en https://status.cmd.tw/en Mon, 26 May 2025 09:35:02 +0000 https://status.cmd.tw/en#ff4d7aa8c164757858a32ed8b3e4980286716324f7e21231744585a36e6094e2 cmProfile recovered https://status.cmd.tw/en Mon, 26 May 2025 09:32:25 +0000 https://status.cmd.tw/en#ff4d7aa8c164757858a32ed8b3e4980286716324f7e21231744585a36e6094e2 cmProfile went down https://status.cmd.tw/en Wed, 21 May 2025 16:17:40 +0000 https://status.cmd.tw/en#e4b628e34612411cc1bb11f5de0f9fa4f1cc599a61f2b1740d1eb6ec22efad5b cmWeblog recovered https://status.cmd.tw/en Wed, 21 May 2025 16:06:37 +0000 https://status.cmd.tw/en#e4b628e34612411cc1bb11f5de0f9fa4f1cc599a61f2b1740d1eb6ec22efad5b cmWeblog went down https://status.cmd.tw/en Mon, 19 May 2025 03:31:47 +0000 https://status.cmd.tw/en#bcc6b509a0f950ec660cc6435885bb78638bda806a899ccf1e89ab7f4c820184 cmProfile recovered https://status.cmd.tw/en Mon, 19 May 2025 03:29:02 +0000 https://status.cmd.tw/en#bcc6b509a0f950ec660cc6435885bb78638bda806a899ccf1e89ab7f4c820184 cmProfile went down https://status.cmd.tw/en Tue, 13 May 2025 10:07:39 +0000 https://status.cmd.tw/en#3d41129281c86db648ee610770d27bdf0883d130e122a5ed5acf3e40480aa87c cmProfile recovered https://status.cmd.tw/en Tue, 13 May 2025 10:05:18 +0000 https://status.cmd.tw/en#3d41129281c86db648ee610770d27bdf0883d130e122a5ed5acf3e40480aa87c cmProfile went down https://status.cmd.tw/en Wed, 23 Apr 2025 07:46:47 +0000 https://status.cmd.tw/en#fb95f2ad8f41548e2632eefa3964193747c7c585476f73fca6617d5d11a0be32 cmProfile recovered https://status.cmd.tw/en Wed, 23 Apr 2025 07:44:40 +0000 https://status.cmd.tw/en#fb95f2ad8f41548e2632eefa3964193747c7c585476f73fca6617d5d11a0be32 cmProfile went down https://status.cmd.tw/en Mon, 21 Apr 2025 21:19:12 +0000 https://status.cmd.tw/en#4ee8b4aaa2d7b9db443197bfbde9bd150b9d4377e5fa39beae76e61b20434568 Azure Korea Central went down https://status.cmd.tw/en Sun, 06 Apr 2025 15:52:32 +0000 https://status.cmd.tw/en#ab53c6ca20564b507f9d86f8c428b1a0041945e6cbc689eb8ba97d14f2e141f9 cmWeblog recovered https://status.cmd.tw/en Sun, 06 Apr 2025 15:47:31 +0000 https://status.cmd.tw/en#ab53c6ca20564b507f9d86f8c428b1a0041945e6cbc689eb8ba97d14f2e141f9 cmWeblog went down https://status.cmd.tw/en Sat, 29 Mar 2025 12:04:19 +0000 https://status.cmd.tw/en#477caa18ddac24dbf7c7a8c5a6132c9ad385cc46328f4bf76477583571d42595 cmProfile recovered https://status.cmd.tw/en Tue, 11 Mar 2025 01:30:43 +0000 https://status.cmd.tw/en#477caa18ddac24dbf7c7a8c5a6132c9ad385cc46328f4bf76477583571d42595 cmProfile went down https://status.cmd.tw/en Tue, 11 Mar 2025 00:35:48 +0000 https://status.cmd.tw/en#2275690396654d464b8d945e22e7c6dfa188d087946998b259ae8fe6ec2acf9b cmProfile recovered https://status.cmd.tw/en Tue, 11 Mar 2025 00:20:57 +0000 https://status.cmd.tw/en#2275690396654d464b8d945e22e7c6dfa188d087946998b259ae8fe6ec2acf9b cmProfile went down