Google's Pixel November Update Is Still Missing: What to Check
No November Pixel OTA a week in, while the security bulletin is already out. Here's what to check and what not to do.

A week into November, Pixel phones are still sitting on the October build. The Pixel November update hasn't appeared, and no changelog has either. That's unusual enough to be worth explaining.
The short version: the November Android security bulletin is already published, your phone just hasn't been given the build that carries it. Android Authority's explanation is a schedule change tied to Android 17 QPR2, and the outlet is careful to label that as speculation. Google hasn't said anything.
Here's what is confirmed and what isn't, as of November 9.
Item | Status |
|---|---|
November Pixel OTA | Not shipped as of November 7 |
November Android security bulletin | Published, patch level 2026-11-01 |
Play system and app updates | Still arriving on the normal schedule |
Android 17 QPR2 | Release candidate builds spotted, no release date |
What a missing monthly build actually costs you
Your phone keeps October's security patch level. Every fix in the November bulletin is a fix you don't have yet, and the bulletin isn't empty: it covers framework and system vulnerabilities rated high, the kind that need local access or a malicious app rather than a stranger on the internet.
So the practical exposure is small for most people and non-zero for everyone. The bigger annoyance is that you can't tell whether the delay is normal. A patch that arrives late by design looks exactly like a patch that got stuck.
The phone isn't frozen. Not even close. Play services, the Play Store and your apps keep updating on their own track, which is why nothing appears broken while the monthly build sits in limbo.
What a normal monthly build carries is worth remembering while you wait. It bundles the platform fixes from the bulletin, a short list of device-specific corrections, and occasionally a carrier configuration update that changes how your network behaves. None of it counts as feature work, and none of it shows up as a new app or setting. The October build you're on already covers the previous month's list, which is why the phone still feels fine.
The QPR2 theory, and why it's still a theory
Android 17 QPR2 release candidate builds have appeared on Google's storage servers. Android Authority read that as a sign Google may push QPR2 out early and fold the November patch into it, rather than shipping a standalone monthly build first.
It fits how Google has handled the last few cycles. Quarterly platform releases carry both fixes and feature drops, and a single larger download is cheaper to validate than two overlapping ones. Android 17 shipped in June, QPR1 landed in September with the Pixel Drop, so a QPR2 built on top of it looks like the next scheduled milestone anyway.
It also rests on inference. A release candidate on a server isn't a release note. Google has delayed monthly builds before without changing the cadence, and a skipped week in November doesn't prove anything about December.
If you got here by searching "Pixel update missing", you're one of a lot of people doing the same thing. That phrase being a common query is the only solid evidence that this is widespread rather than a handful of loud forum posts.
Check your build before you assume the worst
The first thing to rule out is your own phone, because a stalled update and a phone that never asked for one look identical from the outside.
- Open Settings → About phone → Android version.
- Read the build number and the security update date on that screen.
- If the date reads October 2026, you're on the last public build and the delay is Google's, not yours.
Then check the Play system update separately. Settings → About phone → Android version → Google Play system update carries its own date, and that module can move while the monthly OTA hasn't. A fresh date there tells you the update machinery on your phone works.
One more thing to ignore: the message that says your system is up to date. It's accurate, and it means nothing about scheduling. Google's update server answers with the newest build your device is allowed to receive today, so a phone that checks out fine on November 9 can still be waiting on a build that hasn't been published.
Two other things can make your phone look broken when it isn't. Carrier-locked models take builds from the carrier, which can trail unlocked units by days. And if you joined the Android Beta for Pixel program at any point, you're on the beta track, where monthly stable builds get replaced by QPR beta builds. Check Settings → System → Developer options or the beta program page to see whether your device is enrolled.
Don't sideload the beta to get ahead
The temptation is obvious: QPR2 builds exist, so why not grab one. Because the cost is higher than most people expect.
Flashing a factory image or a full OTA requires an unlocked bootloader, and the process wipes the device. Beta builds also aren't certified against the compatibility test suite, which means Play Integrity checks can fail. Banking apps, some games and a few work profiles treat that as a red flag and refuse to run.
If you have a spare Pixel and a free afternoon, go ahead. Spare phone, spare risk. On the phone that holds your bank app and your two-factor codes, waiting is the better trade.
What still protects you this month
Play Protect is doing more work than usual while the platform patch is behind. It scans apps you install from outside the Play Store, and it's the layer that catches a malicious sideload before it runs.
Keep it on, and be more careful than usual with APK files from forums and Telegram channels over the next few weeks. A phone one month behind on platform patches isn't a crisis. A phone one month behind with an unknown APK installed is a worse position.
If you handle work email or client data on the device, that's the case for being conservative: skip the unfamiliar APK, not the phone.
When the build will show up
Watch two pages instead of refreshing your phone settings every morning. Google's Pixel update bulletin lists the build number and patch level for each supported device, and the factory images page publishes the same builds for manual flashing. When a new build appears on either, the OTA follows within days.
If nothing appears by mid-November, the early-QPR2 theory gets stronger. If a standalone November build lands next week, the theory was wrong and the delay was ordinary.
Either way, the check is the same one you'd do any other month: Settings → System → Software update → Check for update. Do it once, note the date, and stop there.
FAQs
- Did Google cancel the November 2026 Pixel update?
- No cancellation has been announced. The build simply hasn't shipped, and Google hasn't explained why.
- Is my Pixel unsafe without the November patch?
- You're one month behind on platform fixes. Most of them need local access or a malicious app, so the risk is low for careful users, but it isn't zero.
- Will installing Android 17 QPR2 wipe my phone?
- A normal over-the-air update doesn't wipe anything. Flashing a factory image or a full OTA by hand does, and it needs an unlocked bootloader.
- Why does someone else's Pixel already have it?
- Rollouts move by region, model and carrier, and beta program devices run on a different track. A build going live elsewhere doesn't mean yours is broken.
The Google Pixel security patch for November is written and published. It just isn't on your phone yet, and nothing you do to the settings menu will speed that up. Check the build date once, decide if you can wait it out, and leave the beta images alone if this is your only device.