If a fixed nighttime boundary fits your routine, you can download 9to9 from the App Store and choose the apps and websites you want quiet from 9 PM to 9 AM.
You set up Downtime, the schedule is on, the hour arrives — and the apps open anyway. It is one of the more quietly maddening iOS experiences, because everything looks correct and nothing behaves that way. The good news is that Downtime is almost never actually broken. It is almost always a configuration detail — a toggle left off, a list left too generous, a schedule that says something slightly different than you think. Seven checks cover nearly every cause. Go through them in order before you delete anything or assume the feature does not work.
A note on how to test as you go: after each fix, do not wait for the scheduled hour. Set the window to start in the next few minutes, or check whether the app is dimmed and shielded right away. Testing in real time turns a week of nightly disappointment into ten minutes of debugging — which is what this should be, not a recurring mystery.
1. Block at Downtime is the whole ballgame
Start here, because it is the single most common cause and the easiest to miss. Inside Settings, then Screen Time, then Downtime, there is a toggle separate from the schedule itself: Block at Downtime. The schedule can be on, the hours can be right, and Downtime will still do nothing but dim icons and warn — because without that toggle, it is a notification rather than a restriction.
Check it first. If it was off, that was probably the entire problem, and the fix takes four seconds. This is the difference between the feature's two modes: advisory and actual. A surprising number of “Downtime doesn't work” complaints are just the advisory mode doing exactly what it was told.
It is also worth knowing what “blocked” looks like when it is working, so you can tell the difference. With Block at Downtime on, a restricted app's icon dims and tapping it produces a shield — a clear wall, not a warning. If instead you are getting a notification-style nudge that lets you through with a tap, the schedule is running in advisory mode and the toggle is the fix.
Sources: Set schedules with Screen Time on iPhone (Apple Support)
2. Audit Always Allowed like it is guilty
The second most common cause: the app you expected to be blocked is on the exceptions list. Always Allowed is the roster of apps and contacts that stay reachable during Downtime, and it defaults to more generous than people remember. Phone, Messages, FaceTime are typically there by default — reasonably — but over time other apps get added, and once something is on that list, Downtime does not touch it no matter what the schedule says.
Open Settings, then Screen Time, then Always Allowed, and read it like a list of suspects rather than a list of essentials. Any app on there that turns into a session at night — the social feed, the browser, the short video — needs to come off. The honest version of this list is short: the things you would genuinely need in an emergency or a real task, and nothing else.
The subtle version of this failure is the category sneak-through: you removed the app from Always Allowed but Safari is still there, and the feed works fine in a browser. The allow-list audit has to include the browser question too — if Safari stays allowed, every website on it is a door the app block did not close.
3. Check the schedule against the actual day
Overnight schedules are easy to get subtly wrong. Verify that the start and end times are what you intended — 9 PM versus 9 AM is a mistake the interface makes easy — and that the schedule applies to the day you are testing. If you customized by day, a Tuesday-only schedule does nothing on a Friday, and a schedule set to begin at 11 PM is invisible at 9.
Also check the clock's own assumptions: if the time looks right but nothing happens, confirm the hour format (AM versus PM) and that the schedule is actually enabled rather than just configured. The difference between a schedule that exists and a schedule that is on is the whole ballgame.
One more schedule subtlety worth checking: whether the window is set to run during the hours you actually mean. A Downtime set for 9 AM to 9 PM — the workday, not the night — is a schedule that is technically working and completely inverted from what you wanted. It happens more than it should; the fix is just reading the times literally.
3.5 A note on the passcode question
While you are in these settings, a related detail worth checking: whether a Screen Time passcode is set and whether you know it. A passcode you set yourself does not prevent the failure you are debugging — it just adds a step to the override — but a forgotten or mismanaged one can produce behavior that looks like a broken schedule: prompts that do not behave as expected, settings that seem not to stick. If the passcode exists and you did not set it — a family member's device, a managed phone — that is the layer to look at.
4. Downtime and App Limits are different controls
This one catches people who think they set a schedule but actually set a budget. App Limits cap total daily minutes — they have no idea what time it is, only how much has been used. Downtime controls when apps are available at all. If you configured an App Limit expecting a nightly block, you built the wrong thing: a thirty-minute allowance will happily let you spend all thirty minutes in bed at midnight.
Check which feature you actually edited. If your goal was a window, you want Downtime; the limit is a different instrument for a different problem, and the two being neighbors in the same menu is what makes the confusion so common.
4.5 A note on app-level versus total blocking
A related confusion worth separating: some people set up Downtime expecting it to behave like an app-by-app block — picking which apps get restricted during the window. That is not how it works. Downtime restricts everything except the Always Allowed list; it is a broad restriction with exceptions, not a per-app scheduler. If your goal is “block these three apps at night, leave the rest alone,” Downtime can do it — but only by exempting everything else, which is exactly the allow-list maintenance described above. Knowing the model prevents an evening of expecting a precision the tool does not have.
5. Decide whether Screen Time syncs across devices
If you use more than one Apple device — an iPad, a Mac — there is a setting called Share Across Devices that decides whether the same Screen Time rules apply everywhere. When it behaves inconsistently — blocked on the phone, open on the iPad — this toggle is usually why. Decide deliberately whether you want the rules to follow you across devices or live per-device, because a schedule that means one thing on one screen and another on the other is the kind of inconsistency that makes the whole setup feel broken when it is actually just split.
6. When the settings are right and it still misbehaves
Occasionally the configuration is correct and the behavior is stale — Screen Time, like any software, can lag. The boring fixes first: restart the iPhone, check for an iOS update and install it, then test the schedule again. Also confirm you are not accidentally bypassing with a Screen Time passcode you set yourself — the passcode that makes limits enforceable is the same one that, if you know it, makes them optional.
If none of that works, the problem may be upstream: a managed device, a family-sharing configuration, or a sync issue that needs a deeper look. But go through the ordinary causes first; they cover the overwhelming majority.
7. Consider whether the tool is the problem
The last check is the least technical and sometimes the most useful. If you have been through the settings and the arrangement still does not hold — if the allow-list keeps growing, if the overrides keep happening, if maintaining the system has become a small ongoing job — it is worth asking whether the tool fits the problem. Downtime's broad-to-narrow model is powerful but it is also maintenance: you are always managing exceptions.
There is a version of this troubleshooting that never ends, and it is worth recognizing: the person who keeps the system running by constantly fixing it is doing the thing the system was supposed to prevent — spending attention on the phone's rules at exactly the hours it should be protecting. If your Downtime setup needs a monthly audit and a weekly override, the tool is the problem, not your configuration of it.
A narrower blocker exists for exactly this: 9to9 takes the opposite approach — you pick the distracting apps and websites once, and the same 9 PM to 9 AM window applies every day, automatically, with a five-minute Temporary Access for the genuine needs. No allow-list to tend, no schedule to get wrong, nothing to renegotiate at the hour when it matters. If Downtime keeps failing not because it is broken but because its model asks more upkeep than you want to give, that is the simpler shape.
The two questions people actually ask
Why do some apps look blocked but still open? Usually Block at Downtime is off, the app is in Always Allowed, or a passcode is quietly overriding. Check those three before anything else.
Will reinstalling the app fix it? Almost never. The app is not the problem — the configuration around it is, and reinstalling leaves the configuration untouched.
And if the whole thing feels like more machinery than the problem deserves? That is a fair response, and it is the reason the fixed-schedule alternative exists. The point was never to master Screen Time. It was to have an evening that ends.
One last honest note: if you have been through all seven and the block still does not hold, the explanation is almost never that the iPhone is broken. It is that the system is asking you to maintain a boundary at the exact layer where you keep needing to override it — and at that point, the fix is less about the settings and more about choosing a tool whose boundary does not live where your bypass does.
A faster diagnosis, in one place
If you want the whole thing as a checklist rather than a guide: confirm Block at Downtime is on; audit Always Allowed for the app you expected blocked; verify the schedule's days and AM/PM; confirm you configured Downtime and not App Limits; check whether Share Across Devices is splitting the rule; restart and update if the behavior is stale; and if the upkeep is the real problem, switch to a fixed tool. Six of the seven are toggles. The seventh is admitting the tool was more than you needed.