Before yesterday (10/17/2022), I've always had a command prompt window (MS Windows) up running a constant ping at 3 second interval - so I can tell when the network starts to degrade or just stops responding (which has become very frequent in the last few months).As of yesterday morning, both ping and tracert commands consistently fail. As in no longer any response. So it appears the ports used for those commands are now being blocked on the 5g network? I have a 5g phone on Tmobile, and I see the same result. On 5g with hotspot turned on, with computer connected, ping and tracert fail 100%. If I force the phone to use LTE and stay off 5g, ping and tracert start working again. Don't really understand why Tmobile would block such a basic network analysis command.This is in downtown Scottsdale AZ. As a sidenote, service on the 5g network degrades consistently every day after about 8am, and usually is consistently bad all weekend long. Works great before 8am most days.

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.

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.

I can understand that. Another user was using the T-Mobile solution as a back up and doing a similar tactic with his negate firewall. In order to insure the failover could take place he had to disable the ping processing. When the Starlink fell it still transitioned to the backup. I don't mean to lessen the importance of being able to have ICMP packets passed. I have seen the excessive loss and latency of the ICMP responses to 150 ms or more so I get it. I just don't think T-Mobile will be invested in resolving it right away. It is hard to tell how extensive the behavior is but it is generating some noise. Maybe with lots more noise they will pay attention.

ShanStewart wrote: Ok, i spoke to T-Mobile tech and they said they no longer support ping so that is interesting. FFS. Since we'e picking & choosing cucial communication potocols now, I've decided to no longe suppot the lette 'r'.

Hi, I too wish T-Mobile would fix this, and that the issue deserves to be newsworthy!I have been having major issues related to my T-Mobile home internet, primarily devices like home assistants and their accessories that rely on lower latency to fulfil requests. My Nest Mini now takes on average 10 full seconds to begin loading the response. Beyond that, issues with security since my cameras have increased lag making my doorbell camera less useful, and problems with my DNS not able to properly filter the web. I'm not the only one and neither are any of you: https://community.t-mobile.com/tv-home-internet-7/dns-provider-for-home-internet-38694Clearly this is an aggressive rollout of provisioning. To report my locale, I'm in the PNW but most of you are in the South/Midwest states like Texas. Well, location doesn't seem to matter IMO as I still have noticed many issues recently, to the timeframe given in this forum, in where my web filter has not been able to deny requests properly on one of my home computers. I believe ICMP details noted are related.Sadly enough, I am JUST learning how to network in college, in my second year and taking classes related specifically to latency and ping... So just wanted to note that I am genuinely affected by this… My own learning material has me doing these types of ICMP ping requests in Windows, and some posts here are lining up with my college material, but while learning from other members here has been fun, it also means to realize that my learning just got a lot harder BECAUSE of my fervent interest in bleeding-edge wireless tech… It doesn't have to be this way!When testing using Fast.com and other methods, I'm anywhere between 50ms and 1.2seconds loaded for latency. While that hasn't been an issue, what's different is that now never reporting the lower number. One second of latency means I can pretty much throw away my Xcloud membership LMAO I have much better results playing using my phone's mobile hotspot.Other tests, like Edge's in-browser utility, no longer can report latency at all and therefore the program hangs. Just as another user said, it makes it harder for a given person who doesn't know what's going on understand what's happening. This issue is compounded when the customers end up calling staff who have no source of truth for information on ping/latency leading to no progress for either party.All in all, this is snowballing quickly and the best action really is to roll back these changes or communicate the incoming fixes. At minimum, progress in this would feel like acknowledging that the official stance isn't that "ping isn't used anymore" by T-Mobile and instead the stance customers want to see would be closer to working on a solution to the existing latency and ICMP problem for T-Mobile Home Internet users Nationwide.Thanks to other forum members here, I understand now that if I want to continue to effectively filter my web I now need an addition device, a VPN (a hardware solution akin to a PfSense router) between my modem and personal router… and I would rather configure my own hardware like the ASUS modem I had before, but T-Mobile Home Internet does not support other hardware even if I did try and use a hotspot or 3rd-Party 5G Modem. I really don't want a bunch of networking equipment at home, I'd wanna leave that for school lol... so it's horrible to see this provisioning and clearly it's basically "love it or leave it" unless we outcry. So I'd like to join you all in a big +1 @inductivesoul @iTinkeralot @ShanStewart @Walkabt and ask T-Mobile to sympathize with customers, geeks and nerdy students alike and cool it with the way their locking down these gateways.

Has ping / tracert been blocked on 5g network?

Denuke
Roaming Rookie
Hace 2 años
I use pingplotter (pingplotter.com) and it has always been working for me.
iTinkeralot
Bandwidth Buff
Hace 2 años
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.
ShanStewart
Transmission Trainee
Hace 2 años
Oh, I also have the T-Mobile home internet router and ping is blocked for wired and wireless devices connected to the router.
ShanStewart
Transmission Trainee
Hace 2 años
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.
gff1stof3
Newbie Caller
Hace 2 años
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.
iTinkeralot
Bandwidth Buff
Hace 2 años
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.
Bryce13
Network Novice
Hace 2 años
Same issue here in Savannah, GA area!! Ping time-out issues that started around May or so… Tech support was no help…
Randall310
Newbie Caller
Hace 3 años
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
ShanStewart
Transmission Trainee
Hace 3 años
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.
fireguy_6364
Modem Master
Hace 3 años
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?