A network outage began at NTT Docomo shortly after 10:30 a.m. on the 11th, leaving voice calls and data communications on mobile phones hard to connect. As of shortly before 3 p.m. the outage was still continuing. The company is investigating the cause, but so far it has not been confirmed to be the result of unauthorized access. The extent of the impact is not consistent across accounts: some say voice calls and data communications are hard to connect nationwide, some describe a failure of 5G services, and some say it is limited to some users. Docomo also caused a communications outage in its 5G services on the 5th of this month. That failure began at around 11:18 a.m. and was fully restored at around 1:20 a.m. the next day, the 6th. Docomo explains the cause on the 5th as congestion at switching equipment housing 5G SA subscribers.
Mobile phones are the everyday foundation for calls, contact, payments and even work exchanges. When an outage occurs, it affects not only the users themselves but also the services that use those lines. Because two outages followed in a short period, whether the cause is the same or different becomes a point to check in preventing a recurrence.
Docomo subscribers will want to check the state of restoration in the outage notices Docomo issues. To prepare for times when calls will not connect, having several ways to get in touch, such as calling over Wi-Fi and messaging apps, helps you avoid panic.
Some reports say this too is a failure of 5G services, and there is a view that is concerned about a link to the failure on the 5th. If it happened again on the same equipment, the question is whether the measures after the 5th were sufficient.
On the other hand, there is also an account that voice calls and data communications are hard to connect nationwide, so it may be a wide failure not limited to 5G. Because the cause is not necessarily the same, there is also a view that we should wait for the company’s findings.
What we could confirm is that the failure began shortly after 10:30 a.m. on the 11th and was still continuing shortly before 3 p.m., and that unauthorized access has not been confirmed so far. We could not confirm the cause, the extent of the impact, the number of users or the time of restoration. The relationship to the failure on the 5th is not known either. We want to see the cause and time of restoration that Docomo presents.
NHK (NTT Docomo outage continues; no unauthorized access confirmed, 11/11) · Asahi Shimbun (Docomo hit by 5G service outage again, following the 5th of this month, 11/11) · TBS NEWS DIG (NTT Docomo outage nationwide; voice calls and data communications hard to connect, 11/11) · ITmedia (Docomo outage restored; cause was congestion at switching equipment housing 5G SA subscribers, 11/6)
Outage at NTT Docomo Since Shortly After 10:30 a.m. on the 11th; No Unauthorized Access Confirmed
Voice calls and data communications became hard to connect, and the company is investigating the cause. There was also a failure in its 5G services on the 5th of this month.
A network outage began at NTT Docomo shortly after 10:30 a.m. on the 11th, leaving voice calls and data communications on mobile phones hard to connect. As of shortly before 3 p.m. the outage was still continuing, and the company is investigating the cause. So far it has not been confirmed to be the result of unauthorized access. Accounts of the extent of the impact differ: some say voice calls and data communications are hard to connect nationwide, some describe a failure of 5G services, and some say it is limited to some users. Docomo also caused a communications outage in its 5G services on the 5th of this month.
The failure on the 5th began at around 11:18 a.m. and was fully restored at around 1:20 a.m. the next day, the 6th. Docomo explained the cause as “congestion” at switching equipment housing 5G SA subscribers. Congestion means that requests for communication concentrate on particular equipment, like a traffic jam on a road, and cannot all be processed. Whether the cause this time is the same as on the 5th is not yet known. The number of users affected and the outlook for restoration have not been confirmed either.