Home Internet Gateway Needs Reboot Multiple Times Daily, Internet Access Dropping
Multiple times on most days, at no particular time of day, internet access stops working. Devices can still connect to the WiFi network, but there is no internet access on WiFi or wired until the device gets turned off and back on. In rare cases it might work itself out within a matter of hours, for example if I am not home to reboot it. It has been like this the entire time I've had it, and it causes parts of my security system not to work, as well as stops my crypto mining that my PC does when I'm not using it, therefore actively costing me money when I'm not home to babysit the gateway (eg, at work). I really,reallywant to stick with T-Mo but I'll have to sign up with the local cable monopoly if uptime is this bad.
T-Mobile Home Internet infuriating, atrocious, and aggravating
Hi all, For the last few weeks, T-Mobile Home Internet has been infuriating, atrocious, and aggravating. I need to know how I can get T-Mobile support to resolve this and what possible solutions I can try. In a previous post T-Mobile Home Internet Slow IPv4 | T-Mobile CommunityI showed how IPv6 latency was much better than the worse than dial-up IPv4 latency. I was putting my Asus router on IPv6 pass-through. I've been using T-Mobile Home Internet for about 1 year or so. My issues with IPv4 started about 4-6 weeks ago. I started to implement DNS of TLS (DoT) and IPv6 passthrough on my Asus router. Since this time, my IPv4 experience has been absolutely infuriating. In a previous post, I showed how IPv6 was providing lower latency. This is not the case anymore. When I connect directly to the T-Mobile 4G router, both IPv4 and IPv6, latency is 100 Prior to tall these issues, my IPv4 latency was about 50-60 ms to many common locations. I was not even using IPv6.Now, no matter how many power cycles, or using DHCP default T-Mobile DNSservers and no DNS privacy, I now get average latency of about 250 ms but at times, dropping of data and really bad experience. Here is a current example of my latency, connected straight to the T-Mobile 4GTM-RTL0102: ping 192.168.12.1 -t Pinging 192.168.12.1 with 32 bytes of data: Reply from 192.168.12.1: bytes=32 time=3ms TTL=64 Reply from 192.168.12.1: bytes=32 time=4ms TTL=64 Reply from 192.168.12.1: bytes=32 time=3ms TTL=64 Reply from 192.168.12.1: bytes=32 time=4ms TTL=64 Reply from 192.168.12.1: bytes=32 time=3ms TTL=64 Reply from 192.168.12.1: bytes=32 time=4ms TTL=64 Ping statistics for 192.168.12.1: Packets: Sent = 6, Received = 6, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 3ms, Maximum = 4ms, Average = 3ms C:\>ping bing.com -t Pinging bing.com [2620:1ec:c11::200] with 32 bytes of data: Reply from 2620:1ec:c11::200: time=266ms Reply from 2620:1ec:c11::200: time=368ms Reply from 2620:1ec:c11::200: time=59ms Reply from 2620:1ec:c11::200: time=470ms Reply from 2620:1ec:c11::200: time=376ms Reply from 2620:1ec:c11::200: time=51ms Reply from 2620:1ec:c11::200: time=287ms Reply from 2620:1ec:c11::200: time=65ms Reply from 2620:1ec:c11::200: time=86ms Reply from 2620:1ec:c11::200: time=271ms Ping statistics for 2620:1ec:c11::200: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 51ms, Maximum = 470ms, Average = 229ms C:\>ping bing.com -4 -t Pinging bing.com [13.107.21.200] with 32 bytes of data: Reply from 13.107.21.200: bytes=32 time=301ms TTL=115 Reply from 13.107.21.200: bytes=32 time=195ms TTL=115 Reply from 13.107.21.200: bytes=32 time=182ms TTL=115 Reply from 13.107.21.200: bytes=32 time=79ms TTL=115 Reply from 13.107.21.200: bytes=32 time=265ms TTL=115 Reply from 13.107.21.200: bytes=32 time=472ms TTL=115 Reply from 13.107.21.200: bytes=32 time=473ms TTL=115 Reply from 13.107.21.200: bytes=32 time=475ms TTL=115 Reply from 13.107.21.200: bytes=32 time=159ms TTL=115 Reply from 13.107.21.200: bytes=32 time=72ms TTL=115 Reply from 13.107.21.200: bytes=32 time=362ms TTL=115 Reply from 13.107.21.200: bytes=32 time=257ms TTL=115 Reply from 13.107.21.200: bytes=32 time=49ms TTL=115 Reply from 13.107.21.200: bytes=32 time=69ms TTL=115 Reply from 13.107.21.200: bytes=32 time=170ms TTL=115 Reply from 13.107.21.200: bytes=32 time=53ms TTL=115 Reply from 13.107.21.200: bytes=32 time=57ms TTL=115 Reply from 13.107.21.200: bytes=32 time=56ms TTL=115 Reply from 13.107.21.200: bytes=32 time=57ms TTL=115 Reply from 13.107.21.200: bytes=32 time=133ms TTL=115 Reply from 13.107.21.200: bytes=32 time=873ms TTL=115 Reply from 13.107.21.200: bytes=32 time=242ms TTL=115 Reply from 13.107.21.200: bytes=32 time=124ms TTL=115 Ping statistics for 13.107.21.200: Packets: Sent = 23, Received = 23, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 49ms, Maximum = 873ms, Average = 225ms In the past, I was using the 5G cylinder router but due to it trying to use a further 3-mile away 5G router tower than a closer 1-mile away 4G tower, I switched to the 4G router. I was having horrible experience like I am now with the 3-mile away tower. The closer tower has been having "maintenance" done to it and the further 3-mile away tower has been "having issues". This is a reason I have not gone back to the 5G router. The service is just c___ now. By the way, here's a strange experience I had when using a Cisco router with IP passthrough on a LTE gateway to T-Mobile: web.archive.org I rely on T-Mobile Home Internet for work and this is causing me to not do my job and could affect my livelihood. I'm sure this is fine to some people there at T-Mobile screwing things up or not implementing things properly and not thinking twice. Is there a way to open a case with T-Mobile online? T-Mobile Support in Taiwan or USA seems to treat this like " that's it, take it or leave it" customer service like a fast-food place rather than an important utility that should be providing an effective, and responsivecustomer service. At some point, T-Mobile isn't worth it anymore. -Jason