this post was submitted on 24 Sep 2025
870 points (95.2% liked)
Technology
75458 readers
2391 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related news or articles.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Is this maybe much more common on common VPN IPs? Not what I think you meant by "local ISP", but would make a lot more sense to me.
It wasn't that way until earlier this year. I switched to a vpn to get around it. I'm using non US VPS in a country that is less tolerant of googles bullshit.
To be clear the cable IPs are a /20 block that was routed to the cable companies predecessor in 2016. I'm the one who put in the request with ARIN. The new company that acquired this system was bought out by yet another company before the sale went through. I just looked and Cable one has purchased a large stake late last year. All in all it still works okay. Their support though is clueless due to flowchart ignorance. The plant OPs guy stayed the same and he knows how to keep the levels balanced and noise out.
It is definitely more common on VPN IPs, since Google likely identifies the outgoing address as a datacentre, and gets suspicious. I've had multiple issues with the bot sign-in screen when using a VPN for it, whereas not using a VPN doesn't have those problems.