Why Am I Getting Notifications on Do Not Disturb? (And How to Fix It)

Do Not Disturb is supposed to be your digital quiet time — no buzzes, no banners, no interruptions. So when notifications keep breaking through anyway, it feels like the feature isn't working. Most of the time, it is working. The problem is that DND has a surprisingly complex set of exceptions built in, and many of them are turned on by default.

Here's what's actually happening and why certain alerts keep getting through.

How Do Not Disturb Actually Works

DND doesn't block all notifications — it filters them. The feature silences most alerts, but every major platform (iOS, Android, Windows, macOS) ships with a set of override rules that allow specific notifications to bypass the silence. These rules exist for legitimate reasons: emergency alerts, alarms, and calls from close contacts are genuinely things most people don't want to miss even during quiet hours.

The catch is that these exceptions are often enabled by default, and many users never review them. So when a notification breaks through DND, it's usually not a bug — it's a rule you either set intentionally or inherited from your device's default configuration.

Common Reasons Notifications Break Through DND

🔔 Allowed Contacts or Favorites

Most DND implementations let calls or messages from specific people bypass the filter. On iOS, "Allowed People" can be set to Everyone, No One, Contacts, or Favorites. Android's DND has a similar "People" section where starred contacts or conversation exceptions can be defined.

If you're getting calls or texts during DND, check whether the sender is in your favorites list or has been individually granted an exception.

Repeated Calls

A near-universal DND exception: if the same number calls twice within a short window (typically around 3 minutes), the second call gets through. This is a safety feature designed to let someone reach you in a genuine emergency. It's on by default on both iOS and Android and is easy to forget about.

Alarms Are Almost Always Exempt

Alarms set through your device's built-in clock app are typically exempt from DND by default. This is intentional — most people still want to wake up even when they've silenced everything else. However, third-party alarm apps may or may not follow this rule depending on the platform and app permissions.

App-Specific Notification Permissions

Some apps can be granted Critical Alerts (iOS) or high-priority notification channels (Android) that are specifically designed to bypass DND. Medical apps, safety apps, and some government emergency systems use this capability. If you've approved an app that uses critical alerts, its notifications will come through regardless of DND status.

On iOS, you can check this under Settings → [App Name] → Notifications → Critical Alerts. On Android, notification channel priority is managed per-app under notification settings.

Focus Modes and Scheduled Automations

On iOS and macOS, Do Not Disturb is now part of the broader Focus system. If you have multiple Focus modes set up (Work, Sleep, Personal), and automations are toggling between them, you might be in a mode that looks like DND but has a different set of allowed apps and contacts configured.

On Android, Routines or Bedo automations can also activate and deactivate DND modes with different settings than what you manually configured. If your DND settings seem inconsistent at different times of day, automated triggers are worth checking.

Emergency and Government Alerts

Wireless Emergency Alerts (WEA) — including AMBER alerts, extreme weather warnings, and presidential alerts — are transmitted over a separate broadcast channel. These are designed to bypass nearly all phone settings, including DND, because they operate at the carrier network level rather than through the normal notification system. On most devices, you can manage (and in some cases disable) individual alert categories, but they are on by default.

Synced Devices and Notification Mirroring

If you use a smartwatch, tablet, or another device linked to the same account, notifications may be arriving on those devices even when your phone is silenced. Apple Watch, for example, has its own DND/Focus settings that operate independently of your iPhone's. If your wrist keeps buzzing, that device may not be configured to mirror your phone's DND state.

The Variables That Determine Your Situation

Checking Your Own Configuration

The most reliable way to diagnose notification bleed-through is to go through your DND or Focus settings methodically:

• Review allowed contacts and apps — even one allowed app in a high-traffic category (email, messaging) can explain a flood of exceptions
• Check for automation triggers — any app with access to your DND settings can switch modes on its own schedule
• Audit critical alert permissions — on iOS, this is a per-app setting that's easy to miss
• Inspect paired devices separately — each device needs its own DND configuration

The right configuration depends heavily on your own balance between availability and silence. Someone who needs to be reachable for family emergencies has genuinely different needs than someone doing a full digital detox — and the same DND feature supports both scenarios through its exception settings. 🔇

What's actually letting notifications through for you comes down to which of these layers applies to your specific device, OS version, installed apps, and how your exceptions were originally set up.