Google One VPN Is Retired; Pixel VPN Is a Different Service
Google One VPN was retired in June 2024, and Pixel VPN is a separate product with its own eligibility. Identify the service before resetting anything.
The VPN row in Settings still sits there, the toggle refuses to stay on, and the message mentions a product that Google stopped running in 2024. That row is a leftover record of a subscription benefit, not a damaged Wi-Fi stack, and no amount of network fiddling brings it back. Two things get confused at this point: the Google One benefit that ended in June 2024, and VPN by Google on Pixel, which Google documents separately with its own device list and its own regions. Read the label before you change a setting, because one of those products is gone and the other may never have applied to the phone in your hand.
Both names sit under the same Google account, which is why the mix-up is so common. Only one of them can be restored by anything you do on the device.
The label on the phone decides which product you have
Open Settings, then Network & internet, then VPN, and read the name on the row that will not connect. A row labelled VPN by Google One is a record of a benefit that ended, while a VPN by Google row belongs to the newer Pixel service and follows that service's rules. Both rows can survive on one handset after a plan change, and only the second can be made to work.
An old screenshot settles nothing, because it captures a state that has since moved on. A third-party Android client in the same list is a different arrangement with its own endpoint and its own operator, not a skin over a Google service. A paid Google One plan does not by itself put the newer product on a phone that Google does not list as supported. The label, the model number and the Android release are the three facts that decide the question.
Retirement has no undo, and resets have a price
Clearing the app storage of a retired client restores nothing, because no service is left for the app to reach. Sideloading an older build changes the provenance of the software on the phone, defeats the store signature that would otherwise vouch for it, and still cannot reopen a benefit that Google closed. Nothing on the handset makes a withdrawn product answer again.
Anything published before the retirement date describes the old arrangement. Read such a guide as history, not as a repair sequence.
A network reset is the expensive move people reach for next. On current Android releases it clears saved Wi-Fi networks, mobile data settings and Bluetooth pairings, and it does not touch product eligibility at all. Whether VPN profiles or user certificates go with it depends on the release, and clearing credentials is a separate action under security settings, so assume the profile may survive while the certificates may not. None of that changes the answer, which is the point: the reset costs you a working configuration and buys nothing in return.
A four-row eligibility check you can run in a minute
Work through these observations in order before changing anything. Stop at the first row that fails, because a later row cannot compensate for an earlier one.
| What to open | What a passing result looks like |
|---|---|
| Settings → About phone → Model | The model appears on the supported device list in the Pixel VPN guide |
| Settings → Network & internet → VPN | The row is named VPN by Google, not VPN by Google One |
| Settings → About phone → Android version | The release meets the minimum that the guide states |
| The availability message on that row | The wording names a supported device rather than an unsupported one |
A failure in the first or third row is a hardware and release answer, and no setting on the phone can revise it. A failure in the last row is the one worth reporting, because the exact wording is what separates an ineligible device from a service fault.
The Pixel VPN guide carries the device list, the regions and the account conditions these rows test against. Keep it open while you check, since the list changes and a blog post quoting an older copy sends you the wrong way. The guide is also the only place where a regional restriction is stated plainly, rather than inferred from a forum thread.
Where a reset still helps, and where it only costs you
A reset is the right tool for a corrupted network profile: Wi-Fi that will not associate, mobile data that no APN edit repairs, Bluetooth pairings that keep failing. Those faults live in the network layer, and the reset rebuilds that layer. A missing entitlement is not a network-layer fault, so the same action leaves the cause exactly where it was.
The cheaper moves follow the same rule. Changing DNS servers, cycling airplane mode, and forgetting and rejoining a network all act below the VPN layer. If the label on the VPN row still points at the retired product after you try them, you have confirmed the diagnosis rather than fixed it.
What to send when a current device really fails
When a supported Pixel device genuinely cannot connect, four facts make the report useful: the product name exactly as the VPN row shows it, the model and Android build, the availability message in full, and whether the underlying network works with the VPN switched off. That last one separates a tunnel failure from a phone with no working uplink at all.
A supported service that times out is a solvable problem. An entry for a retired product that refuses to connect is not, and reporting it as a fault only returns advice you have already tried.
If what you actually need is private access from a work laptop or a non-Pixel handset, pick that arrangement on its own terms. A Google-branded client was never a general-purpose gateway, and the retired one certainly is not.