Forum Discussion

jasoncal84's avatar
jasoncal84
Roaming Rookie
Hace 3 años

T-Mobile Home Internet infuriating, atrocious, and aggravating

Hola 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 | Comunidad de T-Mobile I 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 DNS servers 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 4G TM-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 responsive customer service. At some point, T-Mobile isn’t worth it anymore.

-Jason

 

  • Mapeebs's avatar
    Mapeebs
    Network Novice

    I am experiencing horrible buffering. At 2:00 AM the download is 200.+. But in the normal usage hours, it is .5 or less. Trying to watch TV is so frustrating and watching a football game?-forget that. I have dealt with customer service so many times in the last month. If I can get a rep who I can understand (i.e. English is their fourth language) I get constant run-around. First, "just give it time"; next, "Theres a problem at the tower"; next, we will replace the gateway; next "Hmmm". Finally, "there's a problem with the tower."  None of this solves my problem. How do I escalate this??? Ive tried being polite, but my polite is wearing thin!  Please know, I am the opposite of a techie!  I don't understand all the numbers…I just want something that works! Can't use IPhone, doorbell doesn't transmit, it's like living in the 50's. Lord, I don't want to go back to Spectrum or Frontier

  • Cali_Cat's avatar
    Cali_Cat
    Bandwidth Buddy
    Ali YUSUF wrote:

    I don't want internet line I have asked you several times to Delete from my Account, but you have not deleted it from me.  I took it home and returned it, not used but I can see the Cash value of $71 in my Account.  delete my Account again.

    Nobody in this community forum can delete your account. You can only call TMO support directly to cancel service and delete your account. 

  • Ali_YUSUF's avatar
    Ali_YUSUF
    Network Novice

    I don't want internet line I have asked you several times to Delete from my Account, but you have not deleted it from me.  I took it home and returned it, not used but I can see the Cash value of $71 in my Account.  delete my Account again.

  • tomwil wrote:
    jasoncal84 wrote:

    I rely on T-Mobile Home Internet for work and this is causing me to not do my job and could affect my livelihood.

     

    T-Mobile Home Internet probably works fine for 90% of subscribers, but for the other 10% that are more advanced or dependent on jobs, T-Mobile is probably not the best choice.

     

    T-Mobile Home Internet is a new technology, not fully developed like cable or other internet suppliers.  It is especially hampered by having the lowest data priority on its cellular system, which it has to share with phones and other higher priority devices.

     

    If your job depends on the internet, don’t go cheap, spend a little more and get a more mature technological solution like cable.

     

    What an excellent way to insult the intelligence of people trying to get answers for their ISP questions on the ISP forum of the ISP. Tell them to spend a little more and get cable. I bet 95+% of the people who are on T-Mobile Home Internet are on it because they don't have cable or fiber available to them. 

  • Hola,

    Maybe I'm now on the screw you routing. It's where they make your experience terrible so you will just leave. Here's a traceroute to bing.com

    tracert 13.107.21.200

    Tracing route to 13.107.21.200 over a maximum of 30 hops

      1     2 ms     1 ms     1 ms  RT-AX3000-67E8.local [192.168.50.1]
      2  1160 ms     *      300 ms  10.21.0.1
      3  1165 ms  1577 ms   958 ms  37.120.244.49
      4  1557 ms     *      309 ms  193.27.15.164
      5  1289 ms  1889 ms  1302 ms  de-cix.nyc.microsoft.com [206.82.104.133]
      6     *        *        *     Request timed out.
      7  1924 ms   956 ms   768 ms  13.104.141.210
      8     *        *        *     Request timed out.
      9     *        *        *     Request timed out.
     10     *        *        *     Request timed out.
     11   954 ms  1225 ms     *     13.107.21.200
     12   925 ms   493 ms     *     13.107.21.200
     13   490 ms  1137 ms  1254 ms  13.107.21.200

    Trace complete.

    That could be why my IPv4 went downhill followed recently by IPv6. They were still perfecting their "new technology" and got it finely tuned now. 

    -Jason

  • Hola,

     

    Maybe they configured me to be on the FU routing… where they make your latency high to infuriate you off to get rid of you and make way for other customers:

     

    tracert 13.107.21.200

    Tracing route to 13.107.21.200 over a maximum of 30 hops

      1     2 ms     1 ms     1 ms  RT-AX3000-67E8.local [192.168.50.1]
      2  1160 ms     *      300 ms  10.21.0.1
      3  1165 ms  1577 ms   958 ms  37.120.244.49
      4  1557 ms     *      309 ms  193.27.15.164
      5  1289 ms  1889 ms  1302 ms  de-cix.nyc.microsoft.com [206.82.104.133]
      6     *        *        *     Request timed out.
      7  1924 ms   956 ms   768 ms  13.104.141.210
      8     *        *        *     Request timed out.
      9     *        *        *     Request timed out.
     10     *        *        *     Request timed out.
     11   954 ms  1225 ms     *     13.107.21.200
     12   925 ms   493 ms     *     13.107.21.200
     13   490 ms  1137 ms  1254 ms  13.107.21.200

    Trace complete.

     

    Maybe that could explain why IPv4 when downhill followed then by IPv6. They just didn't figure out how to F UP my IPv6 yet. 

    -Jason

  • tomwil's avatar
    tomwil
    Bandwidth Buff
    jasoncal84 wrote:

    I rely on T-Mobile Home Internet for work and this is causing me to not do my job and could affect my livelihood.

     

    T-Mobile Home Internet probably works fine for 90% of subscribers, but for the other 10% that are more advanced or dependent on jobs, T-Mobile is probably not the best choice.

     

    T-Mobile Home Internet is a new technology, not fully developed like cable or other internet suppliers.  It is especially hampered by having the lowest data priority on its cellular system, which it has to share with phones and other higher priority devices.

     

    If your job depends on the internet, don’t go cheap, spend a little more and get a more mature technological solution like cable.

     

  • I talked with T-Mobile customer service, they actually alluded to exploring no longer using them. It's as if they want to not have to deal with me and the problems in their networks than restore their networks to good working no BS working condition. They said they will follow-up next Sunday.