No Earthquake Alert Arrived on a Phone in California, Oregon, or Washington

A phone that stayed silent through an earthquake is not one fault. It is three, because a ShakeAlert message reaches a handset over three routes that share nothing but the source. Wireless Emergency Alerts ride the carrier network. The earthquake feature built into Android and iOS rides Wi-Fi or mobile data. The MyShake app rides its own notifications. Each has a separate switch, each has its own alerting threshold, and one of them being on says nothing about the other two.

Before any of that matters, one boundary decides whether the question is answerable at all. ShakeAlert is a United States Geological Survey system, and it operates in California, Oregon and Washington — the ShakeAlert program describes it as serving over 50 million residents and visitors across those three states. Outside them there is no ShakeAlert message to miss, and a silent phone during shaking in another state means something different. That case is covered further down.

The three switches, in the order worth checking

USGS lists exactly three ways to receive ShakeAlert-powered alerts on a phone, and the agency adds one clarification worth having in front of you before searching an app store: “There is no app called ‘ShakeAlert’ to download.” Anything sold or listed under that name is not the system.

1. Wireless Emergency Alerts

WEA is the FEMA-coordinated channel that also carries weather warnings and AMBER alerts. The FCC describes it as delivering “geographically-targeted, text-like messages” to compatible mobile devices, and the mechanism matters here: WEA uses cell broadcast rather than SMS, so an alert is aimed at an area rather than at a phone number, and no one needs the number to reach the handset. The FCC notes the system became operational in 2012 and has since delivered more than 40,000 alerts, and that a new or high-end phone is not required to receive them.

The switch lives in different places on the two platforms:

• iPhone — Apple’s instruction is to open Settings › Notifications and look at the bottom of the screen for Government Alerts.
• Android — Google’s steps are: open the Settings app, tap Notifications › Wireless emergency alerts, then choose how often alerts arrive and which categories are on.

Two limits on this route are documented rather than inferred. Apple states plainly that “some government alerts can’t be turned off,” which is why a list of toggles may look shorter than expected, and the FCC notes that presidential alerts cannot be blocked. Everything else in that list is a category a previous owner, a carrier setup screen, or a stray tap could have switched off months ago without any visible consequence until the day it mattered.

2. The earthquake feature built into the phone

This is the route most often missing, because it is a separate feature that happens to be about the same hazard.

On Android, Google’s support instructions give the path as: open the Settings app, tap Safety & emergency › Earthquake alerts, then turn Earthquake alerts on or off. Where that entry is not present, Google lists an alternative location at Settings › Location › Advanced › Earthquake alerts. Google also states a hard requirement for this route: “To get alerts, you must have Wi-Fi or data turned on.” A phone with mobile data disabled and no Wi-Fi in range can still take a WEA over the carrier network, but this feature has nothing to travel on.

On iPhone, the equivalent is newer and narrower. Apple documents Enhanced Safety Alerts as requiring iOS 26.2 or later and being “available in the United States and Taiwan.” Apple’s steps read: open Settings and tap Notifications, scroll to the bottom of the screen, under Enhanced Alerts tap Enhanced Safety Alerts, then tap Earthquake Alerts, Imminent Threat Alerts or Improve Alert Delivery to turn it on or off. Apple states that Earthquake Alerts and Imminent Threat Alerts are on by default while Improve Alert Delivery is off by default, and that these alerts “are sent over Wi-Fi and cellular data when available” — the same dependency Android has.

Apple splits its earthquake notifications into two levels. An Awareness Alert “notifies you when an earthquake is detected nearby and that you should prepare to take action if necessary.” An Action Alert is “labeled as critical” and fires when you are in an area where strong shaking is expected. Both carry an estimated magnitude and your proximity to the quake.

If the iPhone in question is on an earlier release than iOS 26.2, this second route simply does not exist on it. That is not a settings problem, and no amount of toggling will produce the menu.

3. MyShake

USGS names MyShake as the app option, available from the App Store and Google Play. It is an ordinary installed app, which means it needs the usual permissions granted at first run — location and notifications — and it will not deliver anything if those were declined or later revoked in the app’s own settings page.

A silent phone is often a phone below the threshold

The assumption behind most missed-alert complaints is that any felt earthquake should produce one. The published rules say otherwise. The ShakeAlert program states that end users in the three states receive alerts “only if certain thresholds for magnitude and shaking intensity are met” — two conditions, not one. A quake can clear the magnitude bar and still produce shaking too weak at a given address to cross the intensity bar.

The clearest published numbers belong to the Android route. Google states that an Android phone “sends you alerts about nearby earthquakes of magnitude 4.5 and above” using approximate location, and describes three tiers above that gate:

• Be Aware — light shaking, intensity MMI 3 to 4, delivered as a normal notification that respects the phone’s existing settings.
• Be Ready — noticeable shaking, intensity MMI 4, which Google describes as able to override Do Not Disturb.
• Take Action — moderate to extreme shaking, intensity MMI 5 and above, which makes a sound and lights the screen.

MMI is the Modified Mercalli Intensity scale, and the distinction it draws is the one that resolves most of these cases. Magnitude is a single number for the whole earthquake. Intensity is local, and it falls off with distance and varies with ground conditions. Two people the same distance apart from the same quake can sit on different sides of an intensity threshold.

One thing deliberately not stated here: the exact magnitude and intensity figures that trigger a Wireless Emergency Alert for ShakeAlert. The ShakeAlert program publishes an alert delivery thresholds page, but it presents the figures as a chart image rather than as text, and it carries an explicit warning that “not all Technical Partner delivery methods have the same alerting thresholds and may not all activate for a given earthquake.” Since those per-route numbers could not be read directly from the official page, no figure is quoted for them. The practical consequence is the part that matters anyway: a quake can trip the phone’s built-in feature and not trip WEA, or the reverse, and neither outcome is a malfunction.

The alert that arrives during the shaking

The second common report is not silence but lateness — a notification that lands while the room is already moving, or a few seconds after it stops. This is the system working as described, and USGS says so directly. In its account of earthquake early warning, the agency notes that the approach works best away from the epicenter and that warnings arrive too late for the area where the earthquake originates.

The physics is unforgiving and worth stating once. An early warning system does not predict earthquakes. It detects one that has already started, at sensors near the fault, and races a message ahead of the shaking. Google’s description of the West Coast arrangement puts the ShakeAlert sensor network at 1,675 seismic sensors feeding that detection. The message travels at network speed and the shaking travels at seismic speed, so the further away you are, the larger the gap — and directly above the rupture the gap is zero or negative.

USGS frames the payoff in seconds, not minutes: enough to drop, cover and hold on, enough for a train to begin slowing, enough for an elevator to reach a floor and open its doors. What no official page publishes is a lead time for a specific address. Any source offering one is not quoting USGS.

What each route needs before it can reach the screen

Once the switches are confirmed on, these are the documented dependencies, each tied to a specific route:

• WEA needs the carrier network and the targeted area. It is broadcast to a geographic zone, so a phone outside the zone gets nothing regardless of settings, and a phone with no cellular service has no channel to receive it on.
• The Android feature needs connectivity. Google’s requirement is explicit: Wi-Fi or data turned on.
• The iPhone feature needs iOS 26.2 or later. Apple also states these alerts travel over Wi-Fi and cellular data when available.
• The Android feature needs a supported country. Google notes alerts are only received “in supported countries,” and states separately that “earthquake alerts aren’t supported in all areas.”
• Every route tolerates misses by design. Google’s own caveat is unusually blunt: “You might not get alerts for all earthquakes in your area… Occasionally, you may get an alert but not feel an earthquake in your location.” It adds that not all earthquakes can be detected and that magnitude and shaking intensity estimates may have errors.

That last point cuts both ways, and it is the reason the protective advice does not depend on the phone at all. USGS puts it as a single instruction: on feeling shaking or receiving an alert, drop, cover and hold on. The alert is a bonus, not the trigger.

Outside California, Oregon and Washington

A phone in Nevada, Utah, Alaska, Hawaii, Missouri or South Carolina is not covered by ShakeAlert, and no setting changes that. What it may still have is the second route in a different form. Google describes the Android Earthquake Alerts System as operating in more than 100 countries by crowdsourcing detection: participating phones act as small sensors, and when enough of them register a pattern consistent with shaking, Google’s servers confirm the event and estimate the affected area. On the US West Coast that same feature is fed by ShakeAlert instead, per Google’s description of the partnership.

So on an Android phone outside the three states, the Settings › Safety & emergency › Earthquake alerts switch is still the one to check. On an iPhone, Apple’s Enhanced Safety Alerts are documented as available in the United States generally rather than in specific states, so the iOS 26.2 requirement is the binding constraint rather than geography within the country.

The order that answers the question fastest

1. Establish whether ShakeAlert covers the location at all. Three states, no exceptions, no setting that extends it.
2. Open the government or emergency alerts list first — Settings › Notifications › Government Alerts on iPhone, Settings › Notifications › Wireless emergency alerts on Android — and confirm the categories are on rather than assuming they are.
3. Check the separate earthquake feature at Settings › Safety & emergency › Earthquake alerts on Android, or Settings › Notifications › Enhanced Alerts › Enhanced Safety Alerts on iOS 26.2 or later. This is the switch most often found off, because nothing else on the phone points to it.
4. Confirm the connectivity the built-in route requires. Wi-Fi or mobile data on, not merely a working carrier signal.
5. Compare the earthquake against the published gate before treating anything as broken. Below magnitude 4.5, the Android route is documented not to alert at all.
6. Ask where the phone was relative to the epicenter. An alert during or after shaking near the source is expected behaviour, not a fault.
7. Install MyShake as an independent third route if the first two have been confirmed and more coverage is wanted. It fails separately from the other two, which is the point of having it.

When This Doesn’t Apply

This diagnosis assumes a specific case: a phone that produced no earthquake alert, in a place and at a magnitude where one was plausible. Several conditions take it off the table entirely.

• The earthquake was outside the three ShakeAlert states. Then the question is not about ShakeAlert delivery. On Android it becomes a question about the crowdsourced Android Earthquake Alerts System; on iPhone, about whether the device is on iOS 26.2 or later.
• The quake was below magnitude 4.5. For the Android route this is settled: Google documents the feature as alerting on nearby earthquakes of magnitude 4.5 and above. Nothing was missed.
• Shaking was felt but intensity stayed low. The magnitude gate and the intensity gate are separate, and a distant moderate quake can be felt without reaching the intensity level any route requires. A felt tremor is not evidence that a threshold was crossed.
• The alert arrived, just too late to act on. That belongs to the physics of the method, not to the settings. USGS states the warning is too late for the area where the quake originates.
• The phone was off, out of service, or in airplane mode. WEA needs a live carrier connection to the targeted area, and the built-in features need Wi-Fi or data. None of the three routes has a way to deliver into a device with no network at all.
• A specific number is wanted for a specific address. How many seconds of warning a given location will get, and the exact magnitude and intensity figures behind each individual delivery method, are not published as plain text on the official pages. Estimates found elsewhere are not agency figures, and this article does not repeat them.
• The goal is prediction. Nothing described here forecasts an earthquake before it starts. Every route in this article is triggered by a quake that is already underway.

The underlying shape of the problem is simple enough to hold onto: three independent routes, two separate thresholds, and one hard physical limit near the epicenter. Most silent phones turn out to be a switch nobody knew existed. Most late alerts turn out to be the system doing exactly what it was built to do.