Incidents | Sakamoto Network Latency Grapher Incidents reported on status page for Sakamoto Network Latency Grapher https://status.sakamoto.blog/ https://d1lppblt9t2x15.cloudfront.net/logos/e4d1ff76cf83d3c035042c4054c5f8dd.jpeg Incidents | Sakamoto Network Latency Grapher https://status.sakamoto.blog/ en Local Taichung 02 (500M) and Local Taipei 01 (500M) are 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. Local Taichung 02 (500M) and Local Taipei 01 (500M) are down 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. Local Taichung 02 (500M) and Local Taipei 01 (500M) are 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. Local Taichung 02 (500M) and Local Taipei 01 (500M) are down 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.