Has ping / tracert been blocked on 5g network?

I use pingplotter (pingplotter.com) and it has always been working for me.

The blocking/failure of using the ping utility seems to vary from one location to another. Here in east TN we had a period of time when it was failing to work but now it does. More than likely there is a configuration parameter in place to block ping packets. T-Mobile can run it down if they are motivated to do so. They may not be aware of the behavior in that location. Once they had enough complaints here they addressed the behavior and now it seems to be resolved. Well, it works here. You might try doing an IPv6 ping vs the IPv4 ping and see if there is a difference in behavior from one to the other. It might take a call to T-Mobile support to possibly get headway.

Oh, I also have the T-Mobile home internet router and ping is blocked for wired and wireless devices connected to the router. 

I have been battling with this for months in the Phoenix AZ area. My other phone is AT&T and they are also blocking ping/trace. 

This has been a problem for me off and on since its inception and through multiple TMHI gateways.  IPV4 ICMP pings just randomly fail sometimes for days.  Or latency just varies dramatically.  Rebooting the gateway works sometimes and other times not so much.  Not sure what is causing this exactly BUT IPV6 seems to work every time.  So it could be related to their CGNAT implementation or a combination of that and the gateway firmware.  I use a dual WAN OPNSense setup and need to monitor WAN quality to pick the best ISP.  Right now I have just disabled monitoring on that interface to get by but I may have to try to get IPV6 working on WAN interface to fix this permanently.  But that's a big bunch of complexity that I really don't want to undertake.  I don't have any wired ISP's in my area so I am stuck with TMO and ATT until Verizon offers their wireless internet in my area.   If anyone comes up with a solution please let us know here.  Gracias.   

I ran a test here in East TN which our traffic routes out of Nashville and I can see the latency is up going to multiple targets. I saw similar times but no loss to the same target quad9 and latency roughly the same. I hit google.com, and cloudflare.com as well and see the same general impact. I ran a speed test and I am still getting ~300 MBs down and 44 MBs uploads so not an impact to flow is seems. 

Testing with speed.cloudflare.com results in 200 MBs down but different test. Ping latency with the Cloud Flare test to Chicago from Nashville was not bad but different scenario so not apples for apples comparison. At least the ICMP traffic is not as extreme as last time. Downdetector.com reports no outages for T-Mobile so hard to say what is causing the delay. Blame it on cosmic radiation.

Same issue here in Savannah, GA area!! Ping time-out issues that started around May or so… Tech support was no help… 

Pings are working again in the Littlerock, AR area, but very slow all day

20:02:52.893 : Reply[3644] from google.com: bytes=32 time=504.5 ms TTL=114
20:02:54.442 : Reply[3645] from google.com: bytes=32 time=548.2 ms TTL=114
20:02:56.068 : Reply[3646] from google.com: bytes=32 time=623.7 ms TTL=114
20:02:58.070 : 142.250.72.46: request timed out
20:02:58.934 : Reply[3648] from google.com: bytes=32 time=864.4 ms TTL=114
20:03:00.427 : Reply[3649] from google.com: bytes=32 time=491.3 ms TTL=114
20:03:02.089 : Reply[3650] from google.com: bytes=32 time=660.5 ms TTL=114
20:03:03.645 : Reply[3651] from google.com: bytes=32 time=555.3 ms TTL=114
20:03:05.182 : Reply[3652] from google.com: bytes=32 time=536.5 ms TTL=114
20:03:06.765 : Reply[3653] from google.com: bytes=32 time=580.7 ms TTL=114
20:03:08.435 : Reply[3654] from google.com: bytes=32 time=669.0 ms TTL=114
20:03:10.257 : Reply[3655] from google.com: bytes=32 time=821.8 ms TTL=114
20:03:11.994 : Reply[3656] from google.com: bytes=32 time=735.7 ms TTL=114
20:03:13.547 : Reply[3657] from google.com: bytes=32 time=551.6 ms TTL=114
20:03:15.114 : Reply[3658] from google.com: bytes=32 time=564.9 ms TTL=114
20:03:16.925 : Reply[3659] from google.com: bytes=32 time=809.9 ms TTL=114

I am honestly surprised no tech blog or YouTube channel picked up T-Mobile blocking ping. You would think it would be newsworthy in the tech circle. 

iTinkeralot wrote:

                                                                                                                                                                                                                                                                                                                                                           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. 

Comcast or other? where at in Ca?