Routing problem...?

[MrFire8808]

I just got my broadband hooked up today, and everything seems fine untill I goto play counter-strike.. I live in Bend, Oregon and I get a latency of 100 on a Portland, Oregon server.. yet 60 on a Dallas, TX server.. Whats going on here?! On my internet games list servers from Texas are showing up befor servers in OR, WA, CA (sorted by ping)..

Does my cable provider just suck balls or is there a problem here? I have Bend Broadband...

Also, my downloads seem to cap at 60 kbps..

Picture

 

[Goosemaster]

First of all, thank you for posting the schematics. Truly, I would not be able to help you out without them.

Take two Advil, post a tracert, and post another one in the morning.

 

[MrFire8808]

Did you vote for the lamp?

 

[Goosemaster]

i see no tracert....do not pass go, do not collect $200.


In windows, go to start, run, type 'cmd', press enter

then type 'tracert yahoo.com'


cut and paste the results to multiple site, such as local newspapers, and national stuff like yahoo and google.

 

[MrFire8808]

Tracing route to oregonian.com [65.223.248.205]
over a maximum of 30 hops:

1 8 ms 10 ms 10 ms bc18601.bendcable.com [216.228.186.1]
2 9 ms 23 ms 18 ms 216.228.160.67
3 23 ms 22 ms 31 ms 66.62.56.5
4 36 ms 33 ms 33 ms slc1-core-02.360.net [66.62.5.2]
5 31 ms 34 ms 35 ms den1-core-01.360.net [66.62.3.22]
6 32 ms 44 ms 35 ms den1-edge-01.360.net [66.62.4.67]
7 35 ms 56 ms 35 ms so-1-3-0-0.gar1.Denver1.Level3.net [4.71.40.9]
8 43 ms 35 ms 36 ms ae-1-53.bbr1.Denver1.Level3.net [4.68.107.65]
9 51 ms 48 ms 48 ms ae-0-0.bbr2.Dallas1.Level3.net [64.159.1.110]
10 47 ms 49 ms 49 ms so-7-0-0.edge1.Dallas1.Level3.net [209.244.15.16
6]
11 49 ms 48 ms 51 ms uunet-level3-oc48.Dallas1.Level3.net [209.245.24
0.142]
12 50 ms 52 ms 48 ms 0.so-3-3-0.XT1.DFW9.ALTER.NET [152.63.99.1]
13 92 ms 92 ms 92 ms 0.so-6-0-2.XT1.NYC8.ALTER.NET [152.63.0.22]
14 91 ms 94 ms 91 ms 0.so-2-0-0.WR1.NYC8.ALTER.NET [152.63.18.73]
15 106 ms 93 ms 93 ms pos7-0.ur1.ewr2.web.wcom.net [63.111.126.54]
16 94 ms 93 ms 93 ms 63.87.224.53
17 98 ms 95 ms 95 ms 63.87.230.193
18 97 ms 94 ms 93 ms core0-udc-ge.executor.ADVANCE.NET [69.2.115.169]

19 92 ms 97 ms 104 ms prodops-ge.udc0.ADVANCE.NET [69.2.115.178]
20 * prodops-ge.udc0.ADVANCE.NET [69.2.115.178] reports: Destination n
et unreachable.

Trace complete.

C:\Documents and Settings\Paul>tracert google.com

Tracing route to google.com [72.14.207.99]
over a maximum of 30 hops:

1 8 ms 6 ms 7 ms bc18601.bendcable.com [216.228.186.1]
2 7 ms 14 ms 13 ms 216.228.160.67
3 43 ms 32 ms 21 ms 66.62.56.5
4 45 ms 35 ms 51 ms slc1-core-01.360.net [66.62.5.65]
5 38 ms 36 ms 37 ms pdx1-core-01.360.net [66.62.3.10]
6 36 ms 38 ms 37 ms pdx1-edge-01.360.net [66.62.4.131]
7 42 ms 40 ms 42 ms POS10-3.PEERA-STTLWA.IP.GROUPTELECOM.NET [66.59.
190.41]
8 40 ms 39 ms 41 ms six.sea01.google.com [198.32.180.17]
9 41 ms 41 ms 39 ms 72.14.233.55
10 93 ms 95 ms 100 ms 72.14.233.118
11 97 ms 91 ms 93 ms 72.14.232.113
12 106 ms 93 ms 104 ms 72.14.236.134
13 92 ms 93 ms 110 ms 72.14.207.99

Trace complete.

C:\Documents and Settings\Paul>tracert portlandtribune.com

Tracing route to portlandtribune.com [128.121.215.224]
over a maximum of 30 hops:

1 9 ms 7 ms 8 ms bc18601.bendcable.com [216.228.186.1]
2 19 ms 7 ms 10 ms 216.228.160.67
3 21 ms 25 ms 23 ms 66.62.56.5
4 34 ms 32 ms 32 ms slc1-core-02.360.net [66.62.5.2]
5 36 ms 31 ms 31 ms den1-core-01.360.net [66.62.3.22]
6 33 ms 35 ms 34 ms den1-edge-01.360.net [66.62.4.67]
7 35 ms 40 ms 37 ms so-1-3-0-0.gar1.Denver1.Level3.net [4.71.40.9]
8 52 ms 34 ms 34 ms ae-1-53.bbr1.Denver1.Level3.net [4.68.107.65]
9 48 ms 47 ms 47 ms as-0-0.bbr1.Dallas1.Level3.net [209.247.11.22]
10 49 ms 54 ms 51 ms ae-23-54.car3.Dallas1.Level3.net [4.68.122.111]

11 50 ms 63 ms 50 ms verio-level3-10ge.Dallas1.Level3.net [4.68.110.6
2]
12 119 ms 97 ms 82 ms p64-0-0-0.r20.snjsca04.us.bb.gin.ntt.net [129.25
0.3.152]
13 86 ms 81 ms 84 ms xe-0-1-0.r20.mlpsca01.us.bb.gin.ntt.net [129.250
.5.61]
14 83 ms 83 ms 82 ms xe-1-1.r02.mlpsca01.us.bb.gin.ntt.net [129.250.3
.97]
15 93 ms 83 ms 80 ms ge-2-1.r00.mlpsca01.us.wh.verio.net [129.250.26.
169]
16 95 ms 82 ms 83 ms ge-25.a0354b.mlpsca01.us.wh.verio.net [128.121.1
29.74]
17 85 ms 84 ms 86 ms pamplinmedia.securesites.com [128.121.215.224]

Trace complete.

C:\Documents and Settings\Paul>tracert bendbulletin.com

Tracing route to bendbulletin.com [209.225.11.190]
over a maximum of 30 hops:

1 9 ms 10 ms 22 ms bc18601.bendcable.com [216.228.186.1]
2 7 ms 9 ms 18 ms 216.228.160.67
3 24 ms 20 ms 23 ms 66.62.56.5
4 46 ms 34 ms 45 ms slc1-core-02.360.net [66.62.5.2]
5 44 ms 46 ms 36 ms den1-core-01.360.net [66.62.3.22]
6 36 ms 35 ms 35 ms den1-edge-01.360.net [66.62.4.67]
7 34 ms 33 ms 34 ms so-1-3-0-0.gar1.Denver1.Level3.net [4.71.40.9]
8 * 33 ms * ae-1-53.bbr1.Denver1.Level3.net [4.68.107.65]
9 49 ms 51 ms 50 ms ae-0-0.bbr2.Dallas1.Level3.net [64.159.1.110]
10 50 ms 73 ms 58 ms ae-14-53.car4.Dallas1.Level3.net [4.68.122.80]
11 50 ms 51 ms 49 ms savvis-level3-ge.Dallas1.Level3.net [4.68.111.90
]
12 50 ms 49 ms 74 ms dpr1-ge-2-2-1.dallasequinix.savvis.net [204.70.1
94.29]
13 49 ms 50 ms 61 ms dcr1-so-1-1-0.dallas.savvis.net [204.70.194.66]

14 85 ms 93 ms 85 ms dcr2-so-6-0-0.Atlanta.savvis.net [204.70.192.69]

15 79 ms 84 ms 83 ms bcs1-so-2-0-0.Washington.savvis.net [204.70.192.
54]
16 80 ms 81 ms 79 ms bcs1-so-7-0-0.Washington.savvis.net [204.70.192.
33]
17 82 ms 81 ms 81 ms csr21-ve243.Sterlingdc2.savvis.net [216.33.98.27
]
18 81 ms 97 ms 81 ms csr21-ve243.Sterlingdc2.savvis.net [216.33.98.27
]
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.


C:\Documents and Settings\Paul>tracert msn.com

Tracing route to msn.com [207.68.172.246]
over a maximum of 30 hops:

1 8 ms 5 ms 10 ms bc18601.bendcable.com [216.228.186.1]
2 15 ms 7 ms 9 ms 216.228.160.67
3 24 ms 26 ms 28 ms 66.62.56.5
4 42 ms 36 ms 38 ms slc1-core-01.360.net [66.62.5.1]
5 43 ms 39 ms 39 ms pdx1-core-01.360.net [66.62.3.10]
6 36 ms 45 ms 35 ms pdx1-edge-01.360.net [66.62.4.131]
7 41 ms 39 ms 44 ms POS10-3.PEERA-STTLWA.IP.GROUPTELECOM.NET [66.59.
190.41]
8 * * * Request timed out.
9

 

[jlazzaro]

lol wow. just because its a website about oregon, doesnt mean it hosted in oregon. most of the above sites are being served from the east coast...ya rly.

you need to post traceroute's to the game servers themselves.

edit: damn you.

 

[nweaver]

eh....yeah, you do realize that the "InTernET" doesn't follow the highway, right?

This is normal. to ping my work from my home, (AT&T T1 at home, 27 miles to work) I went to Chicago first....

 

[MrFire8808]

lol wow. just because its a website about oregon, doesnt mean it hosted in oregon. most of the above sites are being served from the east coast...ya rly.

Im aware of this, I just did what I was instructed to do

cut and paste the results to multiple site, such as local newspapers, and national stuff like yahoo and google.

 

[MrFire8808]

Originally posted by: nweaver
eh....yeah, you do realize that the "InTernET" doesn't follow the highway, right?

This is normal. to ping my work from my home, (AT&T T1 at home, 27 miles to work) I went to Chicago first....

Hm.. then what could be causing me to get terrible pings to local servers? It wasnt like this when I had comcast

 

[nweaver]

because you may be routed across an ISP prior to actually hitting the "Internet"

Possibly the server was ON the comcast network

Do you actually understand routing? You don't just go your house->ISP->location, you get bounced everywhere (as is evidenced by my home->work via Chicago example)

 

[MrFire8808]

Originally posted by: nweaver
because you may be routed across an ISP prior to actually hitting the "Internet"

Possibly the server was ON the comcast network

Do you actually understand routing? You don't just go your house->ISP->location, you get bounced everywhere (as is evidenced by my home->work via Chicago example)

No, I do not understand routing, which may or may not be why I am here asking for help.

Do you understand the issue I am having? Im not concerned that its routing to dallas or LA or where ever. I'm concerned because I get triple the latency on the same servers I frequent on and the only thing that has changed is my ISP. Now from what you're telling me, its definatly not a routing problem. What I want to know is how I can fix this.

I know nothing about computers, I know nothing about the InTErneT.

 

[spidey07]

Originally posted by: MrFire8808
No, I do not understand routing, which may or may not be why I am here asking for help.

Do you understand the issue I am having? Im not concerned that its routing to dallas or LA or where ever. I'm concerned because I get triple the latency on the same servers I frequent on and the only thing that has changed is my ISP. Now from what you're telling me, its definatly not a routing problem. What I want to know is how I can fix this.

I know nothing about computers, I have an IQ of about 50 and this message took me hours to type.. How can you help?

You have no control whatsoever of how your packets get routed on the Internet.

There is nothing you can do.

 

[Goosemaster]

Originally posted by: spidey07

Originally posted by: MrFire8808
No, I do not understand routing, which may or may not be why I am here asking for help.

Do you understand the issue I am having? Im not concerned that its routing to dallas or LA or where ever. I'm concerned because I get triple the latency on the same servers I frequent on and the only thing that has changed is my ISP. Now from what you're telling me, its definatly not a routing problem. What I want to know is how I can fix this.

I know nothing about computers, I have an IQ of about 50 and this message took me hours to type.. How can you help?

You have no control whatsoever of how your packets get routed on the Internet.

There is nothing you can do.

*in deep ominous voice*

muwahahahahha,....MUWAHAHAHAHAHHA

seriously though, call your ISP