Belong Mobile Long Traceroute to Los Angeles and More!

Just joined belong mobile from Boost Mobile and I am shocked at the long traceroute's and speed. It takes a crazy traceroute to Los Angeles over 300ms return trip.

I'm on 5G with them full bars, Speedtest is 100mbps locally.

A simple ping to google.com should be around 30ms or less but they're 100ms.

Anyone else feeling this?

Related Stores

Belong
Belong

Comments

  • DNS?

    • What would dns have to do with it?

    • DNS does not affect the way you get the website

      • I'm on 5G with them full bars

        like this will

        300ms to LA isn't that bad? It should be around 200ms.

        I would be more interested in your tracert for 1.1.1.1

    • +2

      Do Not Signup?

  • Google.com is an anycast address so when you ping it from Australia you the Australian service (not one in the USA)

    • Cloudflare is even worse, ICMP is not de prioritised, as NBN connection its less that 2ms.

      PING 1.1.1.1 (1.1.1.1): 56 data bytes
      64 bytes from 1.1.1.1: icmp_seq=0 ttl=55 time=96.632 ms
      64 bytes from 1.1.1.1: icmp_seq=1 ttl=55 time=141.561 ms
      64 bytes from 1.1.1.1: icmp_seq=2 ttl=55 time=495.368 ms
      64 bytes from 1.1.1.1: icmp_seq=3 ttl=55 time=225.654 ms
      64 bytes from 1.1.1.1: icmp_seq=4 ttl=55 time=121.587 ms

  • 5G is NOT suitable for gaming.

    Downloading of files or streaming should be okay once the connection is established as packets (assuming a network sliding window app is used).

    Speed will be crap under a bunch of conditions on 5G compared to 4G and even then both can be crap if there is a problem with the tower or the band being used on the tower.

    • +1

      this is crazy though

      traceroute to fiber9.iaasdns.com (173.82.65.242), 64 hops max, 52 byte packets
      1 172.20.10.1 (172.20.10.1) 5.693 ms 4.201 ms 4.267 ms
      2 10.3.67.148 (10.3.67.148) 106.695 ms 400.961 ms 244.004 ms
      3 10.3.67.146 (10.3.67.146) 21.896 ms 17.211 ms 20.565 ms
      4 10.5.135.1 (10.5.135.1) 20.225 ms 17.843 ms 19.901 ms
      5 10.5.135.8 (10.5.135.8) 20.355 ms 19.226 ms 18.937 ms
      6 203.50.63.8 (203.50.63.8) 19.989 ms 22.108 ms 30.024 ms
      7 bundle-ether25.cha-core10.brisbane.telstra.net (203.50.61.0) 22.788 ms 19.061 ms 18.890 ms
      8 203.50.13.157 (203.50.13.157) 35.821 ms 33.985 ms 35.929 ms
      9 bundle-ether19.ken-core10.sydney.telstra.net (203.50.13.146) 43.846 ms 43.963 ms 36.705 ms
      10 bundle-ether1.pad-gw11.sydney.telstra.net (203.50.6.61) 34.533 ms 34.839 ms 33.853 ms
      11 203.50.13.90 (203.50.13.90) 37.043 ms 34.193 ms 40.062 ms
      12 203.50.13.90 (203.50.13.90) 414.431 ms 312.385 ms 813.650 ms
      13 i-20802.eqnx-core02.telstraglobal.net (202.84.141.25) 194.819 ms 496.726 ms 221.491 ms
      14 i-92.eqnx03.telstraglobal.net (202.84.247.17) 311.844 ms 355.795 ms 251.848 ms
      15 4.68.68.125 (4.68.68.125) 180.382 ms 462.953 ms 307.923 ms
      16 ae1.3505.edge9.sanjose1.level3.net (4.69.219.61) 311.891 ms
      ae2.3605.edge9.sanjose1.level3.net (4.69.219.65) 501.746 ms *
      17 lumen-level3-sanjose1.level3.net (4.68.110.178) 331.504 ms 318.371 ms 361.652 ms
      18 los-edge-07.inet.qwest.net (67.14.102.146) 269.733 ms 538.696 ms 250.872 ms
      19 65.153.29.222 (65.153.29.222) 365.727 ms 305.364 ms 287.967 ms
      20 nx1.multacom.com (96.45.162.10) 323.190 ms 222.071 ms 324.711 ms

  • *adjusts tinfoil hat

    Pine Gap

    • lol

  • Any vpn to speak off?

    Here's mine, belong 4g on home router, using desktop. Average ping time 29ms
    Tracert to google.com

    1 local router ip
    2 local router ip
    3 * * * Request timed out.
    4 32 ms 28 ms 28 ms 10.4.74.66
    5 19 ms 14 ms 18 ms 10.3.211.65
    6 23 ms 16 ms 18 ms 10.3.211.72
    7 42 ms 30 ms 35 ms 203.50.63.144
    8 27 ms 59 ms 16 ms ae20-20.exi-ice302.melbourne.telstra.net [203.50.61.162]
    9 16 ms 19 ms 18 ms bundle-ether26.exi-core30.melbourne.telstra.net [203.50.61.160]
    10 17 ms 59 ms 17 ms bundle-ether1.lon-edge903.melbourne.telstra.net [203.50.11.199]
    11 38 ms 27 ms 28 ms 142.250.162.46
    12 26 ms 21 ms 19 ms 142.250.234.219
    13 16 ms 20 ms 19 ms 216.239.59.109
    14 18 ms 26 ms 20 ms mel05s02-in-f14.1e100.net [142.250.70.238]

    • its more international issues. Local ping issues seem to be the tower im connected to, running it a little later tonight is better

      traceroute to google.com (172.217.167.110), 64 hops max, 52 byte packets
      1 172.20.10.1 (172.20.10.1) 5.148 ms 4.524 ms 4.420 ms
      2 10.4.96.4 (10.4.96.4) 145.328 ms 144.114 ms 223.769 ms
      3 10.4.96.2 (10.4.96.2) 23.594 ms 27.418 ms 17.471 ms
      4 10.5.135.1 (10.5.135.1) 18.592 ms 18.232 ms 23.728 ms
      5 10.5.135.8 (10.5.135.8) 17.328 ms 19.978 ms 22.931 ms
      6 203.50.63.8 (203.50.63.8) 15.751 ms 19.913 ms 18.857 ms
      7 bundle-ether25.cha-core10.brisbane.telstra.net (203.50.61.0) 273.266 ms 20.945 ms 20.477 ms
      8 203.50.13.157 (203.50.13.157) 33.376 ms 34.436 ms 146.646 ms
      9 bundle-ether1.ken-edge903.sydney.telstra.net (203.50.11.173) 32.125 ms 32.147 ms 34.480 ms
      10 72.14.212.22 (72.14.212.22) 35.860 ms
      goo2503144.lnk.telstra.net (58.163.91.202) 164.260 ms 35.899 ms
      11 108.170.247.33 (108.170.247.33) 43.450 ms * *
      12 209.85.253.177 (209.85.253.177) 138.142 ms 33.616 ms
      142.251.64.178 (142.251.64.178) 35.858 ms
      13 syd09s17-in-f14.1e100.net (172.217.167.110) 48.534 ms
      209.85.253.181 (209.85.253.181) 32.368 ms
      syd09s17-in-f14.1e100.net (172.217.167.110) 39.491 ms

  • oh no!

    So what impact is this having on your life exactly?

Login or Join to leave a comment