Jump to content

Recommended Posts

Traceroute is a useful tool that can give insight into the topology and geography of the network between your device and a remote webpage, host, etc. It also shows the raw latency (ping) between your device and the first hop TCP/IP router on the network. Whereas sites like speedtest show the ping between your device and their server in who-knows-where.


Let's post our traceroutes from our Sprint devices to some common mobile websites (m.google.com, m.yahoo.com) and see how they compare in various parts of the country. I did two traceroutes while on LTE from my iPhone, one to Google and one to Yahoo. Be sure you disable Wi-fi before you do the traceroute. I used a cheap app called IT Tools ($0.99) to do the traceroute on my iPhone 5. But there are free ones available.


For consistency purposes, I recommend you traceroute directly to the same IP addresses my traceroutes used, since various parts of the country may use DNS to resolve target IP addresses in a different geographical location.


I'm in Austin, TX. My phone's IP address according to its interface table is 51.127.74.x and according to www.whatismyip.com it is I'm about 1000 feet from my tower with my iPhone's signal strength showing -82 (aka 4 or 5ish "bars")


google - 9 iterations

traceroute to m.google.com (, 64 hops max, 56 byte packets
1  sent:9 loss:0% last:30.132 ms avg:30.148 ms
2  sent:9 loss:0% last:31.378 ms avg:33.102 ms
3  sent:9 loss:0% last:31.671 ms avg:35.49 ms
4  sent:9 loss:44.4% last:39.579 ms avg:37.77 ms
5  sent:9 loss:0% last:37.74 ms avg:36.324 ms
6  sent:9 loss:0% last:34.538 ms avg:57.248 ms
sl-crs3-fw-.sprintlink.net (
7  sent:9 loss:0% last:35.364 ms avg:38.376 ms
8  sent:9 loss:0% last:92.194 ms avg:45.749 ms
9  sent:9 loss:0% last:35.156 ms avg:43.811 ms
10  sent:9 loss:0% last:38.256 ms avg:48.43 ms
11  sent:9 loss:0% last:59.839 ms avg:58.647 ms
12  sent:8 loss:0% last:60.326 ms avg:63.575 ms
13  sent:8 loss:100% last:0 ms avg:0 ms
14  sent:8 loss:0% last:58.614 ms avg:67.883 ms
ye-in-f193.1e100.net (

yahoo - 32 iterations

traceroute to m.yahoo.com (, 64 hops max, 56 byte packets
1  sent:33 loss:0% last:32.607 ms avg:39.101 ms
2  sent:33 loss:0% last:29.243 ms avg:33.093 ms
3  sent:33 loss:0% last:38.868 ms avg:35.506 ms
4  sent:33 loss:12.1% last:38.542 ms avg:40.582 ms
5  sent:33 loss:0% last:35.382 ms avg:36.152 ms
6  sent:33 loss:0% last:38.624 ms avg:40.726 ms
sl-crs3-fw-.sprintlink.net (
7  sent:33 loss:0% last:42.728 ms avg:48.217 ms
8  sent:32 loss:0% last:36.135 ms avg:43.818 ms
9  sent:32 loss:0% last:95.774 ms avg:44.656 ms
ae-4-90.edge3.dallas1.level3.net (
10  sent:32 loss:0% last:40.504 ms avg:40.655 ms
yahoo-inc.edge3.dallas1.level3.net (
11  sent:32 loss:0% last:40.661 ms avg:43.8 ms
ae-2-d131.msr2.mud.yahoo.com (
ae-1-d131.msr2.mud.yahoo.com (
ae-1-d121.msr1.mud.yahoo.com (
ae-2-d121.msr1.mud.yahoo.com (
12  sent:32 loss:0% last:42.541 ms avg:40.765 ms
te-7-1.fab1-a-gdc.mud.yahoo.com (
te-7-2.fab1-a-gdc.mud.yahoo.com (
te-6-2.fab2-a-gdc.mud.yahoo.com (
te-7-1.fab2-a-gdc.mud.yahoo.com (
13  sent:32 loss:0% last:35.663 ms avg:39.504 ms
unknown-66-94-233-x.yahoo.com (
unknown-66-94-233-x.yahoo.com (
14  sent:32 loss:0% last:36.077 ms avg:41.989 ms
r4.ycpi.vip.mud.yahoo.net (

Share this post

Link to post
Share on other sites

Should I link to my mid-July traceroutes from my LTE testing in Fort Worth? :)

Share this post

Link to post
Share on other sites

A couple miles west of Fredericksburg, TX, tethering my GSIII via TrevEMod AndroidWiFiTether because Sprint's OLAM is being stupid...and it looks like speeds are higher this way...



traceroute to s4gru.com (, 64 hops max, 52 byte packets
1  [AS28513] (  4.167 ms  1.846 ms  2.129 ms
2  [AS65534] (  50.875 ms  34.345 ms  46.806 ms
3  [AS65534] (  43.913 ms
[AS65534] (  49.793 ms
[AS65534] (  52.192 ms
4  [AS65534] (  42.398 ms
[AS65534] (  44.164 ms
[AS65534] (  39.241 ms
5  [AS65534] (  39.823 ms  63.242 ms  52.672 ms
6  [AS65534] (  35.919 ms  35.550 ms  39.924 ms
7  [AS0] (  41.845 ms  42.870 ms
[AS0] (  50.677 ms
8  [AS0] sl-crs2-hou-.sprintlink.net (  42.346 ms
[AS0] sl-crs1-hou-.sprintlink.net (  37.490 ms  48.543 ms
9  [AS0] (  48.789 ms
[AS0] sl-crs2-fw-0-2-0-2.sprintlink.net (  72.051 ms
[AS0] sl-crs1-fw-0-1-5-0.sprintlink.net (  67.240 ms
10  [AS0] (  67.710 ms
[AS0] (  51.135 ms  58.573 ms
11  [AS0] (  60.801 ms
[AS0] (  54.022 ms
[AS0] (  53.121 ms
12  [AS0] (  55.290 ms  68.947 ms  57.474 ms
13  [AS0] dpr1-ge-2-0-0.dallasequinix.savvis.net (  63.899 ms  61.480 ms  59.512 ms
14  [AS0] cr2-tengige0-7-5-0.dallas.savvis.net (  61.961 ms  46.656 ms  58.797 ms
15  [AS0] cr1-te-0-2-0-0.chd.savvis.net (  88.542 ms  91.825 ms  87.293 ms
16  [AS0] ber1-te-1-0-0.chicagoequinix.savvis.net (  80.591 ms  80.942 ms  93.828 ms
17  [AS0] (  80.569 ms  83.858 ms  97.191 ms
18  [AS32244] lw-dc2-core4-te9-1.rtr.liquidweb.com (  89.894 ms  94.465 ms  97.009 ms
19  [AS32244] lw-dc3-dist14.rtr.liquidweb.com (  99.734 ms  97.869 ms  91.643 ms
20  [AS32244] (  93.749 ms  91.852 ms  90.531 ms
21  * * *
22  * *^C


traceroute to (, 64 hops max, 52 byte packets
1  [AS28513] (  4.722 ms  3.972 ms  1.862 ms
2  [AS65534] (  35.168 ms  38.359 ms  39.909 ms
3  [AS65534] (  42.348 ms
[AS65534] (  46.816 ms
[AS65534] (  40.877 ms
4  [AS65534] (  42.017 ms
[AS65534] (  40.798 ms
[AS65534] (  36.112 ms
5  [AS65534] (  39.102 ms  41.974 ms  39.713 ms
6  [AS65534] (  40.528 ms  41.669 ms  53.557 ms
7  [AS0] (  47.445 ms  41.084 ms  53.205 ms
8  [AS0] sl-crs2-hou-.sprintlink.net (  39.006 ms
[AS0] sl-crs1-hou-.sprintlink.net (  40.542 ms
[AS0] sl-crs2-hou-.sprintlink.net (  42.086 ms
9  [AS0] sl-crs2-fw-0-1-5-0.sprintlink.net (  48.446 ms
[AS0] sl-crs2-fw-0-2-0-2.sprintlink.net (  58.324 ms
[AS0] sl-crs1-fw-0-1-5-0.sprintlink.net (  59.018 ms
10  [AS0] (  60.653 ms  48.780 ms
[AS0] (  57.875 ms
11  [AS0] (  53.208 ms
[AS0] (  58.633 ms  79.378 ms
12  [AS0] (  73.200 ms  63.148 ms  52.022 ms
13  [AS3356] ae-1-60.edge3.dallas1.level3.net (  61.298 ms
[AS3356] ae-2-70.edge3.dallas1.level3.net (  58.679 ms  53.319 ms
14  [AS3356] d.resolvers.level3.net (  54.696 ms  56.860 ms  45.587 ms


1  [AS28513] (  4.305 ms  3.578 ms  1.820 ms
2  [AS65534] (  33.945 ms  45.723 ms  42.071 ms
3  [AS65534] (  41.034 ms
[AS65534] (  43.722 ms
[AS65534] (  38.017 ms
4  [AS65534] (  37.707 ms
[AS65534] (  45.018 ms
[AS65534] (  37.840 ms
5  [AS65534] (  36.075 ms  44.898 ms  39.840 ms
6  [AS65534] (  39.559 ms  45.893 ms  40.377 ms
7  [AS0] (  41.466 ms  37.829 ms
[AS0] (  54.308 ms
8  [AS0] sl-crs1-hou-.sprintlink.net (  45.677 ms
[AS0] sl-crs2-hou-.sprintlink.net (  49.360 ms
[AS0] sl-crs1-hou-.sprintlink.net (  37.678 ms
9  [AS0] sl-crs1-fw-0-1-5-0.sprintlink.net (  67.391 ms
[AS0] (  51.198 ms
[AS0] sl-crs2-fw-0-14-0-0.sprintlink.net (  70.877 ms
10  [AS0] (  52.153 ms
[AS0] (  45.431 ms
[AS0] (  46.746 ms
11  [AS0] (  56.755 ms
[AS0] (  66.894 ms
[AS0] (  51.534 ms
12  [AS0] (  59.556 ms
[AS0] (  46.053 ms
[AS0] (  64.612 ms
13  [AS3356] softlayer-t.edge2.dallas3.level3.net (  65.248 ms  57.269 ms  53.896 ms
14  [AS36351] ae5.dar02.sr01.dal05.networklayer.com (  52.430 ms  66.318 ms  70.729 ms
15  * * *
16  [AS36351] speedtest.dal05.softlayer.com (  168.132 ms  45.851 ms  57.905 ms


I can't find a site that I can trace to in Houston that doesn't double back to Dallas first...guess Sprint doesn't have many corporate customers in HOU anymore.


The connection looks quite jittery from the traceroutes, but it's incedibly usable, especially considering that it's over 10x faster on downloads than my parents' DSL connection (Verizon, 1.5M down, 384k up...it's all we can get this far out) and over 20x faster on uploads.

Share this post

Link to post
Share on other sites

The hosts you traced to make a lot more sense, iansltx.



traceroute to (, 64 hops max, 56 byte packets
1  sent:26 loss:7.7% last:32.178 ms avg:90.284 ms
2  sent:26 loss:7.7% last:37.712 ms avg:92.992 ms
3  sent:26 loss:7.7% last:35.104 ms avg:75.598 ms
4  sent:26 loss:7.7% last:42.629 ms avg:74.587 ms
5  sent:26 loss:11.5% last:39.756 ms avg:69.021 ms
6  sent:26 loss:11.5% last:35.785 ms avg:56.32 ms
7  sent:26 loss:11.5% last:42.332 ms avg:51.125 ms
sl-crs2-hou-.sprintlink.net (
sl-crs1-hou-.sprintlink.net (
8  sent:26 loss:11.5% last:50.096 ms avg:62.911 ms
sl-crs2-fw-0-2-0-2.sprintlink.net (
sl-crs1-fw-0-14-0-0.sprintlink.net (
9  sent:26 loss:7.7% last:53.249 ms avg:134.595 ms
10  sent:26 loss:7.7% last:54.753 ms avg:127.473 ms
11  sent:26 loss:7.7% last:52.784 ms avg:131.694 ms
12  sent:26 loss:7.7% last:57.668 ms avg:122.757 ms
ae-3-80.edge3.dallas1.level3.net (
13  sent:25 loss:8% last:48.203 ms avg:110.48 ms
d.resolvers.level3.net (

traceroute to s4gru.com (, 64 hops max, 56 byte packets
1  sent:12 loss:0% last:29.375 ms avg:47.102 ms
2  sent:12 loss:0% last:41.331 ms avg:37.179 ms
3  sent:12 loss:0% last:33.418 ms avg:33.888 ms
4  sent:12 loss:0% last:34.147 ms avg:35.711 ms
5  sent:12 loss:25% last:35.242 ms avg:36.503 ms
6  sent:12 loss:0% last:36.355 ms avg:39.449 ms
7  sent:12 loss:0% last:36.511 ms avg:39.858 ms
sl-crs1-hou-.sprintlink.net (
sl-crs2-hou-.sprintlink.net (
8  sent:12 loss:0% last:44.639 ms avg:47.024 ms
sl-crs1-fw-0-12-0-2.sprintlink.net (
sl-crs2-fw-0-14-0-0.sprintlink.net (
9  sent:12 loss:0% last:45.044 ms avg:44.366 ms
10  sent:12 loss:0% last:50.26 ms avg:75.652 ms
11  sent:12 loss:0% last:49.303 ms avg:59.087 ms
12  sent:12 loss:0% last:45.957 ms avg:66.884 ms
pr2-ge-7-0-0.daq.savvis.net (
13  sent:12 loss:0% last:46.693 ms avg:48.858 ms
cr1-tengig0-7-5-0.dallas.savvis.net (
14  sent:12 loss:0% last:78.524 ms avg:77.645 ms
cr1-te-0-2-0-0.chd.savvis.net (
15  sent:12 loss:0% last:78.174 ms avg:88.009 ms
ber1-te-4-4.chq.savvis.net (
16  sent:12 loss:0% last:81.439 ms avg:86.484 ms
17  sent:12 loss:0% last:86.295 ms avg:83.565 ms
lw-dc2-core4-te9-1.rtr.liquidweb.com (
18  sent:11 loss:0% last:91.221 ms avg:97.959 ms
lw-dc3-dist14.rtr.liquidweb.com (
19  sent:11 loss:0% last:76.717 ms avg:79.174 ms
20  sent:11 loss:0% last:95.785 ms avg:101.264 ms
ap04.lw.ipslink.com (

Share this post

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • large.unreadcontent.png.6ef00db54e758d06

  • gallery_1_23_9202.png

  • Similar Content

    • By vanko987
      I'm new to this forum, and I've seen people mention cell sites with specific ID's (for example, SF33XC664). Is there any significance to these ID's, and is there a way to decode them? Also, how do I figure out what the cell site ID's are for towers near me?
      Thanks! I'm excited to start talking on this site more 😀
    • By Paynefanbro
      I figured since Verizon's 5G-NR network officially launched it would make sense for there to be a thread for it.
    • By EntrepreneurKid
      With Todays announcement that T-Mobile and Sprint are merging, and the announcement of the T-Mobile Sprint Roaming deal that will survive and will last for four years regardless if the merger is completed or not, which is effect immediately as stated in the conference call and the slides made available. So I thought I'd create this to see if anyone has been able to use their Sprint device on T-Mobile roaming yet. And of course if not, once you do, come back here and say you have. Personally I'm not bothering with anything until after the coverage map is updated again, hopefully to reflect the T-Mobile roaming. And of course if you are able to roam onto T-Mobile what kind of speeds are you pulling, and on what device.
      Also for those that are unaware, the T-Mobile Sprint Roaming agreement that was announced as part of todays merger announcement is a roaming agreement for Sprint customers to roam onto T-Mobile for 4 years and takes affect immediately, yes right now, regardless if the merger completes or not. Surely it's a stepping stone to integrating the networks by getting Sprint devices that are capable, which according to the conference call is 20 Million Sprint devices ready to be used on the T-Mobile network full time once deal is approved by the regulators and finally completed.
    • By danlodish345
      hello everyone i m starting a thread for sprint network predictions for 2018. i am wishing sprint and s4gru a happy holidays and new years. 
      regards Daniel
    • By EntrepreneurKid
      I'm here looking for answers to a simple question. Where is this mystery Sprint signal coming from? For the past few weeks I've received a signal on multiple Sprint devices, two Sprint devices with roaming turned off, and two Virgin Mobile phones and Virgin Mobile phones can't roam, the other rate plans might be able but I'm talk about Virgin Mobile devices from before they introduced all those other plans. What I'm making clear is these devices have to be picking up a Sprint signal, plus I've downloaded the SignalCheck Pro app which has indicated two different signals 1XRTT and 1X800. 
      The signal only last for about 8 hours each morning and begins coming in and out towards the end of each morning. I try making a call and it fails, and it doesn't get any data at all. I try each device and they all do the same thing they have a signal and very strong signal with no data, and voice doesn't go threw, I haven't tried sending a text figured no data, no voice then there must be no text.
      I read about some "projects"  that Sprint has going on Project Ocean and Project Cedar. Since Project Ocean is suppose to be taking place in Missouri and I live so close to the Iowa, Missouri line, I figured if there is a tower going up maybe it is possible I'm getting a signal from it, in the early stages. I really don't know what is going on, if Sprint is launching service, putting up new towers and that signal finally comes, and stays, and works. I'll be back full time on the Sprint ban wagon. Unfortunately, I live in an area not served by (according to experience and coverage map) Verizon, AT&T, T-Mobile and Sprint. Not even the two Iowa carriers i Wireless or Chat Mobility serve my area, go 10, 15 or 20 miles in any direction your good, here, wireless dead zone, no choice of carriers. And if Sprint puts a tower here if I finally get an answer and learn that signal will soon come and stay and work I'll finally have a choice.
      So if anyone has any ideas, has experienced this in other parts of the country or has any idea what could be going on please say. Any information is better than not knowing, and together maybe this will be answered.
  • Posts

  • Recently Browsing

    No registered users viewing this page.

  • Create New...