Rune Central

Here's my traceroute to shmack, what the heck is going on here? I assume I'm just screwed until I get a new ISP, but I'm posting this anyway cause I know how much people like to hear ping whining

Tracing route to 69.64.35.230 over a maximum of 30 hops
1 3 ms <1 ms <1 ms 192.168.0.1
2 49 ms 41 ms 41 ms mpls-dsl-gw06.mpls.qwest.net [207.225.140.6]
3 50 ms 41 ms 42 ms mpls-agw1.inet.qwest.net [207.225.140.93]
4 41 ms 42 ms 41 ms mpl-core-01.inet.qwest.net [205.171.128.21]
5 65 ms 65 ms 65 ms dal-core-02.inet.qwest.net [205.171.8.141]
6 65 ms 64 ms 65 ms dap-brdr-01.inet.qwest.net [205.171.225.53]
7 65 ms 65 ms 65 ms so-1-2-0.edge1.Dallas1.Level3.net [209.245.240.165]
8 * * * Request timed out.
9 104 ms 96 ms 96 ms so-3-0-0.mp2.StLouis1.Level3.net [64.159.0.50]
10 97 ms 97 ms 96 ms ge-7-2.hsa1.StLouis1.Level3.net [64.159.4.142]
11 97 ms 97 ms 97 ms server4you-gw.stl1.us.inetbone.net [63.208.32.162]
12 97 ms 97 ms 97 ms 69.64.35.230
Trace complete.


It's smooth sailing to the chicago server singed is on:

Tracing route to 64-202-114-222 over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.0.1
2 49 ms 41 ms 41 ms mpls-dsl-gw06.mpls.qwest.net [207.225.140.6]
3 49 ms 41 ms 41 ms mpls-agw1.inet.qwest.net [207.225.140.93]
4 49 ms 41 ms 41 ms mpl-core-01.inet.qwest.net [205.171.128.21]
5 58 ms 50 ms 50 ms cer-core-01.inet.qwest.net [205.171.205.62]
6 59 ms 50 ms 51 ms chp-brdr-01.inet.qwest.net [205.171.139.146]
7 58 ms 50 ms 51 ms 205.171.4.14
8 59 ms 50 ms 50 ms 0.so-5-0-0.XL1.CHI13.ALTER.NET [152.63.73.17]
9 59 ms 50 ms 50 ms POS6-0.GW2.CHI13.ALTER.NET [152.63.71.205]
10 59 ms 51 ms 51 ms uunet.ord.scnet.net [64.202.110.2]
11 51 ms 51 ms 51 ms so-3-1-0.j2.ord.scnet.net [205.234.158.82]
12 51 ms 51 ms 51 ms a3.2540.ord.scnet.net [64.202.110.50]
13 59 ms 51 ms 52 ms 64-202-114-222.chi.essentrix.net [64.202.114.222]
Trace complete.

What is your ISP? Is it Verizon? Qwest?
Whats your connection Speed?

Mines 703KDown/131KUp
My ISP is Verizon, and lately Im getting bad pings on the first hop, averaging 30ms instead of 15ms on the first hop.

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Owner>tracert quake.shmack.net

Tracing route to quake.shmack.net [69.64.35.230]
over a maximum of 30 hops:

1 30 ms 31 ms 30 ms 10.6.3.1
2 31 ms 31 ms 30 ms at-2-0-0-1713.CORE-RTR2.PITT2.verizon-gni.net [1
30.81.8.193]
3 31 ms 29 ms 31 ms at-3-0-1-0.CORE-RTR1.PITT2.verizon-gni.net [130.
81.18.250]
4 31 ms 31 ms 31 ms so-7-0-0-0.BB-RTR1.RES.verizon-gni.net [130.81.1
8.0]
5 31 ms 30 ms 31 ms 130.81.10.90
6 31 ms 31 ms 31 ms so-0-2-0-0.e1.Washington1.Level3.net [67.29.172.
13]
7 31 ms 31 ms 30 ms so-2-1-0.bbr2.Washington1.Level3.net [209.244.11
.13]
8 62 ms 62 ms 62 ms so-0-0-0.mp2.StLouis1.Level3.net [64.159.0.57]
9 62 ms 62 ms 62 ms ge-7-2.hsa1.StLouis1.Level3.net [64.159.4.142]
10 62 ms 62 ms 62 ms server4you-gw.stl1.us.inetbone.net [63.208.32.16
2]
11 61 ms 62 ms 61 ms 69.64.35.230

Trace complete.

and to the signed server

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Owner>tracert 64.202.114.222

Tracing route to 64-202-114-222.chi.essentrix.net [64.202.114.222]
over a maximum of 30 hops:

1 29 ms 15 ms 30 ms 10.6.3.1
2 31 ms 31 ms 31 ms at-2-0-0-1713.CORE-RTR2.PITT2.verizon-gni.net [1
30.81.8.193]
3 31 ms 31 ms 31 ms at-3-0-1-0.CORE-RTR1.PITT2.verizon-gni.net [130.
81.18.250]
4 31 ms 31 ms 31 ms so-7-0-0-0.BB-RTR1.RES.verizon-gni.net [130.81.1
8.0]
5 31 ms 31 ms 31 ms 130.81.10.90
6 31 ms 31 ms 31 ms 130.81.15.10
7 62 ms 62 ms 62 ms 0.so-0-1-0.cr1.ord1.us.nlayer.net [69.22.142.106
]
8 62 ms 62 ms 46 ms so2-0-0.j1.ord.scnet.net [64.202.110.73]
9 62 ms 62 ms 62 ms so-3-1-0.j2.ord.scnet.net [205.234.158.82]
10 62 ms 62 ms 62 ms a3.2540.ord.scnet.net [64.202.110.50]
11 62 ms 62 ms 62 ms 64-202-114-222.chi.essentrix.net [64.202.114.222
]

Trace complete.

C:\Documents and Settings\Owner>

My ISP is qwest. I have the faster dsl, 150KB down, 100KB up. Actually, after posting my traceroute I noticed that the first router was taking its sweet time, always atleast 41ms. So I called quest a few days ago and whined about it. They agreed it should take no more than 10ms, and said they'd have someone take a look at the router. It's been a couple days and it's still >41ms. I'll give them another day or so and then call them to whine some more.

It's amazing I still ping well to singed with a 40ms delay at the first router. It looks like something down the line is also funky in my shmack ping, but I'm sure I'm just stuck with it until I switch ISPs. All my friends in Minneapolis with time warner or charter cable ping like champs to both singed and shmack, but these aren't available where I'm at. I'll switch once I move.
-y

You might of been placed on Interleave which means really bad Pings, but it allows for future Speed Upgrades, you need Fast Path,(good Pings) and it hard to get. I dont know if Qwest Has Fast Path.



Interleave

I hope this helps
DSL Search

Getting really bad pings today, and speed seems like Dial-up.
Provisioned @768Kbps/128Kbps

Speed Test results

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Owner>tracert quake.shmack.net

Tracing route to quake.shmack.net [69.64.35.230]
over a maximum of 30 hops:

1 1074 ms 1202 ms 1218 ms 10.6.3.1
2 1280 ms 1327 ms 1390 ms at-2-0-0-1712.CORE-RTR1.PITT2.verizon-gni.net [1
30.81.8.189]
3 1405 ms 1406 ms 1452 ms so-7-0-0-0.BB-RTR1.RES.verizon-gni.net [130.81.1
8.0]
4 1452 ms 1437 ms 1531 ms 130.81.10.90
5 1546 ms 1562 ms 1531 ms so-0-2-0-0.e1.Washington1.Level3.net [67.29.172.
13]
6 1514 ms 1562 ms 1531 ms so-2-1-0.bbr2.Washington1.Level3.net [209.244.11
.13]
7 1623 ms 1531 ms 1577 ms so-3-0-0.mp1.StLouis1.Level3.net [64.159.0.49]
8 1593 ms * 609 ms ge-9-0.hsa1.StLouis1.Level3.net [64.159.0.62]
9 62 ms 62 ms 140 ms server4you-gw.stl1.us.inetbone.net [63.208.32.16
2]
10 62 ms 62 ms 62 ms 69.64.35.230

Trace complete.

C:\Documents and Settings\Owner>

Ah, man, Meatwad I thought you were using dialup --- I feel for you, bud.

Thanks Man

My Pings have returned to normal 18 to 20ms at the first hop and now speeds are back to the way it should be.

go meatwad

so how are your little meat-arms anyways?

interesting study guys, but why bother?

_________________
If you see me online, say Hi