Why your phone alarm didn't go off
Short answer: it almost always did go off, and one of eleven specific things stopped you hearing it or stopped it firing. Work through the list below before concluding you slept through it — roughly half the time it's a settings problem with a permanent fix.
1. It went off and you dismissed it
The most common cause, and the least believed. Motor control returns before memory formation does, so you can reach out and silence an alarm while functionally still asleep, and form no memory of it. If your alarm was off rather than snoozed when you woke, this is the likeliest explanation. There's a fuller account in turning off your alarm in your sleep.
Check: most phones log alarm history, and your screen-on time will often show activity at the alarm time.
2. Bluetooth routed the sound elsewhere
If your phone stayed paired to headphones, a speaker or a car overnight, the alarm may have played through that device at whatever volume it was set to. Sleep earbuds are a frequent culprit — the alarm plays into an earbud that fell out hours ago.
Fix: turn Bluetooth off at night, or check what your phone considers the active output before bed.
3. A Focus or Do Not Disturb mode with the wrong exceptions
Standard alarms usually survive Do Not Disturb. Third-party alarm apps, calendar reminders and timed notifications frequently don't. If you rely on anything other than the built-in clock app, verify it's allowed through.
4. Media volume vs alarm volume are separate
On Android especially, ringer, media, notification and alarm volumes are independent sliders. Turning media volume to zero for a video the night before doesn't touch the alarm — but on some manufacturer skins it does, or the two are linked in ways that aren't obvious.
Fix: find the alarm volume slider specifically and set it deliberately.
5. Battery saver killed the app
Aggressive power management on some Android phones suspends background apps overnight, including third-party alarms. This is a known and widely-documented problem, and it varies by manufacturer.
Fix: exclude your alarm app from battery optimisation, or use the built-in clock, which is normally exempt.
6. The phone was off, or died
An alarm on a powered-off phone does not fire on most devices. Nor does one on a phone that hit 0% at 4am. If you charge overnight, check the cable is actually seated and the plug is switched on — a loose cable is a silent failure.
7. AM/PM
Unglamorous and extremely common. 7:00 PM instead of 7:00 AM. If you use a 12-hour clock, this will get you eventually. Switching your phone to 24-hour time removes the entire category of error.
8. It was set for the wrong days
Repeat alarms set for weekdays don't fire on a bank holiday you're working, and one-off alarms don't repeat. Check whether the alarm shows specific days or "once".
9. Time zone changed under you
Travel is the obvious case, and there's a fuller treatment in waking up on time in a new time zone. Less obvious: a phone that auto-detects time zone can pick up a neighbouring one near a border, or fail to update after a flight until it gets signal. Daylight saving transitions catch people the same way, particularly with third-party apps.
10. A software update rebooted the phone
Overnight updates restart the device, and some alarm apps don't re-register their schedule until opened. Built-in clock apps generally survive this; third-party ones sometimes don't.
11. You genuinely slept through it
Once the first ten are eliminated, this is what's left — and it's a real thing rather than a character failure. It usually means one of two causes: habituation, where your brain has learned to filter a sound it's heard hundreds of times and stopped treating it as significant, or sleep debt, where being consistently short of sleep raises the threshold needed to wake you. Why loud alarms stop working covers the first; how much sleep you actually need covers the second.
A five-minute audit
- Switch the phone to 24-hour time
- Set alarms in the built-in clock app, not a third-party one
- Exempt the clock app from battery optimisation
- Turn Bluetooth off at bedtime, or confirm the output device
- Set alarm volume explicitly, separately from media
- Turn off automatic time zone if you're not travelling
- Check the repeat days actually match your week
That eliminates causes 2 through 10 permanently. What's left is 1 and 11 — and those are the two a settings change can't fix.
If it's 1 or 11
Both come down to the same thing: sound has stopped being a reliable way to wake you, either because you can silence it while asleep or because you've tuned it out.
Moving the phone across the room addresses the first, at the cost of waking everyone else. Changing sensory channel addresses both — a wake-up delivered through touch carries no years of learned indifference, and can't be dismissed by a hand that hasn't properly woken up. That's what Silent Wake is: a wrist-worn vibration alarm, no sound, worn rather than placed.
If your problem turned out to be a Bluetooth setting, though, just fix the Bluetooth setting.
Related reading
- Why You Turn Off Your Alarm in Your Sleep
- Why Loud Alarms Do Not Work for Heavy Sleepers
- How to Wake Up on Time in a New Time Zone
- Can You Use an Apple Watch or Fitbit as a Silent Alarm?
Behaviour varies by phone model and OS version. Where a setting name differs on your device, the underlying principle is usually the same.