← Wakeward

Your iPhone alarm didn’t go off

There are about a dozen real causes, and they fall into three groups: the alarm never rang, it rang and you never heard it, or it rang and something quietly turned it down. They need different fixes, so the first job is working out which group you are in.

Start here. If someone else in the house heard it, or you woke up to an alert already on the screen, your problem is in group 2. If the alarm is still sitting in the list untouched with no sign it ever fired, start with group 1.

1. It never rang

The alarm was switched off

Obvious, and still the most common. It is especially easy after editing an alarm, or after a one-off alarm has fired: a non-repeating alarm disarms itself once it has gone off, so the one that woke you on Tuesday is off on Wednesday unless you set repeat days.

It was set for the wrong days

Repeats set to weekdays when the morning you needed was a Saturday, or repeats set to a single day months ago. Check the repeat line, not just the time.

AM instead of PM

Still the single most common wrong-time mistake on a 12-hour clock, and it is invisible when you are half asleep. Switching to a 24-hour clock removes the failure mode entirely: Settings › General › Date & Time › 24-Hour Time.

The device was off, or the battery died

An iPhone that is powered down does not ring, and neither does one that hit 0% at 4am. Low Power Mode is not the culprit here — iOS does not suppress alarms to save battery — but a phone at 8% and unplugged at midnight is a real risk that nothing on screen will warn you about.

You changed time zone

An alarm keeps its clock time, so a 7:00 alarm is still 7:00 where you are now, not 7:00 where you set it. That is almost always what you want, and occasionally not what you assumed after a flight.

The alarm came from a hidden or locked app

Apple states plainly that alarms scheduled by apps that are hidden, or locked behind Face ID, silently fail. There is no error and no warning, and no app can detect this about itself — it is genuinely down to you to know.

The app was only ever sending notifications

Until iOS 26, no third-party app could schedule a real system alarm. Anything built the old way delivers a notification instead — and a notification obeys the Ring/Silent switch, the notification volume, every Focus, and Scheduled Summary. iOS 26 introduced AlarmKit, the first framework that gives an app the same alerting path as the built-in Clock. If your alarm app predates it, that alone explains a lot of silent mornings.

2. It rang and you didn’t hear it

The ringer volume was down

Alarms play at the ringer volume, which is a separate slider from media volume. Open Settings › Sounds & Haptics (it is called Settings › Sounds on iPad) and drag the Ringtone and Alerts slider: iOS plays a sample at the exact volume your alarm will use. That sample is the only honest readout there is.

“Change with Buttons” turned it down for you

It lives in that same screen. With it on, the physical volume buttons move the ringer volume whenever nothing is playing — which is most of your day. A press in a pocket at lunchtime quietly sets the volume of tomorrow morning’s alarm. More on this and the other setting that moves it.

Attention Aware Features lowered it

On iPhones with Face ID, iOS checks whether you are looking at the screen before it lowers the volume of some alerts. Half-waking, glancing at the phone and dropping back to sleep is exactly the shape of this failure, and it is invisible: no app can detect it, prevent it, or work around it. Settings › Face ID & Passcode › Attention Aware Features.

Vibration is switched off device-wide

Accessibility › Touch › Vibration switches off every vibration on the device, including an alarm’s. If your ringer is low, vibration was the whole alarm. No app can read that switch or override it.

The sound went somewhere else

Headphones or a Bluetooth speaker still connected from the night before are worth ruling out before you blame the alarm. So is a phone face-down in soft bedding, which is the easiest of all of these to fix.

Two alarms landed on the same minute

If two apps have an alarm set for the same minute, iOS picks between them unpredictably, and one press of a physical button dismisses every alarm currently alerting. Stagger them by a few minutes instead — a later ring has nothing to compete with.

3. Sometimes it genuinely isn’t you

iOS has shipped silent-alarm bugs in more than one year, and there is an open, unresolved report of alarms firing five to forty-five minutes late when they were scheduled a long way ahead — which describes every wake-up alarm. Two things follow. Re-test after every iOS update, because both settings and behavior move across updates. And do not put anything that actually matters on a single alarm.

What is not the cause

These come up constantly and none of them stop a system alarm.

SuspectReality
Force-quitting the alarm appDoes not stop it. iOS holds system alarms itself, not the app.
Restarting your iPhoneDoes not stop them. iOS re-arms them after a reboot.
Silent mode / the Ring–Silent switchDoes not silence a system alarm.
A Focus, including Sleep and Do Not DisturbDoes not silence one either. Apple’s own answer to whether any Focus can block an AlarmKit alarm is simply “no”.
Low Power ModeDoes not suppress alarms.
Media volumeA different slider from the ringer volume an alarm uses.

What to actually do tonight

  1. Check the alarm is switched on and set for the right day, and check AM/PM.
  2. Set the ringer where you want it, and confirm it with the slider sample rather than by eye.
  3. Turn Change with Buttons off so nothing can move it before morning.
  4. On a Face ID iPhone, turn Attention Aware Features off.
  5. Plug the device in.
  6. Run a real two-minute test from where the device actually sleeps.
  7. Add a second alarm a few minutes later, because every item above can still be defeated by one bad night.