Incidents reported on status page for Shiro / 白 - 11T+ Anycast https://status.shiro.bot/ en https://status.shiro.bot/ Tue, 03 Feb 2026 00:41:23 +0000 https://status.shiro.bot/#2b51db049ce5e7ee04d9998f22763f722a961478439ba2f11a15f3b99ebd9b70 Anycast - NXP1 recovered https://status.shiro.bot/ Tue, 03 Feb 2026 00:17:42 +0000 https://status.shiro.bot/#2b51db049ce5e7ee04d9998f22763f722a961478439ba2f11a15f3b99ebd9b70 Anycast - NXP1 went down https://status.shiro.bot/ Mon, 02 Feb 2026 23:35:31 +0000 https://status.shiro.bot/#3bd2646a75ed3bd681569a9af0a5eeb139949b440682a9e380aa1f9c1ee51d77 Anycast - NCIX recovered https://status.shiro.bot/ Mon, 02 Feb 2026 23:35:24 +0000 https://status.shiro.bot/#0710c1f67f613eecd8461e688658bbf612cf8a4189ef7622e630a01c6f693cc5 DE-FRA - ShiroAPI recovered https://status.shiro.bot/ Mon, 02 Feb 2026 23:35:24 +0000 https://status.shiro.bot/#80de94518b697d099c340217d56952a943cb8af1a5cf175b84d4ef823d707cda Anycast - NXP1 recovered https://status.shiro.bot/ Mon, 02 Feb 2026 23:35:16 +0000 https://status.shiro.bot/#3841103ba123fa8a5b5a8617242da5501855beeaef2f3fc1c2e11be07908aa10 Anycast - DE1 recovered https://status.shiro.bot/ Mon, 02 Feb 2026 23:29:47 +0000 https://status.shiro.bot/#3bd2646a75ed3bd681569a9af0a5eeb139949b440682a9e380aa1f9c1ee51d77 Anycast - NCIX went down https://status.shiro.bot/ Mon, 02 Feb 2026 23:29:42 +0000 https://status.shiro.bot/#80de94518b697d099c340217d56952a943cb8af1a5cf175b84d4ef823d707cda Anycast - NXP1 went down https://status.shiro.bot/ Mon, 02 Feb 2026 23:29:40 +0000 https://status.shiro.bot/#0710c1f67f613eecd8461e688658bbf612cf8a4189ef7622e630a01c6f693cc5 DE-FRA - ShiroAPI went down https://status.shiro.bot/ Mon, 02 Feb 2026 23:29:33 +0000 https://status.shiro.bot/#3841103ba123fa8a5b5a8617242da5501855beeaef2f3fc1c2e11be07908aa10 Anycast - DE1 went down https://status.shiro.bot/ Sat, 31 Jan 2026 10:18:11 +0000 https://status.shiro.bot/#097544de27a0e723e235b8d78aca33a67f47d7c0fe7ee65da2e0d10a75310267 Main Website recovered https://status.shiro.bot/ Sat, 31 Jan 2026 10:12:27 +0000 https://status.shiro.bot/#097544de27a0e723e235b8d78aca33a67f47d7c0fe7ee65da2e0d10a75310267 Main Website went down https://status.shiro.bot/ Fri, 30 Jan 2026 22:17:58 +0000 https://status.shiro.bot/#228ddfe3cd4633332bd92bfe6171acd8a6f4c96b13940ceee71779549ff5ad7a Anycast - HK1 recovered https://status.shiro.bot/ Fri, 30 Jan 2026 19:03:22 +0000 https://status.shiro.bot/#228ddfe3cd4633332bd92bfe6171acd8a6f4c96b13940ceee71779549ff5ad7a Anycast - HK1 went down https://status.shiro.bot/ Wed, 28 Jan 2026 23:26:08 +0000 https://status.shiro.bot/#181ccf2ff4596b6b5c6b5c69a418ae3debd561c6b83dcdd5deef44b29f981b2e Anycast - DE1 recovered https://status.shiro.bot/ Wed, 28 Jan 2026 23:20:22 +0000 https://status.shiro.bot/#f4a33617d7503a0b7ab3ab753a3b76943423dce562d135035809573c9a201a07 DE-FRA - ShiroAPI recovered https://status.shiro.bot/ Wed, 28 Jan 2026 23:08:26 +0000 https://status.shiro.bot/#f4a33617d7503a0b7ab3ab753a3b76943423dce562d135035809573c9a201a07 DE-FRA - ShiroAPI went down https://status.shiro.bot/ Wed, 28 Jan 2026 23:05:31 +0000 https://status.shiro.bot/#181ccf2ff4596b6b5c6b5c69a418ae3debd561c6b83dcdd5deef44b29f981b2e Anycast - DE1 went down https://status.shiro.bot/ Wed, 28 Jan 2026 04:26:21 +0000 https://status.shiro.bot/#844e643bb35a25283a616b97cbb292e04fc925f4ba136eccc2dae81ed9cf2ae0 Anycast - NXP1 recovered https://status.shiro.bot/ Wed, 28 Jan 2026 02:59:39 +0000 https://status.shiro.bot/#844e643bb35a25283a616b97cbb292e04fc925f4ba136eccc2dae81ed9cf2ae0 Anycast - NXP1 went down https://status.shiro.bot/ Mon, 26 Jan 2026 07:08:41 +0000 https://status.shiro.bot/#8de833549622e6911fe20a2abddcec8b2783ae68d3ddb4b7eebadda7c102c71a Anycast - ID1 recovered https://status.shiro.bot/ Mon, 26 Jan 2026 07:05:47 +0000 https://status.shiro.bot/#8de833549622e6911fe20a2abddcec8b2783ae68d3ddb4b7eebadda7c102c71a Anycast - ID1 went down https://status.shiro.bot/ Sat, 24 Jan 2026 07:28:20 +0000 https://status.shiro.bot/#f245ff73da6a8f158a5186b08e0924236b79d4e1bb8da7e966be93eeb4048901 Anycast - RO1 recovered https://status.shiro.bot/ Sat, 24 Jan 2026 07:25:39 +0000 https://status.shiro.bot/#f245ff73da6a8f158a5186b08e0924236b79d4e1bb8da7e966be93eeb4048901 Anycast - RO1 went down https://status.shiro.bot/ Thu, 22 Jan 2026 22:26:49 +0000 https://status.shiro.bot/#de94df96482adf9e8950f6593e8b7df62ed62d31753fef045ccc790137abf77f Anycast - ID1 recovered https://status.shiro.bot/ Thu, 22 Jan 2026 17:18:07 +0000 https://status.shiro.bot/#de94df96482adf9e8950f6593e8b7df62ed62d31753fef045ccc790137abf77f Anycast - ID1 went down https://status.shiro.bot/ Wed, 21 Jan 2026 16:49:25 +0000 https://status.shiro.bot/#23a00fe904a7568e52f1b4dc3b79877b9accf77665d282ac63ce3baeef7aaa17 Anycast - RO1 recovered https://status.shiro.bot/ Wed, 21 Jan 2026 16:46:38 +0000 https://status.shiro.bot/#23a00fe904a7568e52f1b4dc3b79877b9accf77665d282ac63ce3baeef7aaa17 Anycast - RO1 went down https://status.shiro.bot/ Sun, 18 Jan 2026 06:35:58 +0000 https://status.shiro.bot/#77854e220aab09aadfbfc0f4d217a786cc5ae8759a52fa794a2ed4f15a6cf144 Anycast - HK1 recovered https://status.shiro.bot/ Sun, 18 Jan 2026 06:33:20 +0000 https://status.shiro.bot/#77854e220aab09aadfbfc0f4d217a786cc5ae8759a52fa794a2ed4f15a6cf144 Anycast - HK1 went down https://status.shiro.bot/ Wed, 14 Jan 2026 07:00:14 +0000 https://status.shiro.bot/#9b37aa390ba14efc5bc3588093b8f2f80f11d199fd21b989b073dd054703cd73 Anycast - HK1 recovered https://status.shiro.bot/ Tue, 13 Jan 2026 02:06:24 +0000 https://status.shiro.bot/#9b37aa390ba14efc5bc3588093b8f2f80f11d199fd21b989b073dd054703cd73 Anycast - HK1 went down https://status.shiro.bot/ Mon, 12 Jan 2026 12:27:06 +0000 https://status.shiro.bot/#abe7dd5d7df8a192a2f65c39855a212b14b362cd0e1b0f483ace6d23938777a1 Anycast - HK1 recovered https://status.shiro.bot/ Thu, 08 Jan 2026 08:44:30 +0000 https://status.shiro.bot/#9db8b99c7e466cf291fe44d6f26abaa4dc4562c90b8dc0a3cc63d17eecd1ddb3 Anycast - NXP1 recovered https://status.shiro.bot/ Thu, 08 Jan 2026 08:38:42 +0000 https://status.shiro.bot/#9db8b99c7e466cf291fe44d6f26abaa4dc4562c90b8dc0a3cc63d17eecd1ddb3 Anycast - NXP1 went down https://status.shiro.bot/ Wed, 07 Jan 2026 12:44:40 +0000 https://status.shiro.bot/#292c484514eaefd2407f0e7f259c74a5871e1679d27acc9d1a6de4693876db38 Anycast - ID1 recovered https://status.shiro.bot/ Wed, 07 Jan 2026 12:03:08 +0000 https://status.shiro.bot/#292c484514eaefd2407f0e7f259c74a5871e1679d27acc9d1a6de4693876db38 Anycast - ID1 went down https://status.shiro.bot/ Tue, 06 Jan 2026 01:05:55 +0000 https://status.shiro.bot/#bc7556338ea40197584d270a64f633a0d439f983a01d7a0d558d837d75968398 Anycast - NCIX recovered https://status.shiro.bot/ Tue, 06 Jan 2026 00:17:59 +0000 https://status.shiro.bot/#bc7556338ea40197584d270a64f633a0d439f983a01d7a0d558d837d75968398 Anycast - NCIX went down https://status.shiro.bot/ Mon, 05 Jan 2026 09:48:16 +0000 https://status.shiro.bot/#ac515601bd83def7032ccf86fbad9c005e5452974f2ed7e271eb75b932b94fc4 Anycast - ID1 recovered https://status.shiro.bot/ Mon, 05 Jan 2026 09:39:04 +0000 https://status.shiro.bot/#ac515601bd83def7032ccf86fbad9c005e5452974f2ed7e271eb75b932b94fc4 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:25 +0000 https://status.shiro.bot/#abe7dd5d7df8a192a2f65c39855a212b14b362cd0e1b0f483ace6d23938777a1 Anycast - HK1 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/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 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/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.