Incidents reported on status page for Sakamoto Network Latency Grapher https://status.sakamoto.blog/ https://d1lppblt9t2x15.cloudfront.net/logos/e4d1ff76cf83d3c035042c4054c5f8dd.jpeg https://status.sakamoto.blog/ en https://status.sakamoto.blog/incident/723593 Sat, 13 Sep 2025 18:07:29 -0000 https://status.sakamoto.blog/incident/723593#f3af108b37a14a04b7c10965281bcae8ed57f011dd5ec42e5c3008be9269e471 Local Taichung 03 (500M) recovered. https://status.sakamoto.blog/incident/723593 Sat, 13 Sep 2025 18:02:49 -0000 https://status.sakamoto.blog/incident/723593#c2fe3da49fbbd832a2b8ec3c26c6ec06c3455854d9807acdadd71ed786447dba Local Taichung 03 (500M) went down. https://status.sakamoto.blog/incident/723593 Sat, 13 Sep 2025 10:03:13 -0000 https://status.sakamoto.blog/incident/723593#3ae26b2564ac757d9b494a7a773360ab93c93bccca5f8184ee2ccb168e5deef4 Local Taichung 02 (500M) recovered. https://status.sakamoto.blog/incident/723593 Sat, 13 Sep 2025 09:58:38 -0000 https://status.sakamoto.blog/incident/723593#e93d6267653aeda0b207cea8e6c3e967ea4d786c43de944a266fe66aecd4cdae Local Taichung 02 (500M) went down. https://status.sakamoto.blog/incident/722902 Fri, 12 Sep 2025 03:07:17 -0000 https://status.sakamoto.blog/incident/722902#3637e5a9da159299fa28ea1924788982ab88d611c15d24c70b5347343438cadc Local Taipei 01 (500M) recovered. https://status.sakamoto.blog/incident/722902 Fri, 12 Sep 2025 03:02:33 -0000 https://status.sakamoto.blog/incident/722902#87023b93590cddd5eeb69de6697a0b0449b2610f4eb2611c2be522c09da52739 Local Taipei 01 (500M) went down. https://status.sakamoto.blog/incident/722902 Fri, 12 Sep 2025 02:31:29 -0000 https://status.sakamoto.blog/incident/722902#8e5be05ca6c32b65ebab71c8fa7a3e57caba2de77237c81ec5cb1863f9b0548d Local Taipei 02 (500M) recovered. https://status.sakamoto.blog/incident/722902 Fri, 12 Sep 2025 02:28:16 -0000 https://status.sakamoto.blog/incident/722902#4d7cccd6ce4a6e72d23835b40e4155672a514f4636e4bd89591561ace05b553b Local Taipei 01 (500M) recovered. https://status.sakamoto.blog/incident/722902 Fri, 12 Sep 2025 02:27:00 -0000 https://status.sakamoto.blog/incident/722902#d6b08a993b370bf10c8e6a49a837698d1a90bfe8cf9686023bdf9626bbc9cda4 Local Taipei 02 (500M) went down. https://status.sakamoto.blog/incident/722902 Fri, 12 Sep 2025 02:23:44 -0000 https://status.sakamoto.blog/incident/722902#55feff9e1f49c959caaa69cfc99d1d5841d9c264b8f47d88d18377a43d082c1d Local Taipei 01 (500M) went down. https://status.sakamoto.blog/incident/720638 Mon, 08 Sep 2025 18:20:48 -0000 https://status.sakamoto.blog/incident/720638#1659d52a66bb265bb16cff0a38048966fcb908ff0078abb8c1614bf97679636b Local Taichung 02 (500M) recovered. https://status.sakamoto.blog/incident/720638 Mon, 08 Sep 2025 18:15:56 -0000 https://status.sakamoto.blog/incident/720638#13dac190223ae3c57d5da9a4033aab9caf7181d5c8b88de0c97026979e9f9385 Local Taichung 02 (500M) went down. https://status.sakamoto.blog/incident/717916 Wed, 03 Sep 2025 21:07:22 -0000 https://status.sakamoto.blog/incident/717916#81ab2dbb577783d8059d15b9b6485e6a21537bbb3b4ff9ac3dce61b6063050ee Local Taichung 02 (500M) recovered. https://status.sakamoto.blog/incident/717916 Wed, 03 Sep 2025 21:02:39 -0000 https://status.sakamoto.blog/incident/717916#321941a0bf28ec3296c448f5f2d8c618c5592ad1e5d74a8448511224d5e14c77 Local Taichung 02 (500M) went down. https://status.sakamoto.blog/incident/715285 Sat, 30 Aug 2025 12:33:05 -0000 https://status.sakamoto.blog/incident/715285#bf68639b49adedb92c25368b4c8205a463048a58e26fc78aef72e685ee39a783 Local Taichung 01 (500M) recovered. https://status.sakamoto.blog/incident/715285 Sat, 30 Aug 2025 12:28:43 -0000 https://status.sakamoto.blog/incident/715285#ccc473d91e68264f05bfe262b1e93472bdbb28759a84c7a951d04070e70f391c Local Taichung 01 (500M) went down. https://status.sakamoto.blog/incident/715285 Sat, 30 Aug 2025 08:48:01 -0000 https://status.sakamoto.blog/incident/715285#d818ec970ad6471f2ba335d7393ef6df7c8fea09d92b0fc75e44d031ed20fbb1 Local Taichung 01 (500M) recovered. https://status.sakamoto.blog/incident/715285 Sat, 30 Aug 2025 08:43:33 -0000 https://status.sakamoto.blog/incident/715285#634b488d30d48cba489a43cd377ee2745383ff319db8ed2362ae262f1314871b Local Taichung 01 (500M) went down. https://status.sakamoto.blog/incident/713735 Wed, 27 Aug 2025 21:07:24 -0000 https://status.sakamoto.blog/incident/713735#7822af739e1d935551482c4a777137b0e80f6d756f79b463ef72c7ed2ecfa189 Local Taichung 02 (500M) recovered. https://status.sakamoto.blog/incident/713735 Wed, 27 Aug 2025 21:02:50 -0000 https://status.sakamoto.blog/incident/713735#d6482ea2dab63ebf238586e99b67857da27d52bd0a5c2ddca6b61f2e4772e2b1 Local Taichung 02 (500M) went down. https://status.sakamoto.blog/incident/711342 Sun, 24 Aug 2025 02:39:36 -0000 https://status.sakamoto.blog/incident/711342#269bfdf6bcc59f837ff07808b07cf7f8fa2e0ce524fa11bd1d86d5b5a40fdf46 Local Taichung 01 (500M) recovered. https://status.sakamoto.blog/incident/711342 Sun, 24 Aug 2025 02:34:57 -0000 https://status.sakamoto.blog/incident/711342#9b30773ea6a99c9f1e539ab7082db7e80c55e7df0d12e3080ca9e9566c657086 Local Taichung 01 (500M) went down. https://status.sakamoto.blog/incident/709434 Wed, 20 Aug 2025 21:07:06 -0000 https://status.sakamoto.blog/incident/709434#37291d86b4c53cf1231d74b8f424b21c5e3cfcc3d3db3558d68abeb09c39cafd Local Taichung 02 (500M) recovered. https://status.sakamoto.blog/incident/709434 Wed, 20 Aug 2025 21:02:42 -0000 https://status.sakamoto.blog/incident/709434#c0392b50cff7a007fbfc3e557b62f96c788976d1513c86755bdfcfe5def9b8e4 Local Taichung 02 (500M) went down. https://status.sakamoto.blog/incident/707128 Sat, 16 Aug 2025 18:07:25 -0000 https://status.sakamoto.blog/incident/707128#019e185b1c87a1af130e71d643cdfcefcea1b56a9de0d416235bd88261bcf1ff Local Taichung 03 (500M) recovered. https://status.sakamoto.blog/incident/707128 Sat, 16 Aug 2025 18:02:57 -0000 https://status.sakamoto.blog/incident/707128#f8ea07bb88477cc80a1fc8de84e8c7ef9f5338073a2bf7b01052f1701cd5d004 Local Taichung 03 (500M) went down. https://status.sakamoto.blog/incident/705513 Wed, 13 Aug 2025 21:07:31 -0000 https://status.sakamoto.blog/incident/705513#07c665260ed7839efad84595c7245782d25ca7642991b96e5cbd730f8f503c65 Local Taichung 02 (500M) recovered. https://status.sakamoto.blog/incident/705513 Wed, 13 Aug 2025 21:03:04 -0000 https://status.sakamoto.blog/incident/705513#501a23505aa5129907701163e9c5abba6cd8b2d58ea89704ec686aba979f776d Local Taichung 02 (500M) went down. https://status.sakamoto.blog/incident/705513 Wed, 13 Aug 2025 13:45:36 -0000 https://status.sakamoto.blog/incident/705513#e119122f6f4ec52da799de281a56a65e50904af2836237bd7dd1ba0fcd8900ba Local Taichung 02 (500M) recovered. https://status.sakamoto.blog/incident/705513 Wed, 13 Aug 2025 13:41:22 -0000 https://status.sakamoto.blog/incident/705513#a739fe9545c2d0737bd2e02c2da78f6a90c240f9d60dac1483942934ad4b92d3 Local Taichung 02 (500M) went down. https://status.sakamoto.blog/incident/703664 Sun, 10 Aug 2025 05:58:15 -0000 https://status.sakamoto.blog/incident/703664#6f60fec4dd0871ddeba03e2fec7b1dda4154dbd419fb8f3fdbe11667a7031e2d Local Taichung 01 (500M) recovered. https://status.sakamoto.blog/incident/703664 Sun, 10 Aug 2025 05:53:30 -0000 https://status.sakamoto.blog/incident/703664#da2c536d399d7b86a0618e4ce03b67658cf1b6ebf061e0e6005ae35ebce579a7 Local Taichung 01 (500M) went down. https://status.sakamoto.blog/incident/703340 Sat, 09 Aug 2025 10:37:49 -0000 https://status.sakamoto.blog/incident/703340#4e7d9b0772a988f415cb43d9684864d84dee9693330ecc3a4d4fa0e249954ff5 Local Taichung 02 (500M) recovered. https://status.sakamoto.blog/incident/703340 Sat, 09 Aug 2025 10:33:07 -0000 https://status.sakamoto.blog/incident/703340#1f50b9d194c861544d5ff4394358cb64ce76fd5ffdf657e3aeef214187a1ecff Local Taichung 02 (500M) went down. https://status.sakamoto.blog/incident/702693 Fri, 08 Aug 2025 08:41:11 -0000 https://status.sakamoto.blog/incident/702693#c5145b779fadce09bb3b091c4acc2744e0922c94e951ce58573c89aad3afc749 Local Taichung 01 (500M) recovered. https://status.sakamoto.blog/incident/702693 Fri, 08 Aug 2025 08:36:31 -0000 https://status.sakamoto.blog/incident/702693#603727c3808cc83ffa544c33d8a855c8d1045a7160cffcf2414e450e00d8bdbc Local Taichung 01 (500M) went down. https://status.sakamoto.blog/incident/702693 Fri, 08 Aug 2025 08:29:01 -0000 https://status.sakamoto.blog/incident/702693#eb7e6c5ae63f262266de3c3a07acc60abb9777c880eca877e9f33e51fea5f2b4 Local Taichung 01 (500M) recovered. https://status.sakamoto.blog/incident/702693 Fri, 08 Aug 2025 08:24:16 -0000 https://status.sakamoto.blog/incident/702693#b367ea4f48df3fe39103bdb87abcf2186ce0e0dd9b12c602689e857caa2b820a Local Taichung 01 (500M) went down. https://status.sakamoto.blog/incident/702693 Fri, 08 Aug 2025 07:43:46 -0000 https://status.sakamoto.blog/incident/702693#9723567a44aae7994b5fda49b3096d853f98feb63bfe5d8a81d45680b1af5393 Local Taichung 01 (500M) recovered. https://status.sakamoto.blog/incident/702693 Fri, 08 Aug 2025 07:39:15 -0000 https://status.sakamoto.blog/incident/702693#5bd0d92d60c6c7c80930a2ba64cfe716cd204fb6cd3a0384f1b5c886279896e5 Local Taichung 01 (500M) went down. https://status.sakamoto.blog/incident/692687 Sun, 03 Aug 2025 04:59:04 -0000 https://status.sakamoto.blog/incident/692687#99a0da2a210ad7c210c584d09ca114e854ad25a240436f74efc4906aa0fe5c37 Local Taichung 01 (500M) recovered. https://status.sakamoto.blog/incident/692687 Sun, 03 Aug 2025 04:51:35 -0000 https://status.sakamoto.blog/incident/692687#e15abf0ec5e6e91a456f0715cc3f47ee120e59fad9b72373ed1659389ccc56da Local Taichung 01 (500M) went down. https://status.sakamoto.blog/incident/689653 Sat, 02 Aug 2025 18:07:06 -0000 https://status.sakamoto.blog/incident/689653#b1a4750e58b2137ef43c879f5c51506b9108328d5d774196eda3f49c314fcfec Local Taichung 03 (500M) recovered. https://status.sakamoto.blog/incident/689653 Sat, 02 Aug 2025 18:02:45 -0000 https://status.sakamoto.blog/incident/689653#e87e95c2d2f2e2ebe2c4576f6e123d2595e32ad78e089d91616656fe2843bb27 Local Taichung 03 (500M) went down. https://status.sakamoto.blog/incident/625133 Thu, 24 Jul 2025 12:39:01 -0000 https://status.sakamoto.blog/incident/625133#a3aec2279b645adef243354e2e94c46aea0a63125d849e197f592e1076f354f2 Local Taipei 01 (500M) recovered. https://status.sakamoto.blog/incident/625133 Thu, 24 Jul 2025 12:34:29 -0000 https://status.sakamoto.blog/incident/625133#9fdbf15391d569dc0ae8b656bbe65b017b394deccebe0edb9d5cd0679009e996 Local Taipei 01 (500M) went down. https://status.sakamoto.blog/incident/625133 Thu, 24 Jul 2025 12:15:59 -0000 https://status.sakamoto.blog/incident/625133#eba789e709e2d9f8666473e984ce613cba50d96eaf876c05e398972423dcff2d Local Taichung 01 (500M) recovered. https://status.sakamoto.blog/incident/625133 Thu, 24 Jul 2025 12:11:17 -0000 https://status.sakamoto.blog/incident/625133#1a9db955a996a5afa9e7332e4e620c9369538aeb0f700a3a7d01e64add8da3aa Local Taichung 01 (500M) went down. https://status.sakamoto.blog/incident/624724 Wed, 23 Jul 2025 21:07:41 -0000 https://status.sakamoto.blog/incident/624724#4dfc20677d380b41d2a1eb58b2eeca8f33ff42049b52fd9eb4f99af3f5926e2f Local Taichung 02 (500M) recovered. https://status.sakamoto.blog/incident/624724 Wed, 23 Jul 2025 21:03:08 -0000 https://status.sakamoto.blog/incident/624724#315df17b38f94f740b1ad9cce9f106a358256273338153b7ebc9f2bf003a2b55 Local Taichung 02 (500M) went down. https://status.sakamoto.blog/incident/622501 Sat, 19 Jul 2025 18:07:53 -0000 https://status.sakamoto.blog/incident/622501#4174ee2caede29525ef725260f473db354bb3d9157683609b832d96b56356c97 Local Taichung 03 (500M) recovered. https://status.sakamoto.blog/incident/622501 Sat, 19 Jul 2025 18:03:12 -0000 https://status.sakamoto.blog/incident/622501#c6568774dedabfecbcfdc2de435416ded13ce5c1502ae5a31a116f54e66c67f8 Local Taichung 03 (500M) went down. https://status.sakamoto.blog/incident/621959 Fri, 18 Jul 2025 14:40:46 -0000 https://status.sakamoto.blog/incident/621959#110c5623c7db80cebcfa6fdd103b0632363b3c5b4651ee10d11de4e36433f6b5 Local Taichung 01 (500M) recovered. https://status.sakamoto.blog/incident/621959 Fri, 18 Jul 2025 14:33:08 -0000 https://status.sakamoto.blog/incident/621959#54f1da1efe4980804e81a0ba074bd2f7a926a0b66e65d35b44269e7094fefe7e Local Taichung 01 (500M) went down. https://status.sakamoto.blog/incident/620972 Wed, 16 Jul 2025 21:07:53 -0000 https://status.sakamoto.blog/incident/620972#4299f012aba9ed2b30db6460fe889f2a549494a23fecdf2aa383813c13de2f66 Local Taichung 02 (500M) recovered. https://status.sakamoto.blog/incident/620972 Wed, 16 Jul 2025 21:03:10 -0000 https://status.sakamoto.blog/incident/620972#436849b592c685a56d4bff96d1afae6c1a98c81dc568fafbc0e26a6006f13082 Local Taichung 02 (500M) went down. https://status.sakamoto.blog/incident/618538 Sat, 12 Jul 2025 18:07:21 -0000 https://status.sakamoto.blog/incident/618538#8f9febf811779a9361ca06fc0191dc2fd4f9f9d363a100c3cac121b2a9f3b2e7 Local Taichung 03 (500M) recovered. https://status.sakamoto.blog/incident/618538 Sat, 12 Jul 2025 18:02:45 -0000 https://status.sakamoto.blog/incident/618538#1ea545d973d5547a3fced9be3b884e8f6e5070c81f8ab95e4a33308cd2b1a3a1 Local Taichung 03 (500M) went down. https://status.sakamoto.blog/incident/616978 Wed, 09 Jul 2025 21:08:02 -0000 https://status.sakamoto.blog/incident/616978#0d4d0b98d8b9230374dbaa7ab0841e6ea90517efb912282915ab632041ea4113 Local Taichung 02 (500M) recovered. https://status.sakamoto.blog/incident/616978 Wed, 09 Jul 2025 21:03:26 -0000 https://status.sakamoto.blog/incident/616978#a5d15565a30bbaac8f978547d97c8dbd7c8cd36af3a56f61d03817d9c65ce55a Local Taichung 02 (500M) went down. https://status.sakamoto.blog/incident/614169 Fri, 04 Jul 2025 11:03:19 -0000 https://status.sakamoto.blog/incident/614169#2e1aaaf2e6c54c9e9ffe054977b24884d388c51d79a8a24d155f6fbb95651989 Local Taichung 02 (500M) recovered. https://status.sakamoto.blog/incident/614169 Fri, 04 Jul 2025 10:55:39 -0000 https://status.sakamoto.blog/incident/614169#3f49326d18d04fcf88dc017a4ff9ec6196bc184ca1927f3602c85f1ebe87e0e7 Local Taichung 02 (500M) went down. https://status.sakamoto.blog/incident/612716 Wed, 02 Jul 2025 21:11:25 -0000 https://status.sakamoto.blog/incident/612716#c26b811cb025af8ddfea69cfdec1d487926e32f4f33678980aacefb583017d6c Local Taichung 02 (500M) recovered. https://status.sakamoto.blog/incident/612716 Wed, 02 Jul 2025 21:03:51 -0000 https://status.sakamoto.blog/incident/612716#b34f92da0016e7016fe97538e23f64749641573a342af51b2030276c4dd91d63 Local Taichung 02 (500M) went down. https://status.sakamoto.blog/incident/612716 Wed, 02 Jul 2025 00:47:29 -0000 https://status.sakamoto.blog/incident/612716#95ba51d02d069ecda8eb143ceee8a61000faf7151129b66e70b0dc99cf19f172 Japan Osaka Route-02 (10GE) recovered. https://status.sakamoto.blog/incident/612716 Wed, 02 Jul 2025 00:39:49 -0000 https://status.sakamoto.blog/incident/612716#17ad14fa026b65bdfaac45bc6f432d42dc8673a7c818bd7067c6041dda825b9c Japan Osaka Route-02 (10GE) went down. https://status.sakamoto.blog/incident/612443 Tue, 01 Jul 2025 14:06:04 -0000 https://status.sakamoto.blog/incident/612443#109e27440715fff44f919d548377e2cae61187ffaffd139b0a4944a8e3a76ada Local Taichung 01 (500M) recovered. https://status.sakamoto.blog/incident/612443 Tue, 01 Jul 2025 12:55:25 -0000 https://status.sakamoto.blog/incident/612443#59ed9509347d470c583232af95916a41b3b8c6a7740ef98c9aca8d4d03fa7628 Local Taichung 01 (500M) went down. https://status.sakamoto.blog/incident/611100 Sun, 29 Jun 2025 05:06:31 -0000 https://status.sakamoto.blog/incident/611100#e027e6b6a7f2126c621503dbe373e32ebf5eace1121837db3770a81f04df12e5 Local Kaohsiung 02 (500M) recovered. https://status.sakamoto.blog/incident/611100 Sun, 29 Jun 2025 04:58:56 -0000 https://status.sakamoto.blog/incident/611100#c076b208547dccae859ecf67dfdf5c096e13a0e0440bb4a37ae767f2dcfd848e Local Kaohsiung 02 (500M) went down. https://status.sakamoto.blog/incident/608659 Wed, 25 Jun 2025 07:15:12 -0000 https://status.sakamoto.blog/incident/608659#b2aea593a1b8ded9051ec72508d925af4026ff90067647644bce515799286a23 Local Taichung 01 (500M) recovered. https://status.sakamoto.blog/incident/608659 Wed, 25 Jun 2025 07:10:30 -0000 https://status.sakamoto.blog/incident/608659#ccf7148787a2c64b6a5abcda86e4bbcf2190cf3998d20bdd5fe6a421d8b5d99f Local Taichung 01 (500M) went down. https://status.sakamoto.blog/incident/608659 Wed, 25 Jun 2025 03:54:08 -0000 https://status.sakamoto.blog/incident/608659#a1c4410b44d4bf486419b7dbcd11202dff366093a7de128cc90938579a8a2651 Local Taichung 01 (500M) recovered. https://status.sakamoto.blog/incident/608659 Wed, 25 Jun 2025 03:49:26 -0000 https://status.sakamoto.blog/incident/608659#926c42ec1769b54eaafcc4d68b83b3d87e11533b2884fcee008fb8c86a835ed0 Local Taichung 01 (500M) went down. https://status.sakamoto.blog/incident/608659 Wed, 25 Jun 2025 03:36:04 -0000 https://status.sakamoto.blog/incident/608659#7df402fe649e1b5914432ded0d2b1e2ce6e7a49257d9bd3da51d4d8c2232c8db Local Taichung 01 (500M) recovered. https://status.sakamoto.blog/incident/608659 Wed, 25 Jun 2025 02:43:27 -0000 https://status.sakamoto.blog/incident/608659#864006a1129da1562f3dfe41eeae782d056c7128d2f223ca102b47bdc67cc9da Local Taichung 01 (500M) went down. https://status.sakamoto.blog/incident/608048 Tue, 24 Jun 2025 04:50:08 -0000 https://status.sakamoto.blog/incident/608048#f534b3beccfe59e53fcfee42f1a4f425d5d618243898fc4bf0025e201185dc3a Local Taichung 01 (500M) recovered. https://status.sakamoto.blog/incident/608048 Tue, 24 Jun 2025 04:21:31 -0000 https://status.sakamoto.blog/incident/608048#725096c7546fc7f0ae11d258ab2cc957bf03e4fd949ef717047b212fd2ffc78c Local Taichung 01 (500M) went down. https://status.sakamoto.blog/incident/607099 Sun, 22 Jun 2025 07:30:20 -0000 https://status.sakamoto.blog/incident/607099#0cf9a28a583a745d37b60234a75d77104451745392498e27a50ac9947cb221c5 Local Taichung 01 (500M) recovered. https://status.sakamoto.blog/incident/607099 Sun, 22 Jun 2025 07:22:35 -0000 https://status.sakamoto.blog/incident/607099#420d3aa496bd550cc1d5a40838f1419eb85b1153e9fceac202f4bafa0df33dfb Local Taichung 01 (500M) went down. https://status.sakamoto.blog/incident/606930 Sat, 21 Jun 2025 21:26:05 -0000 https://status.sakamoto.blog/incident/606930#30a769cad5b59c75cac181f24eb29261fb1eb6a4131e93efaab24443df630250 Local Taichung 03 (500M) recovered. https://status.sakamoto.blog/incident/606930 Sat, 21 Jun 2025 21:21:50 -0000 https://status.sakamoto.blog/incident/606930#108512ef41754fb5d279e2269c761a51c5a6625977bbb20b7a1325d5bf8355f5 Local Taichung 03 (500M) went down. https://status.sakamoto.blog/incident/605520 Thu, 19 Jun 2025 06:47:55 -0000 https://status.sakamoto.blog/incident/605520#2f7f13a8249dc20c9e61029269b2499a003db74020cf1f492d2c1c3bea22cf81 Local Taichung 01 (500M) recovered. https://status.sakamoto.blog/incident/605520 Thu, 19 Jun 2025 06:43:09 -0000 https://status.sakamoto.blog/incident/605520#5ad54eddfd68769c7c894d6f1175b711203bc6a9ba3d0650bfe88e9c9a1c59e6 Local Taichung 01 (500M) went down. https://status.sakamoto.blog/incident/605520 Thu, 19 Jun 2025 03:59:00 -0000 https://status.sakamoto.blog/incident/605520#88711f256d9a6feff3240e7b9faf1cb8f5325f1b4b5b34d5f495c5cc09bc7b7c Japan Osaka Route-02 (10GE) recovered. https://status.sakamoto.blog/incident/605520 Thu, 19 Jun 2025 03:54:27 -0000 https://status.sakamoto.blog/incident/605520#c4f097f044182ef713b999abd1d4e396a2f1a3445cf105ec94153064186c5b2c Japan Osaka Route-02 (10GE) went down. https://status.sakamoto.blog/incident/605369 Wed, 18 Jun 2025 21:06:58 -0000 https://status.sakamoto.blog/incident/605369#4aaef9386af9f8125e69f5c6f9f99e9d6bf1708b0c8694a5337e245b088dad72 Local Taichung 02 (500M) recovered. https://status.sakamoto.blog/incident/605369 Wed, 18 Jun 2025 21:02:24 -0000 https://status.sakamoto.blog/incident/605369#841132ed4bcecced4f8763d37a4a7b8d67bd9be51a2e1e18d96558e7d9411ec0 Local Taichung 02 (500M) went down. https://status.sakamoto.blog/incident/601048 Thu, 12 Jun 2025 10:17:20 -0000 https://status.sakamoto.blog/incident/601048#627ee72170e56aaff42b858dd46904a1ef9ac3230f76e0915f1610a6a3c3d38a Local Taipei 01 (500M) recovered. https://status.sakamoto.blog/incident/601048 Thu, 12 Jun 2025 10:00:31 -0000 https://status.sakamoto.blog/incident/601048#f9da42524c34465cb8f612ee18237d2ae57b72d09b0fbee4d1df90be3ddf7495 Local Taipei 01 (500M) went down. https://status.sakamoto.blog/incident/601048 Thu, 12 Jun 2025 04:09:39 -0000 https://status.sakamoto.blog/incident/601048#7ba49373af4c6d451fd109137e2c8ad92b8568a95be3e9d8c24970a172555b87 Local Taichung 02 (500M) recovered. https://status.sakamoto.blog/incident/601048 Wed, 11 Jun 2025 21:01:57 -0000 https://status.sakamoto.blog/incident/601048#356bc56ccce51529f07e7ffc2c098ec1bada8280b1e0cc8a18ccf008c9adcf4d Local Taichung 02 (500M) went down.