TraceRt issue

[JR]

TCP/IP novice here. I am having very slow access between my desktop
Windows PC and our hosted web site. I ran tracert (for Windows), as
requested by my hosting site support. I sent them the output and they
blame sprintlink.

I do not understand the output of tracert or traceroute. If it were
just me having the problem, I wouldn't mind so much. However, a number
of our customers around the U.S. are having the same complaint. I'm
only getting 20KB/sec for file transfers when I normally get 300+.

Below is the trace. Is sprintlink an issue or is oneandone (our web
hoster) the problem? I appreciate any insight on this.

Tracing route to 74.208.34.120 over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 10.202.46.1
2 13 ms 8 ms 8 ms 66.60.130.170
3 9 ms 11 ms 7 ms 66.60.130.190
4 * 8 ms 8 ms 66.60.130.198
5 15 ms 13 ms 15 ms 65.170.194.65
6 14 ms 19 ms 13 ms sl-bb21-stk-11-2.sprintlink.net
[144.232.20.18]
7 85 ms 89 ms 85 ms sl-bb26-pen-12-0.sprintlink.net
[144.232.20.162]
8 86 ms 86 ms 86 ms sl-bb21-nyc-11-0-0.sprintlink.net
[144.232.20.143]
9 * 101 ms * sl-bb23-nyc-3-0.sprintlink.net
[144.232.7.109]
10 87 ms 87 ms 86 ms sl-gw30-nyc-1-0.sprintlink.net
[144.232.13.24]
11 121 ms 123 ms 121 ms sl-schlu4-2-0.sprintlink.net
[144.232.230.250]
12 86 ms 108 ms 86 ms vl-402.gw-core-b.nyc.oneandone.net
[217.160.229.105]
13 93 ms 93 ms 92 ms ge-3-1.bb-b.ms.mkc.us.oneandone.net
[212.227.120.230]
14 93 ms 93 ms 93 ms te-2-2.bb-b.hs.mkc.us.oneandone.net
[74.208.1.86]
15 98 ms 97 ms 98 ms te-2-1.bb-b.slr.lxa.us.oneandone.net
[74.208.1.90]
16 97 ms 101 ms 97 ms te-1-1.gw-dists-r5-
a.slr.lxa.oneandone.net [74.208.1.99]
17 100 ms 100 ms 101 ms vl-987.gw-ps1.slr.lxa.oneandone.net
[74.208.1.133]
18 * 96 ms 100 ms 74.208.34.120

Trace complete.

 

[Guest]

Hi JR,

Your tracert points to a problem with Sprint link. I've included the
tracert from my shop for a comparison. I get excellent response from your
server.


5 4 ms 4 ms 4 ms owb.br03.g5-2.americanis.net [206.251.233.66]
6 5 ms 5 ms 5 ms bur-edge-04.inet.qwest.net [63.149.192.185]
7 6 ms 5 ms 5 ms bur-core-02.inet.qwest.net [205.171.13.57]
8 5 ms 5 ms 6 ms lap-brdr-02.inet.qwest.net [205.171.213.50]
9 16 ms 15 ms 16 ms 63.146.26.78
10 50 ms 50 ms 51 ms 64.209.102.178
11 49 ms 49 ms 49 ms te-2-2.bb-b.hs.mkc.us.oneandone.net
[74.208.1.86]
12 52 ms 50 ms 50 ms te-2-1.bb-b.slr.lxa.us.oneandone.net
[74.208.1.90]
13 50 ms 49 ms 49 ms te-1-2.gw-dists-r5-a.slr.lxa.oneandone.net
[74.208.1.115]
14 51 ms 50 ms 49 ms vl-987.gw-ps1.slr.lxa.oneandone.net
[74.208.1.133]
15 50 ms 49 ms 49 ms hhtackshop.com [74.208.34.120]

Try using www.dnsstuff.com to run a trace route from a remote location.

John Cutsinger
Altegris Investments

TCP/IP novice here. I am having very slow access between my desktop
Windows PC and our hosted web site. I ran tracert (for Windows), as
requested by my hosting site support. I sent them the output and they
blame sprintlink.

I do not understand the output of tracert or traceroute. If it were
just me having the problem, I wouldn't mind so much. However, a number
of our customers around the U.S. are having the same complaint. I'm
only getting 20KB/sec for file transfers when I normally get 300+.

Below is the trace. Is sprintlink an issue or is oneandone (our web
hoster) the problem? I appreciate any insight on this.

Tracing route to 74.208.34.120 over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 10.202.46.1
2 13 ms 8 ms 8 ms 66.60.130.170
3 9 ms 11 ms 7 ms 66.60.130.190
4 * 8 ms 8 ms 66.60.130.198
5 15 ms 13 ms 15 ms 65.170.194.65
6 14 ms 19 ms 13 ms sl-bb21-stk-11-2.sprintlink.net
[144.232.20.18]
7 85 ms 89 ms 85 ms sl-bb26-pen-12-0.sprintlink.net
[144.232.20.162]
8 86 ms 86 ms 86 ms sl-bb21-nyc-11-0-0.sprintlink.net
[144.232.20.143]
9 * 101 ms * sl-bb23-nyc-3-0.sprintlink.net
[144.232.7.109]
10 87 ms 87 ms 86 ms sl-gw30-nyc-1-0.sprintlink.net
[144.232.13.24]
11 121 ms 123 ms 121 ms sl-schlu4-2-0.sprintlink.net
[144.232.230.250]
12 86 ms 108 ms 86 ms vl-402.gw-core-b.nyc.oneandone.net
[217.160.229.105]
13 93 ms 93 ms 92 ms ge-3-1.bb-b.ms.mkc.us.oneandone.net
[212.227.120.230]
14 93 ms 93 ms 93 ms te-2-2.bb-b.hs.mkc.us.oneandone.net
[74.208.1.86]
15 98 ms 97 ms 98 ms te-2-1.bb-b.slr.lxa.us.oneandone.net
[74.208.1.90]
16 97 ms 101 ms 97 ms te-1-1.gw-dists-r5-
a.slr.lxa.oneandone.net [74.208.1.99]
17 100 ms 100 ms 101 ms vl-987.gw-ps1.slr.lxa.oneandone.net
[74.208.1.133]
18 * 96 ms 100 ms 74.208.34.120

Trace complete.

 

[Poprivet]

Hi,
I just ran a trace with dsnstuff.com: It didn't show Sprint in the trace at
all, but clearly shows over 250mS for the last 7 hops, of 12 total, all 7
thru nodes on oneandone.net.
But then Ping says:
Pinging 74.208.34.120 [74.208.34.120]:

Ping #1: Got reply from 74.208.34.120 in 55ms [TTL=55]
Ping #2: Got reply from 74.208.34.120 in 63ms [TTL=55]
Ping #3: Got reply from 74.208.34.120 in 57ms [TTL=55]
Ping #4: Got reply from 74.208.34.120 in 55ms [TTL=55]

So maybe one and one trashes the trace on purpose. Sprint may do the same.

Hi JR,

Your tracert points to a problem with Sprint link. I've included the
tracert from my shop for a comparison. I get excellent response
from your server.


5 4 ms 4 ms 4 ms owb.br03.g5-2.americanis.net
[206.251.233.66] 6 5 ms 5 ms 5 ms
bur-edge-04.inet.qwest.net [63.149.192.185] 7 6 ms 5 ms
5 ms bur-core-02.inet.qwest.net [205.171.13.57] 8 5 ms 5 ms
6 ms lap-brdr-02.inet.qwest.net [205.171.213.50] 9 16 ms 15
ms 16 ms 63.146.26.78 10 50 ms 50 ms 51 ms
64.209.102.178 11 49 ms 49 ms 49 ms
te-2-2.bb-b.hs.mkc.us.oneandone.net [74.208.1.86]
12 52 ms 50 ms 50 ms te-2-1.bb-b.slr.lxa.us.oneandone.net
[74.208.1.90]
13 50 ms 49 ms 49 ms
te-1-2.gw-dists-r5-a.slr.lxa.oneandone.net [74.208.1.115]
14 51 ms 50 ms 49 ms vl-987.gw-ps1.slr.lxa.oneandone.net
[74.208.1.133]
15 50 ms 49 ms 49 ms hhtackshop.com [74.208.34.120]

Try using www.dnsstuff.com to run a trace route from a remote
location.

John Cutsinger
Altegris Investments

TCP/IP novice here. I am having very slow access between my desktop
Windows PC and our hosted web site. I ran tracert (for Windows), as
requested by my hosting site support. I sent them the output and
they blame sprintlink.

I do not understand the output of tracert or traceroute. If it were
just me having the problem, I wouldn't mind so much. However, a
number of our customers around the U.S. are having the same
complaint. I'm only getting 20KB/sec for file transfers when I
normally get 300+.

Below is the trace. Is sprintlink an issue or is oneandone (our web
hoster) the problem? I appreciate any insight on this.

Tracing route to 74.208.34.120 over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 10.202.46.1
2 13 ms 8 ms 8 ms 66.60.130.170
3 9 ms 11 ms 7 ms 66.60.130.190
4 * 8 ms 8 ms 66.60.130.198
5 15 ms 13 ms 15 ms 65.170.194.65
6 14 ms 19 ms 13 ms sl-bb21-stk-11-2.sprintlink.net
[144.232.20.18]
7 85 ms 89 ms 85 ms sl-bb26-pen-12-0.sprintlink.net
[144.232.20.162]
8 86 ms 86 ms 86 ms sl-bb21-nyc-11-0-0.sprintlink.net
[144.232.20.143]
9 * 101 ms * sl-bb23-nyc-3-0.sprintlink.net
[144.232.7.109]
10 87 ms 87 ms 86 ms sl-gw30-nyc-1-0.sprintlink.net
[144.232.13.24]
11 121 ms 123 ms 121 ms sl-schlu4-2-0.sprintlink.net
[144.232.230.250]
12 86 ms 108 ms 86 ms vl-402.gw-core-b.nyc.oneandone.net
[217.160.229.105]
13 93 ms 93 ms 92 ms ge-3-1.bb-b.ms.mkc.us.oneandone.net
[212.227.120.230]
14 93 ms 93 ms 93 ms te-2-2.bb-b.hs.mkc.us.oneandone.net
[74.208.1.86]
15 98 ms 97 ms 98 ms te-2-1.bb-b.slr.lxa.us.oneandone.net
[74.208.1.90]
16 97 ms 101 ms 97 ms te-1-1.gw-dists-r5-
a.slr.lxa.oneandone.net [74.208.1.99]
17 100 ms 100 ms 101 ms vl-987.gw-ps1.slr.lxa.oneandone.net
[74.208.1.133]
18 * 96 ms 100 ms 74.208.34.120

Trace complete.