Incidents reported on status page for Shiro / 白 - 11T+ Anycast https://status.shiro.bot/ en https://status.shiro.bot/ Thu, 02 Apr 2026 11:22:25 +0000 https://status.shiro.bot/#05eaed9ac3202fe51c8e7b74c64fdd0b9322c30720a0ce57c209f5f59faa02a8 Anycast - RO1 recovered https://status.shiro.bot/ Thu, 02 Apr 2026 11:16:37 +0000 https://status.shiro.bot/#05eaed9ac3202fe51c8e7b74c64fdd0b9322c30720a0ce57c209f5f59faa02a8 Anycast - RO1 went down https://status.shiro.bot/ Mon, 30 Mar 2026 11:01:16 +0000 https://status.shiro.bot/#32cb37053f3d7cb0efa6ce0a8b2e8fe348e86320b97522d216e2f5bede7c3760 Anycast - RO1 recovered https://status.shiro.bot/ Mon, 30 Mar 2026 08:31:35 +0000 https://status.shiro.bot/#32cb37053f3d7cb0efa6ce0a8b2e8fe348e86320b97522d216e2f5bede7c3760 Anycast - RO1 went down https://status.shiro.bot/ Tue, 24 Mar 2026 13:26:20 +0000 https://status.shiro.bot/#1239bcc9a0d0852d704a3cf25c8fa0d1efd8e7f6f641b12ff8603e992d32ec8e Anycast - NXP1 recovered https://status.shiro.bot/ Tue, 24 Mar 2026 13:23:43 +0000 https://status.shiro.bot/#1239bcc9a0d0852d704a3cf25c8fa0d1efd8e7f6f641b12ff8603e992d32ec8e Anycast - NXP1 went down https://status.shiro.bot/ Tue, 24 Mar 2026 12:59:22 +0000 https://status.shiro.bot/#91285140b1435422021e3fe20b3d47458e4b095832445e5afb6b93a37fb5886d Anycast - NXP1 recovered https://status.shiro.bot/ Tue, 24 Mar 2026 12:53:36 +0000 https://status.shiro.bot/#91285140b1435422021e3fe20b3d47458e4b095832445e5afb6b93a37fb5886d Anycast - NXP1 went down https://status.shiro.bot/ Mon, 23 Mar 2026 13:55:27 +0000 https://status.shiro.bot/#37a492a9a0fbc1883a3a41b1cb894682175479909ce32f1345f3a87428c98c7c Anycast - RO1 recovered https://status.shiro.bot/ Mon, 23 Mar 2026 13:52:42 +0000 https://status.shiro.bot/#37a492a9a0fbc1883a3a41b1cb894682175479909ce32f1345f3a87428c98c7c Anycast - RO1 went down https://status.shiro.bot/ Mon, 23 Mar 2026 12:56:23 +0000 https://status.shiro.bot/#48a9768051b376fe53e55bc57b6838c77a31cfb66d7d23fa8a15cb52cd0b73c5 DE-FRA - ShiroAPI recovered https://status.shiro.bot/ Mon, 23 Mar 2026 12:56:21 +0000 https://status.shiro.bot/#307c9aa48c1eb1945b6c5cde41621b76121600e7945a381b85e58504bc9367bc Anycast - NXP1 recovered https://status.shiro.bot/ Mon, 23 Mar 2026 12:56:07 +0000 https://status.shiro.bot/#4a911009444bde6c2004f801129f97cd9cefa0db8761993c388503bfa801f797 Anycast - DE1 recovered https://status.shiro.bot/ Mon, 23 Mar 2026 11:29:36 +0000 https://status.shiro.bot/#307c9aa48c1eb1945b6c5cde41621b76121600e7945a381b85e58504bc9367bc Anycast - NXP1 went down https://status.shiro.bot/ Mon, 23 Mar 2026 11:29:33 +0000 https://status.shiro.bot/#4a911009444bde6c2004f801129f97cd9cefa0db8761993c388503bfa801f797 Anycast - DE1 went down https://status.shiro.bot/ Mon, 23 Mar 2026 11:29:30 +0000 https://status.shiro.bot/#48a9768051b376fe53e55bc57b6838c77a31cfb66d7d23fa8a15cb52cd0b73c5 DE-FRA - ShiroAPI went down https://status.shiro.bot/ Tue, 17 Mar 2026 03:09:20 +0000 https://status.shiro.bot/#6e809752b9afdbc0fa5212202e6c695bd6d160637a91beaa2ace0b94a0c43c6a Anycast - HK1 went down https://status.shiro.bot/ Wed, 11 Mar 2026 16:41:20 +0000 https://status.shiro.bot/#6daeaef21ea5f5f7e7e65cc97e1f1a45195f59687229827de12fce86eb3c7765 Anycast - NXP1 recovered https://status.shiro.bot/ Wed, 11 Mar 2026 16:38:45 +0000 https://status.shiro.bot/#6daeaef21ea5f5f7e7e65cc97e1f1a45195f59687229827de12fce86eb3c7765 Anycast - NXP1 went down https://status.shiro.bot/ Wed, 11 Mar 2026 12:23:51 +0000 https://status.shiro.bot/#4e0ec07f54d1372a464bf0a3b0ef439463437c6b0ffc4afadb486aaa0fa19456 Anycast - NCIX went down https://status.shiro.bot/ Thu, 05 Mar 2026 16:11:24 +0000 https://status.shiro.bot/#fe6680d2020d13df4c03a5a1768657c9e30f1d22cfce1ee00523a2c26b9dd5af DE-FRA - ShiroAPI recovered https://status.shiro.bot/ Thu, 05 Mar 2026 16:11:13 +0000 https://status.shiro.bot/#d5ee38af86c74080faa7114564d03b1a64407c2c6a6030a2e9721e476f4fdffc Anycast - DE1 recovered https://status.shiro.bot/ Wed, 04 Mar 2026 21:14:43 +0000 https://status.shiro.bot/#fe6680d2020d13df4c03a5a1768657c9e30f1d22cfce1ee00523a2c26b9dd5af DE-FRA - ShiroAPI went down https://status.shiro.bot/ Wed, 04 Mar 2026 21:11:35 +0000 https://status.shiro.bot/#d5ee38af86c74080faa7114564d03b1a64407c2c6a6030a2e9721e476f4fdffc Anycast - DE1 went down https://status.shiro.bot/ Mon, 09 Feb 2026 02:03:06 +0000 https://status.shiro.bot/#4e2566aa630c755900cdfa13c9cdb4c9b2682366a6b88e3ce045831d7fdd7c8d Anycast - ID1 went down https://status.shiro.bot/ Mon, 05 Jan 2026 04:33:31 +0000 https://status.shiro.bot/#9dfe3dea7efee43dca27637fb653cb5aea6089d8c77301b91b4cc8638ef187f7 Anycast - JP1 went down https://status.shiro.bot/ Mon, 05 Jan 2026 04:33:13 +0000 https://status.shiro.bot/#1859337b559894897b43879bf3ffe9727750d9e5d043bde24859ed6ec9661523 Anycast - SG1 went down https://status.shiro.bot/incident/794484 Thu, 25 Dec 2025 23:04:00 -0000 https://status.shiro.bot/incident/794484#17c15c4dd87c7c7047a29366b66354c1cfb967cae11217257e4be77248404609 We are currently investigating a service disruption impacting a subset of users in certain regions. The issue is caused by an Anycast routing anomaly where traffic is being directed to an unintended edge location due to inconsistent BGP route propagation from one of our upstream providers. As a result, some requests may experience increased latency, intermittent failures, or connection timeouts. Our systems are functioning normally, but traffic routing behavior is not optimal in all regions. The affected Anycast routes have been identified, and mitigation steps are in progress, including traffic rebalancing and selective route withdrawal. Service availability is gradually improving as routing convergence continues. https://status.shiro.bot/incident/786658 Mon, 15 Dec 2025 10:47:00 -0000 https://status.shiro.bot/incident/786658#7a4ebca9bc0f3be6af0548f45cda5ac164c44383ca9af6444337d0b7a7de6440 We have fixed the BGP Session issue and finalized our Network Maintenance https://status.shiro.bot/incident/786658 Mon, 15 Dec 2025 06:00:00 -0000 https://status.shiro.bot/incident/786658#11bd5f2121ce7f19cb7c864ae93f84d0bc14a4d80e10a2d3471f998955aaff53 We are currently performing scheduled network maintenance across parts of our infrastructure. Separately, we are also experiencing BGP session instability with an upstream provider. These two events are not directly related, but may both result in intermittent connectivity issues for some users. Our network team is actively monitoring both the maintenance process and the BGP session behavior to ensure overall network stability. Routing will automatically normalize once the BGP sessions are fully stabilized and maintenance is completed. No data loss has been reported. Further updates will be provided as needed. https://status.shiro.bot/incident/784125 Sun, 14 Dec 2025 03:00:18 -0000 https://status.shiro.bot/incident/784125#104a5804162207a81a6e653802410780839adeb89becd7075fc8dd63b0c5cb8e Maintenance completed https://status.shiro.bot/incident/784125 Sat, 13 Dec 2025 10:00:18 -0000 https://status.shiro.bot/incident/784125#b9867351fd6751d93d779cd99005192780db11a71255f1a3c88161dcea9703d4 We are currently performing scheduled maintenance to expand our anycast network and deploy new hardware across our infrastructure. This upgrade also includes improvements to several internal services to ensure better routing stability, lower latency, and higher overall reliability. During this maintenance window, a small percentage of users may experience temporary issues accessing the dashboard. All core services remain operational, and the impact is limited to the dashboard interface only. Our team is actively working on the upgrades, and availability will be fully restored once the hardware rollout and internal adjustments are completed. If you need assistance during the maintenance period, please contact our support team through your usual channel. https://status.shiro.bot/incident/784617 Fri, 12 Dec 2025 05:20:00 -0000 https://status.shiro.bot/incident/784617#8b473bd4c551cf175a2b721cf021973a4380f15641d00e9c82156fd4223a1260 The hardware failure affecting our Tokyo POP has been fully resolved. Dashboard access has returned to normal for all users. https://status.shiro.bot/incident/784617 Thu, 11 Dec 2025 11:00:00 -0000 https://status.shiro.bot/incident/784617#59d1384170f8c4daaa59c43245611b66be00dd2a2bd39a42a89ebe82631b4752 We have identified a hardware failure in our Tokyo point-of-presence (POP) that is impacting one of our internal services. As a result, a small percentage of users may experience temporary unavailability or degraded performance when accessing the dashboard. Our team has isolated the issue and is in the process of replacing the affected hardware and restoring normal operation. All core services remain available, and the impact is limited to the dashboard interface. We expect recovery as soon as the replacement hardware is fully synchronized and routing is stabilized. If you need assistance during this incident, please reach out through your regular support channel.