Is Misaka Network down?

Last checked 1m ago
Current status
Misaka Network is having a partial outage

Active incident: Connectivity issues in Kansas, MO, US (MCI1)

Official status page: https://misaka.fail · Polled every 5 minutes · 85 components tracked

Misaka Network is reporting a partial outage right now (last checked 1m ago). Some components are affected; others remain operational.

Real-time Misaka Network status, recent outages, and incident history — pulled directly from Misaka Network's official status page at https://misaka.fail every 5 minutes. Pingoru tracks 85 Misaka Network services and has captured 7 incidents in the last 90 days (99.31% uptime). Get email, Slack, Discord, or webhook alerts the moment Misaka Network reports a new incident — free for 5 monitors, no credit card.

Users who monitor Misaka Network also follow these Cloud Infrastructure services: Amazon Web Services DigitalOcean Cisco Umbrella Wasabi Vercel Hetzner HashiCorp Egnyte Dyn Genesys Cloud View all 6,000+ providers
Misaka Network uptime 99.31% uptime · past 90 days
Mon Wed Fri
MayJunJul
Less More

Active incident 1

  1. Ongoing ● 157d 4h
    Started Feb 24, 2026, 09:11 PM UTC
    Timeline · 1 update
    • identified · Feb 24, 2026, 09:11 PM UTC

      Status: Identified We are currently experiencing heavy DDoS attacks affecting our Kansas location. Ingress traffic is now being rerouted to our nearest POPs with enough capacity to handle the attack traffic. We are actively working on mitigation strategies to restore normal service. Further updates will be provided as the situation develops. Affected components MCI1 - Kansas City, MO, United States (NOCIX) (Degraded performance)

    Latest: Status: Identified We are currently experiencing heavy DDoS attacks affecting our Kansas location. Ingress traffic is now being rerouted to our nearest POPs with enough capacity to…

Recent outages & incidents

Past 90 days
  1. Resolved
    Started Jul 09, 2026, 11:15 AM UTC · Resolved Jul 09, 2026, 11:15 AM UTC
    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)

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

  2. Resolved
    Started Jul 07, 2026, 02:41 PM UTC · Resolved Jul 07, 2026, 02:41 PM UTC
    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)

    Latest: 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 …

  3. Resolved
    Started Jun 24, 2026, 08:47 AM UTC · Resolved Jun 24, 2026, 08:47 AM UTC
    MIA02 - Miami, FL, United States
    Timeline · 7 updates
    • identified · Jun 23, 2026, 10:41 PM UTC

      Status: Identified We are aware that the facility at US-MIA10, 36 NE 2nd Street, is currently experiencing a power outage. According to the latest update from the facility engineering team, the incident has been escalated from Yellow to Red. Generators 1 and 2 have failed, and the 4th floor is currently without power. The facility team has engaged the vendor to investigate the issue and perform the necessary repairs. We are closely monitoring the situation and will provide further updates as soon as more information becomes available. We apologize for the disruption and appreciate your patience while the facility team works to restore power. Affected components MIA2 - Miami, FL, US (Colohouse) (Full outage) MIA02 - Miami, FL, United States (Full outage)

    • identified · Jun 23, 2026, 11:42 PM UTC

      Status: Identified We have received an update from the facility engineering team regarding the utility transient event at US-MIA10, 36 NE 2nd Street. "Utility power has been restored to the 4th floor. The generator vendor has been engaged and is currently en route to the site, with an estimated arrival time of 8:00 PM. " However, our devices remain offline at this time. We are continuing to monitor the situation closely and will provide further updates as soon as more information becomes available. Affected components MIA02 - Miami, FL, United States (Full outage) MIA2 - Miami, FL, US (Colohouse) (Full outage)

    • identified · Jun 24, 2026, 12:32 AM UTC

      Status: Identified We can confirm that power has been restored and services are now back online. Due to today’s outage, we will proceed with our previously planned migration to Equinix MI1. This migration may require approximately one additional hour before services are fully recovered. We will continue to monitor the situation and provide further updates as needed. Affected components MIA2 - Miami, FL, US (Colohouse) (Full outage) MIA02 - Miami, FL, United States (Full outage)

    • identified · Jun 24, 2026, 03:01 AM UTC

      Status: Identified Our new cluster is currently experiencing boot issues. As a result, we are physically relocating the existing servers from ColoHouse to Equinix MI1. We will provide another update once the servers arrive at Equinix MI1 and we have more information on the recovery timeline. Affected components MIA2 - Miami, FL, US (Colohouse) (Full outage) MIA02 - Miami, FL, United States (Full outage)

    • resolved · Jun 24, 2026, 05:12 AM UTC

      Status: Resolved Services should now be fully restored and operational. As compensation for the extended downtime, all affected customers will receive one month of complimentary service. We expect this to be applied before this Sunday. We sincerely apologize for the prolonged outage, as well as the poor communication during the outage and migration. We understand the impact this caused and appreciate your patience while we worked to restore service. Affected components MIA2 - Miami, FL, US (Colohouse) (Operational) MIA02 - Miami, FL, United States (Operational)

    • monitoring · Jun 24, 2026, 05:23 AM UTC

      Status: Monitoring IPv6 connectivity may currently be unavailable for some customers. Our team is actively working on the issue and expects it to be resolved today. IPv4 connectivity should remain unaffected. A further update will be provided once IPv6 connectivity has been fully restored. Affected components MIA2 - Miami, FL, US (Colohouse) (Partial outage) MIA02 - Miami, FL, United States (Operational)

    • resolved · Jun 24, 2026, 08:47 AM UTC

      Status: Resolved IPv6 connectivity has been restored and should now be fully operational. Please contact support if you continue to experience any connectivity issues. Affected components MIA2 - Miami, FL, US (Colohouse) (Operational) MIA02 - Miami, FL, United States (Operational)

    Latest: Status: Resolved IPv6 connectivity has been restored and should now be fully operational. Please contact support if you continue to experience any connectivity issues. Affected com…

  4. Resolved
    Started May 04, 2026, 08:04 AM UTC · Resolved May 04, 2026, 08:04 AM UTC
    Package MirrorsZRH01 - Zürich , SwitzerlandVIE01 - Vienna, AustriaMail QueueFRA08 - Frankfurt, GermanyMIL02 - Milan, ItalyMAD02 - Madrid, SpainPRG02 - Prague, Czech RepublicICN05 - Seoul, South KoreaS3 Gateway
    Timeline · 2 updates
    • identified · May 04, 2026, 07:44 AM UTC

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

    • resolved · May 04, 2026, 08:04 AM UTC

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

    Latest: Status: Resolved The incident is resolved. The BGP sessions with the affected carrier have fully recovered. We have confirmed that we have been receiving full routing tables from t…

See the full Misaka Network outage history

1 more incident in the last 90 days, plus the full multi-year archive of per-service events and update timelines.

Browse Misaka Network outage history →

Or sign up free to get alerts when Misaka Network breaks · 10 free monitors · No credit card

Outage history

Past 90 days · 4 incidents View full outage history →