Skip to main content
NestGrid logoNestGrid

Verizon SOS Mode and Smart Devices Offline Share One Fix

Phone shows SOS while smart home devices go offline during a Verizon outage.

Last updated

Phone showing SOS beside offline smart home devices during a shared network outage

Verified August 25, 2026. Status: Workaround for Verizon SOS/outage scenarios where smart home devices go offline, not a carrier-confirmed repair procedure for every Verizon gateway, router, or hub firmware.

When a Verizon phone drops into SOS or “Emergency calls only” at the same time the lights, plugs, cameras, or hub all go offline, start by treating it as one layered failure. The phone is not in a special mode you need to turn off. Apple says SOS or SOS only means the iPhone is not connected to its cellular network, although emergency calls may still be possible through other carriers’ networks where supported. [1]

That matters because the smart home may be failing for the same reason, especially if the house uses Verizon Home Internet as its WAN path. Verizon describes a wireless outage as an unexpected disruption affecting many cell sites at once, and its outage FAQ says an event can cause loss of service for mobile or Verizon Home Internet users in the affected area. [2] If the cloud path is gone, Alexa, Google Home, Apple Home, camera apps, and manufacturer apps can all report devices as offline even if the bulbs and plugs inside the house still have power.

StatusWhat it means during this problemWhat to do first
ConfirmedSOS or SOS only is a cellular-network connection state, not a toggle.Stop hunting for an SOS switch and confirm whether Verizon service is down.
WorkaroundWi-Fi Calling can help only if you have another working internet path.Use it for calls and texts while waiting for Verizon service to return.
InvestigatingSmart devices offline at the same time strongly suggests a shared network dependency, but a local router, hub, SSID, or device problem can still remain after the outage clears.Recover in order: gateway, router, hub, then individual devices.

Do not reset the smart plugs while the carrier network is still down

The first job is not to make every device blink. It is to decide whether the house still has an internet exit. If the Verizon phone says SOS and the Verizon Home Internet gateway is also down or unstable, factory-resetting bulbs and plugs only creates more cleanup later. Those devices may be faithfully reporting the obvious: they cannot reach the services that make the app look alive.

Use Verizon’s own outage tools, the My Verizon app, and Network Notifications where available before you start blaming the hub. Verizon also recommends using Wi-Fi and Wi-Fi Calling during an outage when an alternate internet connection exists. [2][3] That last clause is the whole catch. Wi-Fi Calling does not help if the only Wi-Fi in the house is riding on the same failed Verizon Home Internet connection.

User-report sites are useful smoke, not the fire marshal’s report. A spike on Downdetector can corroborate that many people are seeing trouble, but it is still user-reported signal rather than official confirmation.

If you want the narrower local-vs-carrier split, keep this separate from the full recovery sequence here: Verizon outage or your gear is the cleaner diagnostic path for checking whether the failure belongs to Verizon or to your own equipment.

The January 14, 2026 Verizon outage is the model case

The reason to anchor this in a dated outage is simple: a real Verizon event showed why the phone symptom and the smart-home symptom should be handled together. During the January 14, 2026 outage, TechRadar’s live coverage described Verizon’s explanation as a software issue, tracked the disruption from about 12:30 PM ET to a 10:24 PM ET resolution update, reported Verizon’s advice to restart devices that still had not reconnected after restoration, and noted a $20 credit. [4]

MacRumors also reported that affected iPhones were showing SOS during that outage and later marked the story resolved. [5] The user-report peak should be handled carefully: TechRadar cited roughly 182,000 Downdetector reports, while Mashable cited roughly 178,000 reports around 12:45 PM ET. [4][6] Those are not interchangeable official measurements of Verizon’s network. They are separate user-report figures from separate coverage.

That case also shows the practical order of operations. While the outage was live, no Airplane Mode trick could repair Verizon’s side of the network. After restoration, a restart became reasonable because the carrier had said service was back and some devices still needed to re-register cleanly.

While Verizon is still down: confirm, preserve control, avoid damage

During a live carrier outage, the useful work is boring but protective. Check whether Verizon acknowledges an outage for your area, look for Network Notifications in My Verizon if you can reach them, and test whether the home has any non-Verizon internet path. A neighbor’s cable internet, a second carrier hotspot, or office Wi-Fi can make Wi-Fi Calling useful. The same setting is not useful through a Verizon gateway that has no upstream service.

  • If the phone says SOS and Verizon confirms an outage: wait for restoration, use Wi-Fi Calling only through a working non-Verizon internet path, and do not reset smart-home devices.
  • If the phone says SOS but Verizon does not confirm anything: check another Verizon phone nearby, your gateway status lights, and Verizon’s outage tools before assuming the whole network is down.
  • If the phone has Verizon service but the smart home is offline: treat it as a home-network or hub problem instead of an SOS-related outage.
  • If the home internet is working through another provider: enable or use Wi-Fi Calling, then leave the smart-home stack alone unless the devices remain offline after Verizon service returns.

Downdetector can still be worth checking because it collects user-submitted problem reports for Verizon, but it should stay in the “corroborating context” bucket. [7] A large report spike can explain why your phone, gateway, and neighbors all look broken at once; it does not replace a Verizon status notice or direct device checks at your house.

Phone-side steps are for restoration, not for a live outage

Once Verizon service is reportedly restored, then the familiar phone steps make sense. CNET and NorthJersey/USA TODAY describe the usual sequence: turn Airplane Mode on for about 15 seconds and turn it off, restart the phone, toggle the cellular line off and back on, check for a carrier settings update, and use Reset Network Settings only as a last resort. [8][9]

That sequence forces the phone to try a clean registration with the network. It does not force Verizon’s network to come back before Verizon has fixed it. If SOS returns immediately during a confirmed outage, stop there and save the deeper resets for after restoration.

Why the apps still say every device is offline after internet returns

A smart home can look worse after the carrier outage clears because the stack did not come back in a clean order. Cloud-dependent control depends on the app, the manufacturer cloud, the home internet connection, the router, and sometimes a local hub all being available. T3’s internet-outage explainer describes the basic problem: when the internet goes down, cloud-based smart-home features and remote app control can stop working even though some local functions may continue. [10]

The annoying version is the hub that booted too early. It sees no internet, decides it is offline, and keeps making downstream devices look unavailable even after the gateway and router are fine. A SmartThings community thread documents that exact kind of post-outage behavior, where a hub stayed offline after an internet outage and required a reboot. [11] That is not proof every hub behaves the same way, but it is a familiar failure pattern.

Diagram showing recovery order from gateway to router to smart home hub to devices

Bring the house back from the bottom up

After Verizon service is back, recover the stack in dependency order. The gateway or modem gets first claim because nothing above it can prove much until the WAN path is alive. The router comes next because Wi-Fi clients need a stable LAN and internet route. The smart-home hub comes after that because it needs both the LAN and, for many ecosystems, cloud access. Individual bulbs, plugs, locks, sensors, and cameras come last.

SmartHomeSensei documents a recommended post-outage sequence: power off the modem or gateway, router, and hub together; bring the modem or gateway up first until it has a solid online light; then bring up the router; then bring up the hub last, allowing a few minutes for connection. [12] Treat that as a documented recovery process, not as Verizon’s universal law for every home.

  1. Check that Verizon service has actually returned. Do not start the smart-home recovery while the gateway is still searching or the phone is still stuck in SOS during a known carrier event.
  2. Power-cycle the Verizon gateway or modem first. Wait for the normal online state, not merely for power.
  3. Restart the router after the gateway is online. Confirm a normal Wi-Fi connection and ordinary web access from a laptop or phone.
  4. Restart the smart-home hub only after the router is stable. Give the hub time to reconnect before judging the devices above it.
  5. Open Alexa, Google Home, Apple Home, SmartThings, or the manufacturer app and refresh status. If a whole room or protocol group is back, leave it alone.
  6. Power-cycle only the devices that remain offline. Do not factory reset unless pairing is truly lost or the vendor app requires it.

If only Wi-Fi devices remain offline after the router came back, check for a changed SSID, password, band steering behavior, or channel change before re-pairing everything. If Zigbee, Z-Wave, or Thread devices are the holdouts, the hub or border-router layer is the more likely place to look. For the protocol-by-protocol version, use the smart home outage behavior map or the staged smart home reconnect after power outage guide.

Use one decision tree, not two separate mysteries

What you see nowMost likely layerNext move
Phone still says SOS and Verizon outage is still activeCarrier networkWait, use Wi-Fi Calling only over a working alternate internet path, and leave the smart-home devices paired as they are.
Verizon says service is restored but phone still says SOSPhone re-registrationUse Airplane Mode for about 15 seconds, restart, toggle the cellular line, check carrier settings, then consider Reset Network Settings as a last resort.
Phone service is back but Verizon Home Internet is notGateway, modem, ONT, or Verizon Home Internet serviceRecover the Verizon gateway or modem first before touching the router, hub, or devices.
Internet is back but every smart device still says offlineRouter or hub layerRestart router after the gateway is stable, then restart the hub.
Only a few devices remain offlineIndividual device, protocol, or Wi-Fi credential issuePower-cycle those devices and check SSID, hub, or protocol-specific recovery before factory reset.

There is no SOS mode on a Verizon 5G Home Internet gateway. SOS is the phone’s status indicator. The connection between SOS and offline smart devices is the shared dependency: one Verizon network event can break cellular service and the home internet path, and the smart-home cloud path fails above that. Once service returns, the same dependency chain gives you the recovery order: cellular re-registration where needed, then gateway, router, hub, and devices.

References

  1. If you see SOS, No Service, or Searching on your iPhone or iPad, Apple Support, June 23, 2026
  2. Wireless Outages and Network Notifications FAQs, Verizon
  3. Wi-Fi Calling FAQs, Verizon
  4. Verizon outage January 2026, TechRadar
  5. Verizon is Down, iPhone SOS [Resolved], MacRumors
  6. Verizon outage worst, Mashable
  7. Verizon outage map, Downdetector
  8. iPhone Stuck in SOS Mode?, CNET
  9. Why is Verizon phone stuck in SOS? How to text, call, fix, turn off SOS mode during Verizon outage, NorthJersey.com
  10. What happens to your smart home when the internet goes down, T3
  11. Hub stays offline after internet outage, requires reboot - AT&T U-verse, SmartThings Community
  12. Smart Device Offline After Power Outage Fix, SmartHomeSensei

Corroborating context

For protocol background on why this failure happens, see Compatibility & Protocols.

Not currently linked to a known regression. Background on the underlying protocol lives in Compatibility & Protocols.

Other fixes for this device

Report / Feedback

If this fix didn't hold on your exact hardware/firmware combination, file a scoped report -- it feeds the re-verification queue instead of an open comment thread.

Blogarama - Blog Directory