Misaka Network Outage History

Misaka Network had 25 outages in the last 2 years totaling 2525h 16m of downtime — averaging 1 incident per month.

There were 25 Misaka Network outages since July 10, 2025 totaling 2525h 16m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://misaka.fail

Minor July 9, 2026

Connectivity issues in Berlin, DE (BER2, BER3)

Detected by Pingoru: Jul 09, 2026, 11:15 AM UTC
Resolved: Jul 09, 2026, 11:15 AM UTC
Duration: —

Timeline · 3 updates

identified Jun 27, 2026, 10:31 PM UTC

Status: Identified Our Berlin network POP, BER2, experienced a brief power issue a few minutes ago. Services have now been restored. We are continuing to monitor the situation and will provide further updates if needed. Affected components BER2 - Berlin, Germany (Speedbone) (Degraded performance) BER3 - Berlin, Germany (3U Telecom) (Degraded performance)
monitoring Jun 28, 2026, 12:47 PM UTC

Status: Monitoring Unfortunately, we have not yet received further details about the incident from the responsible data center operator. Services have since been restored, and we are continuing to monitor the situation. Affected components BER2 - Berlin, Germany (Speedbone) (Operational) BER3 - Berlin, Germany (3U Telecom) (Operational)
resolved Jul 09, 2026, 11:15 AM UTC

Status: Resolved The incident has now been resolved. Affected components BER2 - Berlin, Germany (Speedbone) (Operational) BER3 - Berlin, Germany (3U Telecom) (Operational)

Read the full incident report →

Minor July 7, 2026

Connectivity issues in Miami, FL, US (MIA1)

Detected by Pingoru: Jul 07, 2026, 02:41 PM UTC
Resolved: Jul 07, 2026, 02:41 PM UTC
Duration: —

Affected: MIA02 - Miami, FL, United StatesMIA01 - Miami, FL, United States

Timeline · 2 updates

investigating Jul 07, 2026, 02:10 PM UTC

Status: Investigating We are aware of the connectivity issues in Miami and have engaged our upstream provider for further investigation. We will continue to monitor the situation and provide updates as more information becomes available. Affected components MIA02 - Miami, FL, United States (Full outage) MIA01 - Miami, FL, United States (Full outage)
resolved Jul 07, 2026, 02:41 PM UTC

Status: Resolved The incident has now been resolved. Connectivity in Miami has been restored and should be operating normally. Please contact support if you continue to experience any issues. Affected components MIA02 - Miami, FL, United States (Operational) MIA01 - Miami, FL, United States (Operational)

Read the full incident report →

Minor June 24, 2026

Power outage in Miami, FL, US (MIA02)

Detected by Pingoru: Jun 24, 2026, 08:47 AM UTC
Resolved: Jun 24, 2026, 08:47 AM UTC
Duration: —

Affected: MIA02 - Miami, FL, United States

Timeline · 7 updates

Read the full incident report →

Minor May 4, 2026

Connectivity issues in Moscow, RU (MOW1)

Detected by Pingoru: May 04, 2026, 08:04 AM UTC
Resolved: May 04, 2026, 08:04 AM 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

Read the full incident report →

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: —

Timeline · 2 updates

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

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)

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

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)

Read the full incident report →

Minor February 24, 2026

Connectivity issues in Kansas, MO, US (MCI1)

Detected by Pingoru: Feb 24, 2026, 09:11 PM UTC
Resolved: Apr 27, 2026, 01:28 AM UTC
Duration: 61d 4h

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

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)

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

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)