Google blocking search

HeavenM wrote:

Hey everybody! We really want to find out why exactly this error is occurring and appreciate everyone that is speaking up about it. Filing tickets with our care team is a great way to draw attention to what exactly is going on, but I am also sending your feedback to our T-Mobile Internet team to have it reviewed. 

To pin down exactly what is happening, the information that is extremely helpful is you IP address, time, and city/state when you get the error. Some may not be totally comfortable with sharing that information on the public thread, but if you send me a DM with those details, I can pass it along. 

¡Gracias!

I just sent a DM.  I'm in Foley, AL, although my IP address generally seems to locate to Louisiana.  Thank you for addressing this.

KapFL wrote:

I wonder if this is national or just focused more in one part of the country.  I'm located in the NorthWest panhandle of FL (new Pensacola).  I see a New Orleans, an Ohio, and a Shreveport LA.   

I'm in Louisiana. I really dislike having to bring this up but, is everyone here a Republican? Not saying that's why, yet, just want to rule it out. 
 

I've been dealing with it for about a week now. All devices in the home and T Mobile internet and phone service. Hasn't happened to me while away from the home. 

KapFL wrote:

T-Mobile needs to take a lead to fix it rather than toss out a not-my-problem statement.  Let's get this moving before customers start moving to new services.  

I really expected this to be fixed by now and it's frustrating that nothing's been done about it. Are we just supposed to sit here for weeks completing captchas every time we Google? Pretty sure it's just an issue of Google flagging T-Mobile IPs as abusive - shouldn't TMo be able to say "Hey, these are our dynamic IPs, stop blocking them"? Or at least change the IPs being assigned to customers until they figure out what the core issue is. Either way this is getting pretty old.

it really should be that simple!

qraqson wrote:

KapFL wrote:

T-Mobile needs to take a lead to fix it rather than toss out a not-my-problem statement.  Let's get this moving before customers start moving to new services.  

I really expected this to be fixed by now and it's frustrating that nothing's been done about it. Are we just supposed to sit here for weeks completing captchas every time we Google? Pretty sure it's just an issue of Google flagging T-Mobile IPs as abusive - shouldn't TMo be able to say "Hey, these are our dynamic IPs, stop blocking them"? Or at least change the IPs being assigned to customers until they figure out what the core issue is. Either way this is getting pretty old.

this would be something both TMO and Google would have to figure out...kick out fixes...test those..adjust again as needed..then once its been vetted to work then the update gets kicked out to fix it..there isnt a switch they just flick and all is good..there will be a bunch of back and forth..especially to figure out why its happening in the first place..

qraqson wrote:

KapFL wrote:

T-Mobile needs to take a lead to fix it rather than toss out a not-my-problem statement.  Let's get this moving before customers start moving to new services.  

I really expected this to be fixed by now and it's frustrating that nothing's been done about it. Are we just supposed to sit here for weeks completing captchas every time we Google? Pretty sure it's just an issue of Google flagging T-Mobile IPs as abusive - shouldn't TMo be able to say "Hey, these are our dynamic IPs, stop blocking them"? Or at least change the IPs being assigned to customers until they figure out what the core issue is. Either way this is getting pretty old.

I first reported this issue in this same thread almost a week ago, and honestly thought I was going to be fixed soon. I came back here to see if there were any updates since the issue is still going, and I can't believe they're playing the old "not my issue, they have to fix it so you're gonna have to wait for them" card. This is quite obviously an T-Mobile issue, seeing how there's a trend on the IP addresses and their locations. Ridiculous. 

AmySM wrote:

KapFL wrote:

I wonder if this is national or just focused more in one part of the country.  I'm located in the NorthWest panhandle of FL (new Pensacola).  I see a New Orleans, an Ohio, and a Shreveport LA.   

I'm in Louisiana. I really dislike having to bring this up but, is everyone here a Republican? Not saying that's why, yet, just want to rule it out. 
 

I've been dealing with it for about a week now. All devices in the home and T Mobile internet and phone service. Hasn't happened to me while away from the home. 

 

No.. LMAO this is not a republican conspiracy thing. How did you even come to that conclusion, why was it your first guess? Paranoia?

KapFL wrote:

I wonder if this is national or just focused more in one part of the country.  I'm located in the NorthWest panhandle of FL (new Pensacola).  I see a New Orleans, an Ohio, and a Shreveport LA.   

I live about an hour from Pcola and have been having this happen for the last day

I’ve running into the same issue as well, in SW Michigan, for several days, on all devices (iphones, Macs, Windows) connecting through my tmobile gateway…. 

Have not had any issues while devices are using competitors’ networks.

(Issue happens specifically when going to google.com services (search, maps, etc.)

@HeavenM is there anything additional we as customers can be doing to get this escalated? Twitter posts, etc to make t-mobile publicly acknowledge it's a growing problem for their customers?