Has ping / tracert been blocked on 5g network?

I really don't get why they feel the need to block or choke ICMP traffic. Some over aggressive control freak decided to be all Rambo on users it seems. The more bad choices T-Mobile makes the more they will keep pushing customers away. If they really want to kick ATT and Verizon about they need to do it better not just put a thin veneer on it. You can put lipstick and a dress on a pig but it is still a pig. 

in Phoenix area too. These changes may be the cause of our unpleasant experience recently.
 

1) We have a Ting Fire device that monitor's the electrical wiring of our home and it sends information out. It went offline. Couldn't get it to work, but took the device to a neighbors house and no issues…

2) Had challenges joining a homeowner's association meeting. The HOA property management firm uses Microsoft Teams. I was able to get on after a couple attempts. Microsoft email seems to have quirks sending out emails now too.

3) Don’t know if it is an Apple iOS/tvOS16.1 issue or T-Mobile change issue, but watching services through Apple TV has had streaming services like Disney, Hulu, Amazon say oops, we can’t connect or your are offline, this is sporadic.

Signal strength and quality haven't changed. I check the numbers monthly.

If this were a deliberate decision, T-Mobile may be causing issues with the way other company’s products work.

I hope this is a technical error.

I live in WV and started noticing the ping issue rear its ugly head on Friday. I first thought it was something on my network going bad or my ad blocker messing up but narrowed it down to T-Mobile. I'm with everyone else, I can't understand why they are blocking such a critical thing. Glad to see that I'm not alone in the issue.

I hope more people realized there is an issue, find this post, sign in and post. This has to get to 40 pages in my mind before something happens to make this newsworthy.

Here’s my perspective, I’ve called in on several issues on different products recently, writing to a half dozen companies as a heads up that there are problems and neither issue has been resolved or hit the media.

1. Apple Airplay2 functionality is busted in iOS/iPadOS 16 on non-Apple devices. It may, or may not, have to do something with Apple Home App and Matter integration standards. I can find a lot more articles on issues for this topic right now on Reddit and other sites but none appear to connect the dots between products - they are focused on one manufacturer's product, when the issue is Apple AND the manufacturer. From Sonos to Belkin, to receiver manufacturers like Yamaha and Onkyo this is big. This specific issue has been known since July when beta testers were testing the new iOS software and reported it. Airplay2 still works correctly in Mac OS - Ventura. Go to Belkin.com and look up their Soundform Connect and that device's questions page has customers giving it bad reviews because of the issue blaming Belkin for selling the device that doesn't work. Belkin's response has been to please reach out to a special email address to get support. Airplay2 worked, pre iOS 16, then the issues started (the changes in the Home App's code were being implemented due to upcoming Matter integration). While I am significantly impacted having multiple zones in my home using receivers to send AirPlay information to from my phones or iPads, most people probably just use Apple TVs and Apple Home Pod minis and don't experience the issue, since Apple's own devices don't have the issue.
2. Amazon has been selling a device for at least two years where each device's ethernet port of that product is hard coded with the same MAC address making them useless on ethernet if you have more than two devices - you can use over WI-FI... There are threads from the US and India on it, but none are more than four pages long. There are now reviews on Amazon saying the issue, I put a review one out there, it was reviewed by Amazon, but the group that received my call, the group that reviewed my review are not the development team and that's who needs to see it OR an executive of the company. There are several options to fix, including spoofing a MAC address in the device firmware but it has gone no where. Too niche of an issue and not newsworthy. These are higher end products, sold by Amazon, and since WI-FI works for most that's the resolution from support.

This issue is too new, and our situation is a little more unique than we may like to admit. It impacts us, and some of us more than others, but the average user probably just thinks it is the "the tower is under construction". Here's the headlines I have seen recently that are newsworthy to T-Mobile

1. everyone loves T-Mobile; https://www.tmonews.com/2022/10/t-mobile-earns-highest-score-in-j-d-power-2022-us-business-wireless-satisfaction-study/
2. we could be facing an uphill battle - I’ve only seen this report on one site, yet it seems like this is a bigger concern overall, to me. https://thedesk.net/2022/08/t-mobile-home-internet-problems-tower-upgrades/

inductivesoul wrote:

Yes, as of my post it seems T-Mobile is actively blocking Ping, Tracert, Traceroute and ICMP in addition if they do go through at all, they are deprioritized to the point that they are not effective to use in any capacity.

This sucks really bad... 

I use multiple uplinks and depending on the RTT, RTTSD, Loss it switches providers to balance connections across them… 

This behavior from the ISP breaks tons of functions as well as my link down failover automations. I hope T-Mobile realizes that ping and tracert/tracroute are 1000% necessary for proper network management and trouble shooting.

 

Verizon and AT&T don't have this problem of blocking pings, it is a T-Mobile specific issue and really makes the brand look cheap and the network mismanaged. 

You can have a secure network without blocking normal and essential network tools that have existed since before I was born.

^^^^ THIS RIGHT HERE!!! ^^^^
T-Mobile has a broken network or is actively breaking their network to the detriment of paying subscribers.

If this was a conscious business decision by T-Mobile, shame on you. Have you updated your terms of service to list the blocking of common network monitoring and management protocols as a feature of your service? 
 

If it is an error - identify the root cause, fix it, and apologize.

Yours Truly,

A formerly happy, now very pissed off customer in North-Central Ohio…

Having the same problem here. Started a few weeks ago. Makes my load balancing/failover setup useless. TMHI is supposed to be my backup internet. Useless at this point. Going to cancel if this isn't fixed soon.

Aaand it's broken again.

This is making me think tmo doesn't really know how to isp. 

                                                                                                                                                                                                                                                                                                                                                           I sometimes question some of the things they have decided to do but it is out of my control. I just focus on what I have control of. I had almost no options here and this provides a good balance between cost and functionality. I don't have the needs I once had and my only other option with more functionality was Starlink and that is just more than I need to shell out. This solution is still 10X better than the DSL solution we had with our prior ISP in CA. That was a reboot the router at least once or twice a week. If it was wonky just reboot the router. Actually since the stood up the n41 cell over this location the bandwidth is more like 10-14X the speeds we had on DSL. Life in a rural area just has a few compromises for some things. In many other ways it is a big win. 

Found out after doing a factory reset (arcadyan version) today, that the ability to separate the 2.4ghz and 5ghz bands into separate SSIDs has been removed from the webGui (192.168.12.1).   Seems odd they would remove that ability from the user.

My ping to google.com works fine via Mac Terminal. I'm in Los Angeles.

PING google.com (142.250.72.238): 56 data bytes
64 bytes from 142.250.72.238: icmp_seq=0 ttl=50 time=21.246 ms
64 bytes from 142.250.72.238: icmp_seq=1 ttl=50 time=24.115 ms
64 bytes from 142.250.72.238: icmp_seq=2 ttl=50 time=23.327 ms
64 bytes from 142.250.72.238: icmp_seq=3 ttl=50 time=49.096 ms

And this is my speed test: