Misaka Network incident

Connectivity issues in Seattle, WA, US (SEA02)

Minor Resolved View vendor source →

Misaka Network experienced a minor incident on March 3, 2026 affecting SEA02 - Seattle, WA, United States, lasting —. The incident has been resolved; the full update timeline is below.

Started
Mar 03, 2026, 12:11 PM UTC
Resolved
Mar 03, 2026, 12:11 PM UTC
Duration
Detected by Pingoru
Mar 03, 2026, 12:11 PM UTC

Affected components

SEA02 - Seattle, WA, United States

Update timeline

  1. 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)

  2. 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)

  3. 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)

  4. 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)