Misaka Network, Inc.

Outage in Tokyo, JP (NRT04)
Resolved·Full outage

The issue is now resolved.

Fri, Jan 30, 2026, 02:07 PM
(1 week ago)
·
Affected components
Updates

Resolved

The issue is now resolved.

Fri, Jan 30, 2026, 02:07 PM

Monitoring

We can confirm that recovery has been completed for all services except for one hypervisor, where the NVMe SSDs have unfortunately failed.

A technician is currently en route to the facility to investigate further. We will provide additional updates once more information becomes available.

Fri, Jan 30, 2026, 12:33 PM(1 hour earlier)

Monitoring

Most services have now been restored. We are continuing to recover the remaining services that were temporarily failed over to other locations. If you are still experiencing any issues, please open a support ticket so our team can assist you. SLA credits will be applied later today before 22:00 UTC.

Fri, Jan 30, 2026, 10:39 AM(1 hour earlier)

Identified

We identified a discrepancy between our inventory records and the actual system configuration, which caused boot failures. The issue has been resolved, and affected VMs are expected to start within the next 30 minutes.

Fri, Jan 30, 2026, 10:12 AM(26 minutes earlier)

Identified

We have identified that some hypervisors require manual intervention, and a technician has been dispatched to the facility for further investigation.

The network is now fully operational. Further updates will be provided as more information becomes available.

Fri, Jan 30, 2026, 09:29 AM(43 minutes earlier)

Identified

Services are being recovered sequentially. Based on current progress, we are targeting completion within the next 1–2 hours, subject to change as recovery continues.

We appreciate your patience and understanding.

Fri, Jan 30, 2026, 08:58 AM(31 minutes earlier)

Identified

The matter has been escalated internally and is proceeding through the appropriate channels.

We do not yet have a confirmed ETA and will share updates as they become available.

Fri, Jan 30, 2026, 08:04 AM(53 minutes earlier)

Identified

Our team is still actively working on the issue. We will share another update as soon as we have new information.

Fri, Jan 30, 2026, 07:28 AM(36 minutes earlier)

Identified

We have identified the issue and escalated it to the data center. We will provide further updates here as soon as more information becomes available.

Fri, Jan 30, 2026, 05:28 AM(2 hours earlier)

Investigating

We're currently looking into this case and will provide an update as soon as possible.

Fri, Jan 30, 2026, 04:51 AM(36 minutes earlier)
Powered by