iPhone Alarm Didn't Go Off: Causes and Fixes

Why did my iPhone alarm not go off?

Most of the time it's one of three things: the alarm's sound setting is wrong, audio got routed to a disconnected Bluetooth device, or iOS itself has a known bug. By Apple's own design, Silent mode and Do Not Disturb (or another Focus) are not supposed to affect whether the alarm rings — so if it stayed quiet, something else broke that guarantee.

The most common culprit reported across iOS versions is Attention-Aware Features on Face ID phones. With Face ID, Attention Aware Features can reduce the alarm volume once the phone detects you looking, making it seem like the alarm didn't ring. Turning it off (Settings → Face ID & Attention → Attention Aware Features) has fixed it for many users, including on iPhone 13 Pro Max, where it was fixed after turning off Attention-Aware Features.

Audio routing is the second most common cause. If headphones or a car speaker were paired overnight, one user found the fix was to raise ringer volume via side buttons each time disconnecting from bluetooth devices, such as a car, because the alarm kept playing to a device that was no longer nearby. For a broader rundown of what actually keeps alarms quiet even when Silent mode is off, see the guide on making an alarm ring on a silent iPhone.

Why does my iPhone alarm ring silently?

A silent alarm usually means the alarm fired correctly but the sound never reached the speaker. The bug causes alarms to go off, but silently—there's no audible ring, and no vibration. It shows on the lock screen exactly as expected, which is why people are so confused — the system thinks it worked.

This isn't new. Apple confirmed the pattern back in 2024: after many users complained about their alarms ringing silently on iPhones, Apple told TechCrunch that it is aware of the issue and is working on a fix. Since then it has resurfaced repeatedly. One report from late 2025 put it plainly: "For those who have the latest iPhone, my alarm does not ring." AppleInsider staff noted Apple still hasn't acknowledged this problem, even though it seems that many iPhone users have had this issue, and many of them have had the issue multiple times.

A less obvious trigger is the haptic pattern itself. On some builds, using the default haptics on your alarm might cause it to randomly stay silent after it goes off, and changing it could fix this issue. Swap the Haptics setting for the alarm from Synchronized to anything else and retest.

Is this an iOS bug, or something I set wrong?

It can be either, and the two causes look identical from the outside. As one technical breakdown put it, by Apple's design, alarms set in the Clock app will ring regardless of Focus mode, Do Not Disturb, or the Ring/Silent switch — so "I had Focus mode on, so my alarm didn't ring" is not supposed to happen. If it didn't ring anyway, the cause is almost always a misconfiguration, an audio routing issue, or an iOS software bug.

The bug history is well documented across major releases. Apple's alarm system has shipped with confirmed bugs across multiple iOS versions: iOS 17.x — alarms went off silently or didn't fire at all, patched in iOS 17.2.1. The pattern continued into iOS 26. Apple's own developer forums logged a fresh case where users currently on iOS 26.1 may experience alarms failing to ring after updating their system, which can cause real-life disruptions (e.g., being late for work), filed against AlarmKit — the same system framework the Clock app itself relies on, explained in more detail in what AlarmKit is and why it matters.

Sleep-related settings add a third layer of confusion. If you've enabled a "sleep" mode, make sure Alarms is one of the apps that's allowed to notify you during the sleep hours — a Focus misconfiguration, not a bug, but one that produces the exact same missed wake-up. Check how Focus profiles interact with alerts in general on the Focus mode and calendar alerts guide.

How do I fix an alarm that keeps failing?

Start with the settings Apple itself points to, then move to the harder resets. Apple's official troubleshooting for a quiet or silent alarm says to check the basics first: if you have an alarm that doesn't sound or is too quiet, or if your iPhone only vibrates, set the volume on your iPhone, and make sure your alarm sound isn't set to None by opening the Clock app, tapping Alarms, then Edit, tapping the alarm, then Sound, and choosing a Sound. Also confirm Change with Buttons is off, since the option to change ringer and alerts volume with the side buttons, found in Settings → Sounds & Haptics, should be turned off to stop an accidental button press from muting the alarm mid-sleep.

If settings check out, delete and rebuild the alarm rather than editing it. If a specific alarm isn't ringing, try deleting it and creating it again. Corrupted alarm entries are a known cause after iOS updates: this issue seems to arise after iPhone updates, both major and minor, and sometimes after restoring or transferring data to a new iPhone, but it usually sorts itself out within a day or two and can be headed off by deleting and recreating alarms.

Restarting the phone clears a surprising number of stuck-audio cases. Some users report that even after disconnecting Bluetooth, the iPhone stays in headphone mode until restarted — if a test alarm is silent, a quick restart usually clears it. If none of that works, a full settings reset is the next step: reset all settings via Settings → General → Transfer or Reset iPhone → Reset → Reset All Settings, which resets system preferences to defaults without erasing your data. For anything beyond that, Apple's guide on how to set and change alarms on iPhone covers the volume slider and sound settings in full, and the developer-side bug tracker for the AlarmKit regression on iOS 26.2 is documented on Apple's developer forums.

Does a calendar alarm app avoid this problem?

Partly. A separate alarm app doesn't fix Attention-Aware Features or a stuck Bluetooth route, but it does remove the single point of failure that comes from relying on one Clock app entry per event, and it stops meetings from silently depending on notification-style calendar alerts that Focus and Silent mode are allowed to suppress. That's the actual failure mode behind most missed meetings — covered in why calendar reminders don't wake you up.

Pealo converts calendar events from Google Calendar, Outlook, or iCloud into real AlarmKit alarms rather than notifications, so a meeting rings through Silent mode the same way a Clock alarm does, without needing you to duplicate every event by hand into the Clock app. It's a different mechanism from typing times into Clock — see how the two compare in Pealo vs the iPhone Alarm, or check current plans on the Pealo pricing page.