Is Misaka Network down?

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

Active incident: [Security Disclosure] Friday, October 23: Support Ticket Ac…

  • Official status page: misaka.fail
  • Checked every 5 minutes
  • 98 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 misaka.fail every 5 minutes. Pingoru tracks 98 Misaka Network services and has captured 9 incidents in the last 90 days (99.88% uptime). Get email, Slack, Discord, or webhook alerts the moment Misaka Network reports a new incident, free for 3 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 8,000+ providers
Misaka Network uptime 99.88% uptime · past 90 days
Mon Wed Fri
AugSepOct
Less More

Active incident 1

  1. Ongoing ● 7d 8h
    Started Oct 23, 2026, 12:32 PM UTC
    Timeline · 1 update
    • investigating · Oct 23, 2026, 12:32 PM UTC

      Status: Investigating On October 22, we identified and fixed an authorization flaw in our support ticket system that could allow signed-in users with support access to view or modify tickets belonging to other accounts. Our investigation to date indicates that some support tickets may have been accessed without authorization. Logs also show successful requests to update some of these tickets. We are continuing to review the scope of access and any unauthorized changes. The information available through these tickets included first names and the contents of support conversations. Our review found email addresses, customer IP addresses, the last few digits of payment card numbers, and one historical server password in ticket content. We have not found an active instance associated with that password, but this does not establish whether the credential remains in use elsewhere. Protected attachments have separate authorization checks, which this ticket vulnerability did not bypass. We have not confirmed unauthorized downloads of those files. Publicly accessible external links included in ticket content could still be opened. As a precaution, we have temporarily deployed additional security measures, which may occasionally block legitimate access. If you are unable to access the control panel, please contact us at [[email protected]](mailto:[email protected]). What you should do • If you shared passwords, API keys, tokens, or other credentials in a support ticket, rotate any that remain in use, including credentials reused on other services. • Review access logs for those services for unusual activity. • Check your support history for unrecognized replies or status changes, and report anything unexpected to our support team. • Be cautious of any ticket reply asking for credentials or payment details, or containing unexpected links. Do not share passwords or other secrets in support tickets. We will contact affected account holders directly as we confirm their individual impact and provide further updates on our status page. We apologize for this failure and the risk it has created for our customers.

    Latest: Status: Investigating On October 22, we identified and fixed an authorization flaw in our support ticket system that could allow signed-in users with support access to view or modi…

Recent outages & incidents

Past 90 days
  1. Resolved 24m
    Started Oct 03, 2026, 03:02 PM UTC · Resolved Oct 03, 2026, 03:26 PM UTC
    MOW01 - Moscow, Russia
    Timeline · 2 updates
    • identified · Oct 03, 2026, 03:02 PM UTC

      Status: Identified A power outage at the Moscow M9 datacenter is affecting some equipment. Affected components MOW1 - Moscow, RU (M9) (Partial outage) MOW01 - Moscow, Russia (Partial outage)

    • resolved · Oct 03, 2026, 03:26 PM UTC

      Status: Resolved Service has been restored for the affected devices at Moscow M9. This incident is resolved. Affected components MOW01 - Moscow, Russia (Operational) MOW1 - Moscow, RU (M9) (Operational)

    Latest: Status: Resolved Service has been restored for the affected devices at Moscow M9. This incident is resolved. Affected components MOW01 - Moscow, Russia (Operational) MOW1 - Moscow,…

  2. Resolved 4d 17h
    Started Sep 28, 2026, 09:33 PM UTC · Resolved Oct 03, 2026, 03:07 PM UTC
    Timeline · 4 updates
    • identified · Sep 28, 2026, 09:33 PM UTC

      Status: Identified We're aware that one of our hypervisors in Taipei is currently down. We're looking into it. Affected components TPE1 - Taipei (Chief LY) (Partial outage)

    • identified · Sep 28, 2026, 11:09 PM UTC

      Status: Identified We have identified the issue and are applying the fix. Affected components TPE1 - Taipei (Chief LY) (Partial outage)

    • identified · Sep 29, 2026, 12:21 AM UTC

      Status: Identified The issue has resolved Affected components TPE1 - Taipei (Chief LY) (Operational)

    • resolved · Oct 03, 2026, 03:07 PM UTC

      Status: Resolved The issue has resolved Affected components TPE1 - Taipei (Chief LY) (Operational)

    Latest: Status: Resolved The issue has resolved Affected components TPE1 - Taipei (Chief LY) (Operational)

  3. Resolved 14m
    Started Sep 25, 2026, 09:55 AM UTC · Resolved Sep 25, 2026, 10:10 AM UTC
    Timeline · 2 updates
    • identified · Sep 25, 2026, 09:55 AM UTC

      Status: Identified We are aware that one of our transit connections in Hong Kong (HKG12) experienced a brief outage due to a max prefix limit being reached on the BGP session. The issue has been resolved and BGP sessions are currently recovering. We apologize for any inconvenience caused. Affected components HKG12- Hong Kong (Equinix HK2) (Degraded performance)

    • resolved · Sep 25, 2026, 10:10 AM UTC

      Status: Resolved The issue has been resolved. Affected components HKG12- Hong Kong (Equinix HK2) (Operational)

    Latest: Status: Resolved The issue has been resolved. Affected components HKG12- Hong Kong (Equinix HK2) (Operational)

  4. Resolved 33m
    Started Aug 18, 2026, 05:16 PM UTC · Resolved Aug 18, 2026, 05:49 PM UTC
    Timeline · 2 updates
    • investigating · Aug 18, 2026, 05:16 PM UTC

      Status: Investigating The facility experienced a power outage affecting some network infrastructure. As a result, our PITER-IX port went down. Customers with workloads in this region may experience intermittent connectivity issues. Affected components MOW1 - Moscow, RU (M9) (Degraded performance)

    • resolved · Aug 18, 2026, 05:49 PM UTC

      Status: Resolved Services have been restored. We are continuing to monitor the situation closely to ensure stability. Affected components MOW1 - Moscow, RU (M9) (Operational)

    Latest: Status: Resolved Services have been restored. We are continuing to monitor the situation closely to ensure stability. Affected components MOW1 - Moscow, RU (M9) (Operational)

  5. Resolved 8d 8h
    Started Aug 12, 2026, 04:01 AM UTC · Resolved Aug 20, 2026, 12:58 PM UTC
    DUB02 - Dublin, Ireland
    Timeline · 3 updates
    • investigating · Aug 12, 2026, 04:01 AM UTC

      Status: Investigating We are aware of the connectivity issues in Dublin 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 DUB02 - Dublin, Ireland (Partial outage)

    • monitoring · Aug 12, 2026, 04:28 AM UTC

      Status: Monitoring We can confirm that connectivity has now been restored. Affected components DUB02 - Dublin, Ireland (Operational)

    • resolved · Aug 20, 2026, 12:58 PM UTC

      Status: Resolved The issue has now been resolved. Affected components DUB02 - Dublin, Ireland (Operational)

    Latest: Status: Resolved The issue has now been resolved. Affected components DUB02 - Dublin, Ireland (Operational)

See the full Misaka Network outage history

2 more incidents 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

Incident record

Since April 2026 · incident.io · 98 components checked every 5 minutes
37incidents recorded
35last 12 months
7last 90 days
12 daystypical duration, 12 months

The longest incident in the last year, Connectivity issues in Kansas, MO, US (MCI1) on February 24, 2026, ran for 165 days. 14 maintenance windows announced in the same period.

Most affected components, last 12 months

  • MIA02 - Miami, FL, United States4
  • DUB02 - Dublin, Ireland3
  • SEA02 - Seattle, WA, United States3
  • SJC10 - San Jose, CA, United States3
  • ATH01 - Athens, Grace2

Latest incidents

  • [Security Disclosure] Friday, October 23: Support Ticket Access Control Vulnerability October 23, 2026 · still open · major outage

    Status: Investigating On October 22, we identified and fixed an authorization flaw in our support ticket system that could allow signed-in users with support…

  • Power outage at Moscow, RU (MOW1) October 3, 2026 · 24 minutes · degraded service

    Status: Identified A power outage at the Moscow M9 datacenter is affecting some equipment. Affected components MOW1 - Moscow, RU (M9) (Partial outage) MOW01 -…

  • Hypervisor outage in Taipei (TPE01) September 28, 2026 · 5 days · degraded service

    Status: Identified We're aware that one of our hypervisors in Taipei is currently down. We're looking into it. Affected components TPE1 - Taipei (Chief LY)…

Outage history

Past 90 days · 7 incidents View full outage history →