Misaka Network Outage History
Misaka Network is up right nowMisaka Network had 24 outages in the last 2 years totaling 2549h 45m of downtime — averaging 1 incident per month.
There were 24 Misaka Network outages since July 9, 2025 totaling 2549h 45m of downtime. Each is summarised below — incident details, duration, and resolution information.
Connectivity Issues in London / Slough (LON5,LON7)
Timeline · 2 updates
Connectivity issues in San Jose, CA, US (SJC10)
Timeline · 3 updates
- identified Feb 23, 2026, 09:50 AM UTC
Status: Identified We are currently experiencing heavy DDoS attacks affecting our San Jose location. Our team is actively mitigating the attack, and connectivity quality may be temporarily impacted. Further updates will be provided as the situation develops. Affected components SJC10 - San Jose, CA, United States (Degraded performance)
- identified Feb 23, 2026, 03:43 PM UTC
Status: Identified We have temporarily rerouted the affected subnets to other PoPs where sufficient capacity is available. As a result, latency and throughput may be impacted. We will continue to monitor the situation and restore normal routing once conditions stabilize. Affected components SJC10 - San Jose, CA, United States (Degraded performance)
- resolved Mar 15, 2026, 01:01 PM UTC
Status: Resolved The issue has now been resolved. Affected components SJC10 - San Jose, CA, United States (Operational)
Connectivity issues in Berlin, DE (BER2, BER3)
Timeline · 3 updates
- identified Feb 24, 2026, 09:13 PM UTC
Status: Identified We are currently experiencing heavy DDoS attacks affecting our Berlin location. As a temporary measure, we have activated additional DDoS protection capacity to mitigate the impact and maintain service availability. Latency may be temporarily affected while mitigation is in place. Our team continues to monitor the situation closely. We appreciate your understanding and patience. Affected components BER2 - Berlin, Germany (Speedbone) (Degraded performance) BER3 - Berlin, Germany (3U Telecom) (Degraded performance)
- identified Feb 26, 2026, 04:17 PM UTC
Status: Identified We have identified that one of our IP transit providers is currently experiencing capacity constraints due to ongoing DDoS attacks targeting other customers. As a result, we are rerouting traffic to alternative carriers. During this period, latency may be temporarily higher than usual. We will continue to monitor the situation and restore normal routing once conditions stabilize. Affected components BER2 - Berlin, Germany (Speedbone) (Degraded performance) BER3 - Berlin, Germany (3U Telecom) (Degraded performance)
- resolved Mar 15, 2026, 01:01 PM UTC
Status: Resolved The issue has now been resolved. Affected components BER2 - Berlin, Germany (Speedbone) (Operational) BER3 - Berlin, Germany (3U Telecom) (Operational)
Connectivity issues in Seattle, WA, US (SEA02)
Timeline · 4 updates
- identified Feb 23, 2026, 08:17 AM UTC
Status: Identified We are currently experiencing heavy DDoS attacks affecting our Seattle location. Our team is actively mitigating the attack, and connectivity quality may be temporarily impacted. Further updates will be provided as the situation develops. Affected components SEA2 - Seattle, WA, United States (Digital Realty SEA10) (Degraded performance) SEA02 - Seattle, WA, United States (Degraded performance)
- identified Feb 23, 2026, 01:43 PM UTC
Status: Identified Due to the scale of the ongoing DDoS attacks (peaking at approximately 2 Tbps), which exceed our upstream capacity, we have temporarily shut down affected subnets to protect the stability of the network. We are working to restore normal connectivity as mitigation measures are implemented. Further updates will follow. Affected components SEA2 - Seattle, WA, United States (Digital Realty SEA10) (Partial outage) SEA02 - Seattle, WA, United States (Degraded performance)
- identified Feb 23, 2026, 03:19 PM UTC
Status: Identified We have temporarily rerouted the affected subnets to other PoPs where sufficient capacity is available. As a result, latency and throughput may be impacted. We will continue to monitor the situation and restore normal routing once conditions stabilize. Affected components SEA2 - Seattle, WA, United States (Digital Realty SEA10) (Degraded performance) SEA02 - Seattle, WA, United States (Degraded performance)
- resolved Mar 03, 2026, 12:11 PM UTC
Status: Resolved The issue has now been resolved. Affected components SEA2 - Seattle, WA, United States (Digital Realty SEA10) (Operational) SEA02 - Seattle, WA, United States (Operational)
Connectivity issues in Kansas, MO, US (MCI1)
Connectivitiy Issues in Moscow, RU (MOW1)
Timeline · 3 updates
- identified Feb 17, 2026, 03:14 PM UTC
Status: Identified We are currently experiencing heavy DDoS attacks affecting our Moscow location. Due to recent maintenance, some of our network observability tools are still temporarily offline, which may limit real-time visibility during mitigation. Further updates will be provided as the situation develops. Affected components MOW1 - Moscow, RU (M9) (Degraded performance)
- monitoring Feb 17, 2026, 03:49 PM UTC
Status: Monitoring Mitigation has been applied and the network is now stable. We will keep monitoring for any further impact. Affected components MOW1 - Moscow, RU (M9) (Operational)
- resolved Feb 17, 2026, 10:52 PM UTC
Status: Resolved The issue has been resolved. All services are operating normally. Affected components MOW1 - Moscow, RU (M9) (Operational)
Connectivitiy Issues in Berlin, DE (BER2, BER3)
Timeline · 3 updates
- identified Feb 17, 2026, 03:08 PM UTC
Status: Identified We are currently experiencing heavy DDoS attacks affecting our Berlin locations (BER2 and BER3). Our team is actively mitigating the attack, and connectivity quality may be temporarily impacted. Further updates will be provided as the situation develops. Affected components BER3 - Berlin, Germany (3U Telecom) (Degraded performance) BER2 - Berlin, Germany (Speedbone) (Degraded performance)
- identified Feb 17, 2026, 03:49 PM UTC
Status: Identified Mitigation has been applied and the network is now stable. We will keep monitoring for any further impact. Affected components BER3 - Berlin, Germany (3U Telecom) (Operational) BER2 - Berlin, Germany (Speedbone) (Operational)
- resolved Feb 17, 2026, 10:52 PM UTC
Status: Resolved The issue has been resolved. All services are operating normally. Affected components BER2 - Berlin, Germany (Speedbone) (Operational) BER3 - Berlin, Germany (3U Telecom) (Operational)