What is Misaka Network's uptime?

Over the last 90 days, Misaka Network reported 98.72% uptime on its official status page. That figure is calculated from the public incident timeline at https://misaka.fail — each minute of degraded, partial-outage, or major-outage status counts against the total. Sign up to Pingoru free to see Misaka Network's uptime history rolling forward in real time.

Has Misaka Network had outages in 2026?

Yes — Misaka Network has had 11 incidents reported on its official status page so far in 2026. The full timeline (start times, durations, components affected) is shown above on this page. Pingoru re-checks the status page every 5 minutes so the count stays current.

When was the last Misaka Network outage?

The most recent Misaka Network incident was "Maintenance: Scheduled Database Maintenance", which started on May 17, 2026 and was resolved on May 17, 2026. Pingoru captured this directly from https://misaka.fail. See the full incident card above for affected components and the update timeline.

How often does Misaka Network have outages?

Based on the last 90 days, Misaka Network averages 3.7 reported incidents per month on its official status page. Pingoru tracks each one with start time, duration, severity, and affected components — so you can see the pattern at a glance instead of digging through the vendor's archive.

Where is Misaka Network's status page?

Misaka Network's official status page is https://misaka.fail. Pingoru polls it every 5 minutes and renders the same data here, alongside every other cloud or SaaS provider you depend on — so you can spot multi-vendor incidents (e.g. AWS + Stripe + Cloudflare degrading at the same minute) without flipping between tabs.

Is Misaka Network down right now?

Misaka Network is having a partial outage. Pingoru checks the official status page every 5 minutes and flips this headline the moment Misaka Network reports a change. Current status is based on 81 tracked services.

How does Pingoru know if Misaka Network is down?

We read https://misaka.fail directly, using Misaka Network's own status page. If the vendor reports an incident, you see it within one check cycle — not after someone manually marks the page as down.

Where can I get notified when Misaka Network has an outage?

Create a free Pingoru account and add Misaka Network as a monitor. You can filter to specific services, pick severity thresholds, and route alerts via email, Slack, Discord, or a webhook.

Misaka Network's status page says the service is up, but I'm having issues — what's wrong?

Three common reasons: • A real Misaka Network incident that hasn't been acknowledged on their public status page yet — vendor status pages are updated manually and typically lag the first customer reports by 10–30 minutes. • A regional or account-scoped issue affecting a subset of customers — these rarely trigger a global status-page change. • A local problem: ISP / DNS / your own software. Try reproducing from a mobile data connection and from a different network to isolate. If you suspect a real Misaka Network issue that isn't reflected yet, contact their support to escalate. Subscribing here means you get the alert the moment they do post an update.

Where does Pingoru get the official Misaka Network status?

We use Misaka Network's own status page at https://misaka.fail. Nothing is read in a way the vendor hasn't explicitly made public — we use the same data their own dashboard uses. So our data is as accurate as what you'd see loading the status page yourself, but rolled into one dashboard alongside every other service you depend on.

What does "Partial Outage" mean?

Misaka Network has a partial outage — one or more components are down, but the rest of the service is operational.

Is Misaka Network down?

Last checked just now

Current status

Misaka Network is having a partial outage

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

Get alerts when Misaka Network breaks → View Misaka Network outage history →

Free · no credit card

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

Misaka Network is reporting a partial outage right now (last checked just now). 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 81 Misaka Network services and has captured 12 incidents in the last 90 days (98.72% 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:

Genesys Cloud View all 6,000+ providers

Misaka Network uptime 98.72% uptime · past 90 days

Mon Wed Fri

MarAprMayJun

Less More

Active incident 1

Connectivity issues in Kansas, MO, US (MCI1)

Ongoing ● 108d 23h

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

Connectivity issues in Moscow, RU (MOW1)

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…
Connectivity Issues in London / Slough (LON5,LON7)

Resolved —

Started Apr 04, 2026, 05:35 PM UTC · Resolved Apr 04, 2026, 05:35 PM 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 · 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)
- 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)
Latest: Status: Resolved The issue has been resolved. Affected components AP East (tpe1) (Operational) ZRH01 - Zürich , Switzerland (Operational) SJC10 - San Jose, CA, United States (Opera…
Connectivity Issues in London / Slough (LON5,LON7)

Resolved 1m

Started Apr 04, 2026, 05:33 PM UTC · Resolved Apr 04, 2026, 05:35 PM UTC

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 · 3 incidents View full outage history →

Connectivity issues in Moscow, RU (MOW1) Resolved

Started May 04, 2026, 08:04 AM UTC · Resolved May 04, 2026, 08:04 AM UTC · —
Connectivity Issues in London / Slough (LON5,LON7) Resolved

Started Apr 04, 2026, 05:35 PM UTC · Resolved Apr 04, 2026, 05:35 PM UTC · —
Connectivity Issues in London / Slough (LON5,LON7) Resolved

Started Apr 04, 2026, 05:33 PM UTC · Resolved Apr 04, 2026, 05:35 PM UTC · 1m