Google Fiber at home slow only for work VPN. Reasonably fast for others

This is the work VPN, your tunnel is likely limited on the Corp side.

Ah. Thanks for answering the questions. With your reiteration, I see where I missed that in the original post.

So, searching for “isp throttle vpn”, I see it can be a thing. Seems like the best suggestion is to try changing the protocol. Though this was here more towards personal VPNs. I think relatively few corporate VPNs let the average user change protocol, of different ones are even supported.

And you have checked all the things I thought about. So you might have to open a help ticket with your ISP to see if someone accidentally flagged you as troublesome, or something changed wrongly in their configuration.

Sounds frustrating, but interesting at the same time. Do you happen to have a little travel router with a VPN installed? I’m curious if you set up a travel router and connected to that instead and had a double VPN setup. I know normally this would be painfully slow, but I am curious.

By inspect I didn’t mean view the specific data in the packet. Only that sometimes VPN/encrypted packets flag as more suspicious to an ISP. They can’t see the data in the packet, but they can still see that the packet is a VPN/encrypted packet and some choose to throttle that data.

I am far from an expert. This is something that my workplace’s network team has mentioned for users with VPN slowness, and that for some users packets over IPSec protocol are throttled more than those over SSL, depending on ISP.

If that were true i would experience this everywhere…but i dont. Connecting to the vpn on other wifi networks outside my apt or using 5g work great.

Yea this is where im landing. I opened a ticket with gfiber and sent them a bunch of traceroutes. We’ll see what they say.

Just commented below, but tried the double VPN setup and that does fix it. Not only does it fix it, my work VPN connection is like twice as fast now. It’s gotta be a network path issue then. Don’t think Google is gonna fix that though.

Thanks for the update and glad it worked. It gives you the answer though.