Has ping / tracert been blocked on 5g network?

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:

Ping and Trace Route both leverage ICMP to function so it just makes sense that both fail. I would guess with a VPN open both would work fine. It is hard to say what T-Mobile will do next with their solution. I have been getting more apprehensive since the gateway has now transitioned from the n71 to the n41 frequency. I have seen so many reports of users on the n41 where the throttling T-Mobile does pretty much cripples the cell beyond use. The prioritization for mobile handsets over the home gateways and the extra client loading in the urban locations just seems to be a bad mess. On the bright side my speeds have doubled or better on downloads much of the time. 

Choking the ICMP traffic as they have makes no sense to me. Bad move. I used ports 8080 and 443 pinging and it still behaves the same. It looks like they just throttled ICMP to death. For users that do much more than check email, browser the web, or stream a few select services they will eventually jump ship and get another solution that is more reliable and capable.

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.

Now the Arcadyan and also the Sagemcon gateway both require the T-Mobile home internet mobile application ONLY for administrative management as the go to. It is the go forward T-Mobile seems to have decided upon. Probably due to cost reductions for device code development and etc… It does not feel like an improvement for the end user. 

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.

Testing with a Garuda Linux client with a verbose ping to 8.8.8.8 currently it runs with roughly 100 ms latency but out of 43 packets sent 13 received responses so roughly 70% packet loss. Running a speedtest I am still obtaining 275-300 down and meh… 21 mbps upload so the bandwidth is there but the ICMP traffic is impaired or throttled. I sort of suspect it has something to do with throttling for one reason or another. I suppose it may be related to changes with the CGNAT solution but probably a throttling of the traffic. Testing with a MacBook Pro via a thunderbolt to ethernet adapter the response times are worse than with either of the Linux clients I have used but still bad either way. 

traceroute to 8.8.8.8 (8.8.8.8), 64 hops max, 52 byte packets

1  www.webgui.nokiawifi.com (192.168.12.1)  2.145 ms  0.376 ms  0.279 ms

2  192.0.0.1 (192.0.0.1)  0.533 ms  0.698 ms  0.449 ms

3  * 192.0.0.1 (192.0.0.1)  27.721 ms  29.890 ms

4  * * 192.0.0.1 (192.0.0.1)  35.968 ms

5  192.0.0.1 (192.0.0.1)  30.243 ms *  46.172 ms

6  * * *

7  * * *

8  * * *

9  * * *

10  10.164.162.176 (10.164.162.176)  509.603 ms * *

11  * * *

12  * * *

13  * * *

14  * * *

15  * * *

16  *^C

Pretty clear it is useless without using a VPN.

I noticed about 4 days ago that most pings now fail.  If I do a continuous ping(-t) roughly 1 in 20 gets a response, and all are over 100 ms.  Using pinginfoview, I can set the port it uses, and they work.

TMobile needs to fix this.  Lots of people use ping to check connectivity, and it's just going to make them look bad.

Same here in Littlerock AR.  I am a Citrix Admin (Working remote 100% of the time); I always have the end user ping our NetScaler gateway to see that the response time is when they say their remote session is sluggish.

Now even I cannot get a reliable ping response, but I am still able to work remotely.

Seems like ICMP has been throttled.

Not good.

Might have to go back to SuddenLink.

Cannot use this connection if I cannot even ping a remote site.

On the bright side, a new ISP is coming to my area with fiber, still under construction but fingers crossed they are better than SuddenLink and Century Link

Ejemplo:

Pinging google.com [142.250.72.46] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 142.250.72.46: bytes=32 time=117ms TTL=110
Request timed out.
Request timed out.
Request timed out.

With all the Request time outs, my Internet is fine.

If I RDP into a computer at work and ping a remote site, I get great ping responses.

I am in east TN with the Nokia gateway and I ran a quick test with a Macbook Pro and a Linux client. With the Macbook Pro the pings have a significant delay where several request time out messages were reported prior to an actual response typically 140+ ms between responses. I went to a Linux client and did a forced ipv6 ping based upon a prior test. I get a similar response performing IPv6 and IPv4. Both have extreme delay times and are not very useful Of the forced 23 ipv6 ping packets 5 were received with a ~78% loss. So, yes it appears T-Mobile has jacked up the use of ICMP as a trouble shooting tool. 

Based upon the two tests I ran it appears pings with IPv4 fail much worse than IPv6 pings but the use of pings now is pretty much useless.

I fail to see why they feel this would be positive for users. Make it more difficult for users to identify potential issues so they are totally blind. It just makes calls to TMO support less productive when users with such basic knowledge cannot tell support what they do not see.