Misaka Network Outage History

Misaka Network is up right now

There were 8 Misaka Network outages since February 17, 2026 totaling 1468h 17m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://misaka.fail

Minor April 4, 2026

Connectivity Issues in London / Slough (LON5,LON7)

Detected by Pingoru
Apr 04, 2026, 05:35 PM UTC
Resolved
Apr 04, 2026, 05:35 PM UTC
Duration
Affected: Package MirrorsZRH01 - Zürich , SwitzerlandVIE01 - Vienna, AustriaMail QueueFRA08 - Frankfurt, GermanyMIL02 - Milan, ItalyMAD02 - Madrid, SpainPRG02 - Prague, Czech RepublicICN05 - Seoul, South KoreaS3 GatewayBER03- Berlin, GermanyPublic APICloud ServersAuthoritative DNSRecursive DNSDNS UpdatesAnalyticsTraffic SteeringIAD01 - Ashburn, VA, United StatesEWR02 - Secaucus, NJ, United StatesMIA02 - Miami, FL, United StatesSJC10 - San Jose, CA, United StatesLAX02 - Los Angeles, CA, United StatesSEA02 - Seattle, WA, United StatesSTO02 - Stockholm, SwedenOSL02 - Oslo, NorwayCPH02 - Copenhagen, DenmarkDUB02 - Dublin, IrelandBRU02 - Brussels, BelgiumMRS01 - Marseille, FranceWAW03 - Warsaw, PolandZAG01 - Zagreb, CroatiaSOF01 - Sofia, BulgariaLIS01 - Lisbon, PortugalATH01 - Athens, GraceKBP01 - Kyiv, UkraineIST01 - Istanbul, TurkeyOTP01 - Bucharest, RomaniaLOS02 - Lagos, NigeriaGRU03 - São Paulo, BrazilLED02 - St. Petersburg, RussiaKHV01 - Khabarovsk, RussiaYUL04 - Montréal, QC, CanadaFlow collector EUFlow collector USgNMI Telemetry EU
Timeline · 2 updates
  1. identified Apr 04, 2026, 05:28 PM UTC

    Status: Identified We are aware that connectivity between Slough and Telehouse North was temporarily unavailable due to a misconfiguration. As some prefixes are configured to be announced only at Telehouse North, customers may have experienced a brief disconnection. Affected components JNB1 - Johannesburg, South Africa (Teraco JB1) (Operational) MIL02 - Milan, Italy (Operational) SOF01 - Sofia, Bulgaria (Operational) SIN3 - Singapore (Equinix SG3) (Operational) NRT4 - Tokyo, Japan (Equinix TY8) (Operational) LON5 - Slough, United Kingdom (Equinix LD5) (Partial outage) ZAG01 - Zagreb, Croatia (Operational) DNS Updates (Operational) LAX2 - Los Angeles, CA, United States (CoreSite LA2) (Operational) DAL10 - Dallas, TX, United States (Equinix DA10) (Operational) MIA02 - Miami, FL, United States (Operational) STO02 - Stockholm, Sweden (Operational) GRU03 - São Paulo, Brazil (Operational) DUB02 - Dublin, Ireland (Operational) VIE01 - Vienna, Austria (Operational) IAD1 - Ashburn, VA, United States (Equinix DC10) (Operational) CPH02 - Copenhagen, Denmark (Operational) EWR02 - Secaucus, NJ, United States (Operational) Flow collector EU (Operational) gNMI Telemetry EU (Operational) Flow collector US (Operational) Public API (Operational) MOW1 - Moscow, RU (M9) (Operational) Cloud Servers (Operational) AP East (hkg12) (Operational) AP East (tpe1) (Operational) S3 EU Central (Berlin) (Operational) ATH01 - Athens, Grace (Operational) Traffic Steering (Operational) OTP01 - Bucharest, Romania (Operational) WAW03 - Warsaw, Poland (Operational) NetBox (US East) (Operational) AMS2 - Amsterdam, Netherlands (NorthC Amsterdam) (Operational) FRA08 - Frankfurt, Germany (Operational) AP Northeast (nrt4) (Operational) LIS01 - Lisbon, Portugal (Operational) SEA02 - Seattle, WA, United States (Operational) PRG02 - Prague, Czech Republic (Operational) OSL02 - Oslo, Norway (Operational) US West (lax1) (Operational) ICN05 - Seoul, South Korea (Operational) BER3 - Berlin, Germany (3U Telecom) (Operational) ZRH01 - Zürich , Switzerland (Operational) KBP01 - Kyiv, Ukraine (Operational) S3 US East (Ashburn) (Operational) KHV01 - Khabarovsk, Russia (Operational) EWR2 - Secaucus, NJ, United States (Equinix NY2) (Operational) TPE1 - Taipei (Chief LY) (Operational) SEA2 - Seattle, WA, United States (Digital Realty SEA10) (Operational) MAD02 - Madrid, Spain (Operational) LOS02 - Lagos, Nigeria (Operational) LON2 - London, United Kingdom (Telehouse Docklands North) (Operational) LED02 - St. Petersburg, Russia (Operational) IAD01 - Ashburn, VA, United States (Operational) SJC10 - San Jose, CA, United States (Equinix SV10) (Operational) Package Mirrors (Operational) HKG12- Hong Kong (Equinix HK2) (Operational) MCI1 - Kansas City, MO, United States (NOCIX) (Operational) Recursive DNS (Operational) BER2 - Berlin, Germany (Speedbone) (Operational) LAX7 - Los Angeles, CA, United States (1200W) (Operational) BRU02 - Brussels, Belgium (Operational) SJC10 - San Jose, CA, United States (Operational) S3 Gateway (Operational) YUL04 - Montréal, QC, Canada (Operational) Mail Queue (Operational) Authoritative DNS (Operational) MRS01 - Marseille, France (Operational) EU Central (ber3) (Operational) IST01 - Istanbul, Turkey (Operational) LAX02 - Los Angeles, CA, United States (Operational) Analytics (Operational) BER03- Berlin, Germany (Operational) MIA2 - Miami, FL, US (Colohouse) (Operational) AP Southeast (sin3) (Operational) US East (iad1) (Operational)

  2. resolved Apr 04, 2026, 05:35 PM UTC

    Status: Resolved The issue has been resolved. Affected components AP East (tpe1) (Operational) ZRH01 - Zürich , Switzerland (Operational) SJC10 - San Jose, CA, United States (Operational) JNB1 - Johannesburg, South Africa (Teraco JB1) (Operational) Recursive DNS (Operational) NRT4 - Tokyo, Japan (Equinix TY8) (Operational) US East (iad1) (Operational) DAL10 - Dallas, TX, United States (Equinix DA10) (Operational) ZAG01 - Zagreb, Croatia (Operational) Cloud Servers (Operational) DNS Updates (Operational) IST01 - Istanbul, Turkey (Operational) LED02 - St. Petersburg, Russia (Operational) EWR02 - Secaucus, NJ, United States (Operational) EU Central (ber3) (Operational) OSL02 - Oslo, Norway (Operational) MIA2 - Miami, FL, US (Colohouse) (Operational) TPE1 - Taipei (Chief LY) (Operational) AP Northeast (nrt4) (Operational) IAD01 - Ashburn, VA, United States (Operational) HKG12- Hong Kong (Equinix HK2) (Operational) DUB02 - Dublin, Ireland (Operational) NetBox (US East) (Operational) VIE01 - Vienna, Austria (Operational) AP Southeast (sin3) (Operational) US West (lax1) (Operational) SJC10 - San Jose, CA, United States (Equinix SV10) (Operational) Mail Queue (Operational) SOF01 - Sofia, Bulgaria (Operational) SIN3 - Singapore (Equinix SG3) (Operational) CPH02 - Copenhagen, Denmark (Operational) S3 EU Central (Berlin) (Operational) ATH01 - Athens, Grace (Operational) LIS01 - Lisbon, Portugal (Operational) OTP01 - Bucharest, Romania (Operational) Flow collector US (Operational) MCI1 - Kansas City, MO, United States (NOCIX) (Operational) EWR2 - Secaucus, NJ, United States (Equinix NY2) (Operational) FRA08 - Frankfurt, Germany (Operational) AP East (hkg12) (Operational) WAW03 - Warsaw, Poland (Operational) S3 Gateway (Operational) KHV01 - Khabarovsk, Russia (Operational) Authoritative DNS (Operational) ICN05 - Seoul, South Korea (Operational) SEA02 - Seattle, WA, United States (Operational) gNMI Telemetry EU (Operational) S3 US East (Ashburn) (Operational) MOW1 - Moscow, RU (M9) (Operational) Package Mirrors (Operational) LON2 - London, United Kingdom (Telehouse Docklands North) (Operational) LOS02 - Lagos, Nigeria (Operational) MIL02 - Milan, Italy (Operational) BER03- Berlin, Germany (Operational) LAX7 - Los Angeles, CA, United States (1200W) (Operational) Public API (Operational) YUL04 - Montréal, QC, Canada (Operational) BER2 - Berlin, Germany (Speedbone) (Operational) LON5 - Slough, United Kingdom (Equinix LD5) (Operational) LAX2 - Los Angeles, CA, United States (CoreSite LA2) (Operational) BER3 - Berlin, Germany (3U Telecom) (Operational) KBP01 - Kyiv, Ukraine (Operational) LAX02 - Los Angeles, CA, United States (Operational) PRG02 - Prague, Czech Republic (Operational) GRU03 - São Paulo, Brazil (Operational) MRS01 - Marseille, France (Operational) AMS2 - Amsterdam, Netherlands (NorthC Amsterdam) (Operational) MIA02 - Miami, FL, United States (Operational) Flow collector EU (Operational) Analytics (Operational) Traffic Steering (Operational) IAD1 - Ashburn, VA, United States (Equinix DC10) (Operational) STO02 - Stockholm, Sweden (Operational) BRU02 - Brussels, Belgium (Operational) SEA2 - Seattle, WA, United States (Digital Realty SEA10) (Operational) MAD02 - Madrid, Spain (Operational)

Read the full incident report →

Minor March 15, 2026

Connectivity issues in San Jose, CA, US (SJC10)

Detected by Pingoru
Mar 15, 2026, 01:01 PM UTC
Resolved
Mar 15, 2026, 01:01 PM UTC
Duration
Affected: SJC10 - San Jose, CA, United States
Timeline · 3 updates
  1. 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)

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

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

Read the full incident report →

Minor March 15, 2026

Connectivity issues in Berlin, DE (BER2, BER3)

Detected by Pingoru
Mar 15, 2026, 01:01 PM UTC
Resolved
Mar 15, 2026, 01:01 PM UTC
Duration
Timeline · 3 updates
  1. 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)

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

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

Read the full incident report →

Minor March 15, 2026

Connectivity issues in Moscow, RU (MOW1)

Detected by Pingoru
Mar 15, 2026, 01:01 PM UTC
Resolved
Mar 15, 2026, 01:01 PM UTC
Duration
Timeline · 3 updates
  1. identified Feb 23, 2026, 09:50 AM UTC

    Status: Identified We are currently experiencing heavy DDoS attacks affecting our Moscow 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 MOW1 - Moscow, RU (M9) (Degraded performance)

  2. identified Feb 23, 2026, 11:20 AM UTC

    Status: Identified We have implemented additional mitigation policies to address the ongoing attacks. During this process, reachability and performance may be temporarily affected. We apologize for any inconvenience this may cause and appreciate your understanding. Affected components MOW1 - Moscow, RU (M9) (Degraded performance)

  3. resolved Mar 15, 2026, 01:01 PM UTC

    Status: Resolved The issue has now been resolved. Affected components MOW1 - Moscow, RU (M9) (Operational)

Read the full incident report →

Minor March 3, 2026

Connectivity issues in Seattle, WA, US (SEA02)

Detected by Pingoru
Mar 03, 2026, 12:11 PM UTC
Resolved
Mar 03, 2026, 12:11 PM UTC
Duration
Affected: SEA02 - Seattle, WA, United States
Timeline · 4 updates
  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)

Read the full incident report →

Minor February 17, 2026

Connectivitiy Issues in Moscow, RU (MOW1)

Detected by Pingoru
Feb 17, 2026, 10:52 PM UTC
Resolved
Feb 17, 2026, 10:52 PM UTC
Duration
Timeline · 3 updates
  1. 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)

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

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

Read the full incident report →

Minor February 17, 2026

Connectivitiy Issues in Berlin, DE (BER2, BER3)

Detected by Pingoru
Feb 17, 2026, 10:52 PM UTC
Resolved
Feb 17, 2026, 10:52 PM UTC
Duration
Timeline · 3 updates
  1. 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)

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

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

Read the full incident report →

Looking to track Misaka Network downtime and outages?

Pingoru polls Misaka Network's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Misaka Network reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Misaka Network alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Misaka Network for free

5 free monitors · No credit card required