Could someone please explain to me why this route is so crazy?

http://www.digitalravers.com/serverbeach.jpg

I live in the san fernando valley and I ping 100 ms to my server. But at my work in Santa Monica I only ping 50 to my server. So my question is... why is this route so funky?

:beer:

could possibly do with your ISP at home vs. your work connections routing?

www.traceroute.org is a great site where you can trace from around the world.

i'm doing a 186ms round trip from europe.

chello > telia > sprintlink > southwestern bell

Here's from Greenville, SC:

3 26 ms 26 ms 26 ms 216.227.49.108
4 25 ms 25 ms 25 ms ge-1-2-0-50.core1.atl.tlct.net [216.227.49.129]
5 45 ms 44 ms 46 ms so-1-0-0.core2.dfw.tlct.net [216.227.126.22]
6 45 ms 45 ms 45 ms fe-0-2-1.border1.dfw.tlct.net [216.227.126.190]
7 71 ms 69 ms 84 ms mae-atm-central.sbcglobal.net [198.32.139.60]
8 48 ms 50 ms 47 ms bb2-p12-0.rcsntx.sbcglobal.net [151.164.240.237]
9 54 ms 56 ms 56 ms bb1-p4-0.snantx.sbcglobal.net [151.164.240.177]
10 55 ms 56 ms 54 ms ded2-fa1-1-0.snantx.swbell.net [151.164.17.245]
11 54 ms 56 ms 58 ms vip-3027462.cust-rtr.swbell.net [151.164.19.174]
12 133 ms 60 ms 55 ms www.serverbeach.com [66.139.72.8]

Here's from Atlanta, GA:

6 P2-3.c0.atln.broadwing.net (216.140.12.1) 1.877 ms 0.898 ms 1.454 ms
7 P0-0-0.c1.atln.broadwing.net (216.140.17.26) 1.449 ms 1.361 ms 1.292 ms
8 P5-0.c0.wash.broadwing.net (216.140.16.6) 12.262 ms 12.253 ms 12.064 ms
9 216.140.17.29 (216.140.17.29) 12.585 ms 12.058 ms 12.105 ms
10 P2-0.a0.wash.broadwing.net (216.140.8.2) 11.975 ms * 12.695 ms
11 P5-0-0.p0.maee.broadwing.net (216.140.8.10) 13.178 ms 12.845 ms 12.758 ms
12 mae-atm-east.sbcglobal.net (198.32.187.175) 13.733 ms 13.647 ms 13.737 ms
13 bb1-p15-0.hrndva.sbcglobal.net (151.164.243.25) 13.611 ms 189.989 ms 13.948 ms
14 bb2-p11-0.rcsntx.sbcglobal.net (151.164.243.193) 30.610 ms 31.093 ms 30.739 ms
15 bb1-p4-0.snantx.sbcglobal.net (151.164.240.177) 39.291 ms 39.359 ms 39.179 ms
16 ded2-fa1-1-0.snantx.swbell.net (151.164.17.245) 39.456 ms 39.341 ms 39.477 ms
17 vip-3027462.cust-rtr.swbell.net (151.164.19.174) 39.739 ms 40.041 ms 40.141 ms
18 www.serverbeach.com (66.139.72.8) 39.801 ms 40.240 ms 40.123 ms

Here's from Seattle, WA:

3 h1-0-1.gw01.sttl.eli.net (209.210.81.17) 2.488 ms 2.498 ms 1.663 ms
4 srp2-0.cr01.tkwl.eli.net (208.186.20.33) 1.658 ms 2.496 ms 2.496 ms
5 so-0-0-0--0.er02.sttl.eli.net (207.173.114.146) 2.491 ms 7.500 ms 2.495 ms
6 bb1-g1-0.pxsewa.sbcglobal.net (198.32.134.14) 2.496 ms 2.496 ms 2.495 ms
7 bb1-p5-0.sttlwa.sbcglobal.net (151.164.241.61) 67.491 ms 66.662 ms 66.661 ms
8 bb2-p14-0.sttlwa.sbcglobal.net (151.164.240.174) 67.496 ms 66.663 ms 66.662 ms
9 bb1-p12-0.rcsntx.swbell.net (151.164.241.58) 68.322 ms 67.530 ms 68.315 ms
10 bb2-p15-0.rcsntx.sbcglobal.net (151.164.243.10) 66.637 ms 70.830 ms 67.495 ms
11 bb1-p4-0.snantx.sbcglobal.net (151.164.240.177) 75.824 ms 78.329 ms 75.003 ms
12 ded2-fa1-1-0.snantx.swbell.net (151.164.17.245) 78.328 ms 75.832 ms 75.833 ms
13 vip-3027462.cust-rtr.swbell.net (151.164.19.174) 75.825 ms 77.496 ms 75.829 ms
14 www.serverbeach.com (66.139.72.8) 75.822 ms 76.662 ms 75.000 ms

On another note, they only appear to have connectivity from Southwestern Bell, because they have no ASN, and their IP space (through SWBELL) is only announced under Southwestern Bell's ASN from what I can tell.

traceroute to activision.com (63.146.124.28), 30 hops max, 38 byte packets
1 66.139.73.1 (66.139.73.1) 0.504 ms 0.509 ms 0.422 ms
2 151.164.19.173 (151.164.19.173) 26.878 ms 219.354 ms 2.020 ms
3 bb1-g8-0.snantx.swbell.net (151.164.17.246) 1.105 ms 1.134 ms 1.101 ms
4 bb2-p13-0.rcsntx.sbcglobal.net (151.164.240.178) 9.308 ms 9.258 ms 9.237 ms
5 bb1-p15-0.rcsntx.sbcglobal.net (151.164.243.9) 9.628 ms 18.003 ms 9.460 ms
6 sl-gw39-fw-8-0.sprintlink.net (144.228.130.185) 11.391 ms 11.520 ms 11.279
ms
7 144.232.11.66 (144.232.11.66) 11.712 ms 11.730 ms 11.570 ms
8 144.232.11.34 (144.232.11.34) 11.961 ms 11.735 ms 11.732 ms
9 144.232.19.214 (144.232.19.214) 13.883 ms 13.503 ms 13.251 ms

10 dal-core-01.inet.qwest.net (205.171.25.45) 13.396 ms 13.486 ms 13.783 ms
11 iah-core-02.inet.qwest.net (205.171.8.126) 18.451 ms 18.500 ms 18.331 ms
12 bur-core-01.inet.qwest.net (205.171.205.25) 44.998 ms 45.206 ms 45.157 ms
13 bur-core-02.inet.qwest.net (205.171.13.2) 44.786 ms 44.721 ms 44.663 ms
14 buc-cntr-01.inet.qwest.net (205.171.13.158) 44.687 ms 44.941 ms 44.673 ms
15 msfc-88.buc.qwest.net (66.77.125.179) 44.829 ms 44.802 ms 44.808 ms
16 66.77.90.228 (66.77.90.228) 44.841 ms 44.853 ms 44.710 ms
17 63.146.124.28 (63.146.124.28) 44.959 ms 44.855 ms 44.992 ms
[root@www logs]#

This is to activision.com located in santa monica, how come it goes through qwest?

because activision.com's feed is qwest. :)