Was IP banned, now cannot get game data (Second ban wave?)

[bsd]

So this morning I was IP banned. I changed my IP, then logged in. No problem. Shut the game down and went to work, tested at work that I could log in without issue. All was fine until I got home. I went from IP ban, to no botting at all on the account, to cannot get game data.

Switched accounts on the phone, all the same settings, boom, right in.

My sneaking suspicion is the game data is not available because Niantic is actually looking at it. They went through a first wave and are now looking at other accounts.

No teleporting today, nothing changed except time that elapsed.

 

[zardichar]

Honestly bizarre they'd even IP ban considering how archaic and flawed it is. I play on a uni campus wifi with thousands of others, if I got IP banned would they or do they limit to a specific subnet?

Pretty surprised they would even mess with IP bans but whatever. I'm lucky to have not been banned yet but I'm curious how far they'll look into it once this "ban wave" (if it is a ban wave) completes.

 

[bsd]

I have tried logging into 2 phones, fake gps with last known location, real location etc. It's like initially just an IP ban but then they went and decided to scrub more accounts as other accounts were allowed to log in.

From a database perspective, if you don't want new data written, this would happen. Once done, it's writable (you can log in again). I have a feeling they are honestly looking for as much info as possible to prevent ALL possible botting.

This would explain no announcements, no emails saying you are banned etc.

 

[ajbram387]

I have not been IP banned, but I have noticed more accounts being banned...

I had 1 account 'hard banned' (failed to get game data) around the time of the first ban reports (24hrs+). I have 6+ total. No teleporting, no sniping, all stay within my city. I turned off all the bots since the report and checked each account to see if they were alright. All were fine except that 1. Since that first wave I've had 3 more accounts get that error (found out this morning). Not sure what's going on or what's the common denominator....