NTT Docomo's fifth notice on 5 November 2026 described a nationwide disruption affecting customers subscribed to its 5G SA service. The scope matters: nationwide describes the area covered by the notice, while the service description identifies which customers the operator said were affected. It does not mean every Docomo customer had lost every form of connectivity.
The update, labelled 4pm Japan time, said voice calls, mobile data and SMS could be difficult to use for the affected subscribers. It also described a possible 4G workaround. The useful response starts by reading that precise service scope and update time before changing a phone's settings or drawing conclusions about the cause.
Docomo's sixth notice at 5pm Japan time reported no change from the fifth and said restoration work continued. The detailed scope and guidance below reflect those dated updates, rather than a claim that conditions will remain unchanged after publication.
What the 4pm notice said
In its fifth incident notice, Docomo gave an approximate start time of 11.18am on 5 November and described the disruption as continuing. It said customers using Docomo-based MVNO services were unaffected, as were customers using 4G or 5G without the 5G SA subscription. It said emergency calls were unaffected.
The company said it was still investigating the cause. Its investigation to that point had not identified traces of unauthorised access or events indicating a cyberattack around the incident. That is an attributed finding at a stated stage of investigation, rather than a completed independent forensic conclusion.
These details were the operator's published position in that notice. A later update can change the position. Read the dated notice alongside the official incident list before relying on it for a decision made after this article's research time.
Why 5G SA is a narrower description than 5G
Docomo's explanation of 5G SA distinguishes standalone service from the non-standalone arrangement that combines 5G and 4G equipment. It presents SA as an option with its own device, subscription and SIM requirements. The service name therefore identifies more than a general generation of mobile technology.
The page also explains that coverage and actual radio conditions affect whether SA is used. A compatible device and an available network do not make every connection identical. The relevant combination includes the service subscribed to, the device and the connection available at the time.
For a fictional household, two people might both call their phones 5G phones while using different service configurations. One person's experience cannot automatically diagnose the other's. The incident notice's subscription wording is more informative than a broad assumption based on the phones looking similar.
Do not turn a geographic label into a customer count
A notice covering the whole country can still identify a particular service or group of subscribers. Geography and service scope are separate fields. Reading one while ignoring the other can produce an unnecessarily broad account of the event.
Imagine a fictional transport announcement that applies nationwide to one ticketing system. It would not establish that every train in the country had stopped. The same logical distinction applies here: the area stated in a notice does not erase the qualifications about the service affected.
This article does not provide a verified total of affected subscribers or a percentage of successful calls. A search-volume band is not a substitute for either figure. Nor should an individual complaint be multiplied into a national customer count without a reliable measurement and a clear definition of what was counted.
The proposed workaround was conditional
Docomo's customer guidance said selecting 4G in network settings and then restarting the phone or switching airplane mode on and off could allow voice, data and SMS service to be used. It described a possibility, not a guaranteed repair for every device or every problem.
Treat that as a limited change aimed at using an alternative available network mode. It is not a statement that the underlying SA incident has been repaired. A phone working after a change and the operator completing network restoration are different observations.
Before making the change, identify the relevant mobile line and note the existing selection so that you understand what changed. If the option is missing or the menus differ from a generic guide, consult the support information for that exact device. This article does not ask users to erase a phone, delete an eSIM or alter advanced network parameters.
What the iPhone labels mean
Apple's guide to 5G options on iPhone explains that the LTE setting uses LTE even when 5G is available. It distinguishes that from 5G Auto, which can switch to LTE automatically, and 5G On, which uses 5G when available. Additional standalone options depend on the market and provider.
Apple directs users to Mobile Data or Cellular settings and the relevant data options; dual-SIM users need to select the number they intend to change. Labels and available options should be checked against the actual device and current support instructions.
The practical point is to match the option to the intended action. Choosing an automatic mode is not the same as deliberately selecting LTE. In a fictional dual-line phone, changing the settings for the secondary number would not establish that the primary line had been changed. Identify the line before interpreting the result.
Android menus vary across devices
Google's Android internet troubleshooting guide notes that settings may appear under Network and internet or Connections, depending on the device. Its general guidance includes restarting, comparing Wi-Fi with mobile data and checking the relevant connection indicator.
For airplane mode, the guide describes turning it on, waiting ten seconds, turning it off and checking again. That is general device guidance, distinct from Docomo's incident-specific advice to choose 4G for the affected service. If problems persist, Google directs users to the mobile provider.
Do not assume a menu path from one Android manufacturer exists unchanged on another. The goal is to find the supported setting on the phone concerned. A missing label is a reason to consult the device guide, not evidence that an unrelated advanced setting should be changed instead.
Check the function you actually need
A phone is involved in several different activities: an ordinary voice call, an SMS, a web page and an app's account screen do not all answer the same test question. Start by naming the function that failed and the time it failed.
In an invented example, a user can browse a website over home Wi-Fi but cannot use mobile data when leaving the house. The successful web page establishes that a particular connection worked at home. It does not establish that the mobile connection worked outside, or that the voice and SMS functions were tested.
After a limited settings change, make a small ordinary check of the function relevant to your situation. Record the result rather than repeatedly changing several settings at once. If many things change together, it becomes harder to explain which action was followed by an improvement or what to report to support.
A Wi-Fi connection is a different observation
Google's Pixel Wi-Fi guidance suggests comparing another device on the same network to help distinguish a phone problem from an internet-connection problem. That comparison can be useful without pretending it proves the cause of a mobile-network incident.
For a fictional office, a laptop and a phone might both fail to open websites on the office Wi-Fi. That result raises a different question from a phone failing only on mobile data. Conversely, one functioning Wi-Fi network can provide a way to read the operator's notice without demonstrating that mobile service has recovered.
Keep these observations labelled. Write down whether Wi-Fi was on, which mobile line was selected and which function was attempted. Clear observations can narrow a support conversation. They cannot replace the operator's investigation into an incident affecting its wider network.
Read revised scope as new information
Docomo's 2pm third notice explicitly said its title and impact description had been updated. It identified 5G SA subscribers and specified the unaffected categories. That revision explains why a broad earlier headline should not be treated as the most precise description available later in the day.
An incident announcement is a sequence of dated statements. The first notice can establish that the operator is investigating a problem without containing every detail eventually confirmed. Later specificity should be carried forward when summarising the event.
For an invented group-chat example, someone forwards an early message saying Docomo has a nationwide problem. Another person can improve the message by linking the newer notice and retaining its service qualifications. The update should clarify what is known, rather than adding an unsupported explanation for every person's phone problem.
A possible workaround is not a restoration announcement
Three statements should remain separate: the company has identified a group affected, a user may be able to connect using another mode, and the company has declared the incident restored. They can occur at different times and require different evidence.
A successful local check supports a modest statement such as mobile data worked on this phone after the change at this time. It does not support declaring the whole nationwide incident over. Similarly, an unaffected customer's normal service does not disprove a notice covering a different subscription group.
The regional service-status page provides another official route to the operator's service information. Check the detailed service description and its time, rather than inferring an all-clear from a general heading or an older search snippet. The specific dated incident notice supplies the context needed to interpret broad status labels.
Treat the investigation's wording carefully
There is a material difference between a cause still being investigated, an indication not found so far and a final explanation that has been established. The fifth notice contains the first two types of statement. This article does not supply the third.
A fictional comparison helps: a team investigating a failed delivery might establish that its tracking system shows no weather-related interruption while continuing to examine the actual cause. That finding narrows what has been observed. It does not automatically identify a different cause.
For the same reason, a separate headline about another service should not be used to fill a gap in the mobile incident's explanation. A claim that two events share a cause requires evidence linking them. Similar timing, a shared company name or a search trend does not by itself provide that link.
Prepare a useful support description
If the relevant problem remains, a concise record can make the next conversation clearer. Note the device model, the service or line involved, approximate time and location, the function that failed and the outcome of any supported steps already tried.
In a fictional report, saying that ordinary mobile data failed at a particular time while Wi-Fi worked is more useful than saying the whole internet is broken. Mentioning that the user selected 4G and restarted once can avoid repeating an unexplained series of changes.
Keep private account details out of public posts. Share the information requested through the operator's appropriate support channel. This guide does not need a reader's credentials, one-time codes or personal account screenshots to explain the public incident notice or the general troubleshooting distinctions.
Make short-term communication plans explicit
For a household or small team relying on mobile messages, agree on a practical fallback that is already available to the people involved. That could mean checking in through an existing internet connection at an agreed time rather than assuming a message sent through one channel has been received.
An invented delivery team might tell its coordinator which contact method currently works and when it will next check for updates. The coordinator can distinguish an acknowledgement received from a message merely sent. That is a planning choice, not evidence that the operator's service has recovered.
Avoid turning a short disruption into an unnecessary purchasing decision. This article does not recommend a new subscription, device or paid service. Its purpose is to help readers understand the official scope, use supported options where appropriate and communicate the actual result of those limited steps.
Why the topic appeared in Japanese search trends
At retrieval on 5 November 2026, Google Trends' Japan Trending Now page displayed 'ドコモ 通信障害' first under the past-24-hours window, all categories and search-volume-descending sort. Its volume band was 100K+, the increase 1,000 percent and the status Active. No substitute topic was selected.
That establishes search interest during the selected window. It does not count affected subscribers, successful calls or the cause of the disruption. Those questions need the operator's technical information and, where available, independently verified evidence.
Readers can find more reporting in our Technology section. The most useful reading of this incident keeps three details attached: the precise service affected, the time of the notice and the conditional nature of the proposed workaround. Check the latest official update before relying on an earlier description.
Sources consulted 5 November 2026. This article reports dated operator statements and general manufacturer guidance, with fictional examples. It does not claim an independent network test, a completed forensic investigation, universal restoration or a guaranteed fix for an individual device.