Find a service or website

Type at least 2 characters to search.

IDC Frontier ransomware outage disrupts 495 customers, government websites and Nissui logistics

October 8, 2026
Illustrative smartphone cybersecurity image with a shield and padlock against green digital code; not a photograph of IDC Frontier’s affected systems.

A ransomware attack on IDC Frontier’s cloud infrastructure has disrupted services for 495 corporate and municipal customers in Japan, with effects reaching government websites and frozen-food logistics. The SoftBank subsidiary reported the incident on October 7; by October 8, reporting showed that some dependent operations were still unable to resume normally.

The incident concerns part of the provider’s IDCF Cloud, not a confirmed outage of every SoftBank service. That distinction matters: the reported customer count describes the cloud customers in scope, rather than the number of individuals unable to access websites or a measurement of nationwide mobile-network availability.

A regional shutdown to contain the attack

In its second incident notice, IDC Frontier said the disruption began at approximately 3:40 a.m. Japan time on October 7. Its investigation identified a third-party ransomware attack affecting East Japan Region 1. The company said it had disconnected the region from the network and stopped its systems to prevent further damage and possible data leakage.

The operator listed identification and blocking of the intrusion route as ongoing. It was also checking the safety of other regions. As part of those checks, it temporarily stopped externally accessible management consoles outside the affected region, with resumption planned after safety was confirmed. That is a separate administrative-access restriction; the notice does not establish that all customer workloads in those other regions had failed.

ASCII’s original technology reporting independently identified the affected region and the early-morning start time. It also reported that the provider was contacting affected customers individually. Its initial account described unauthorized access; the operator’s subsequent notice identified ransomware as the cause.

Government websites and warehouse operations affected

The disruption became visible beyond the cloud platform itself. Kyodo News reported that websites belonging to the Ibaraki prefectural government and prefectural police had become inaccessible. It also reported a system failure at a Nissui logistics subsidiary using the cloud service, affecting shipments into and out of low-temperature warehouses handling frozen foods and other products.

By October 8, The Asahi Shimbun reported that Nissui’s logistics-system failure had halted inbound and outbound operations at 17 sites across Japan. Citing Nissui, the newspaper said approximately 1,200 business partners, including retailers, restaurants, wholesalers and food producers, were affected. Nissui said restoration was unlikely to be completed that day.

Those figures describe different layers of impact. The 495 figure is IDC Frontier’s affected cloud-customer count; the approximately 1,200 figure concerns business partners affected by Nissui’s logistics disruption. They should not be added together or treated as interchangeable measures of the outage’s size. Nor does a shipment interruption, by itself, establish that food was spoiled or that every retailer faced a shortage.

Recovery and data exposure are still open questions

The reviewed reporting does not provide a verified, platform-wide restoration time. Nissui’s recovery estimate applies to its logistics operations, not necessarily to every IDC Frontier customer. Individual websites, administrative interfaces and business systems may recover on different schedules.

Whether information was exposed also remained under investigation. The provider’s containment steps were intended to prevent leakage, but those measures are not proof that no data was accessed. The reporting likewise does not establish a confirmed attacker identity, whether a ransom was paid or a final technical account of how the intrusion occurred. This feature does not treat an unverified claim circulating online as a confirmed attribution.

Follow the service impact, not just the headline

The incident shows how one cloud-region disruption can affect both public information access and physical business operations. For readers tracking changing availability, Status Is Down’s realtime view and News archive provide complementary outage context; operator notices remain the source for this incident’s recovery announcements.

For a broader look at dependent services, read SID’s Q3 2026 outage report. Explore SID plans and create an account to follow service availability. Monitoring supports awareness of disruption; it does not replace a provider’s security investigation or guarantee restoration.

Image credit: ID 158418683 © Tero Vesalainen | Dreamstime.com

Recent Outage News and Features

Loading...

🌐 This article is available in other languages:

Français·Español·Português·中文·العربية·हिन्दी·日本語·Русский·Deutsch·Bahasa Indonesia·Türkçe·한국어·Kiswahili·Italiano·Nederlands·Polski·Tiếng Việt·Filipino·বাংলা