Rotareneg
Internetus Quickus
- Joined
- Jun 25, 2001
- Posts
- 252
- Likes
- 10
Ouch! No wonder the site's so painfully hard to navigate!
Holy mega lag batman!
- Thread starter Rotareneg
- Start date
- Joined
- Jun 20, 2001
- Posts
- 11,025
- Likes
- 6,633
From various cities, I tracerouted to altavista.com and head-fi.org, and here are the results below:
From San Jose
traceroute to altavista.com (209.73.164.94), 30 hops max, 40 byte packets
1 gigaethernet9-2.ipcolo1.SanJose1.Level3.net (209.244.13.186) 1 ms 0 ms 1 ms
2 POS11-0.ipcolo3.SanJose1.Level3.net (209.244.13.58) 0 ms 0 ms 0 ms
3 64.152.64.6 (64.152.64.6) 83 ms 83 ms 86 ms
4 10.28.2.9 (10.28.2.9) 83 ms 83 ms 83 ms
5 altavista.com (209.73.164.94) 84 ms 83 ms 83 ms
traceroute to head-fi.org (161.58.243.98), 30 hops max, 40 byte packets
1 verio-level3-oc12.SanJose1.Level3.net (209.0.227.30) 1 ms 1 ms 1 ms
2 p4-7-2-0.r00.plalca01.us.bb.verio.net (129.250.3.117) 2 ms 2 ms 2 ms
3 p4-6-0-0.r02.mclnva02.us.bb.verio.net (129.250.2.246) 92 ms 92 ms 92 ms
4 vwh1.dca.verio.net (129.250.30.167) 92 ms 92 ms 92 ms
5 wusezine.com (161.58.243.98) 92 ms 93 ms 92 ms
From Tokyo
traceroute to altavista.com (209.73.180.9), 30 hops max, 40 byte packets
1 ge-0-3-0.mpls2.tok1.japan.Level3.net (210.57.4.194) 1 ms 0 ms 0 ms
2 210.57.4.86 (210.57.4.86) 113 ms 113 ms 113 ms
3 at-7-0-0-285.mp1.LosAngeles1.Level3.net (209.244.19.18) 113 ms 114 ms 113 ms
4 so-0-1-0.mp1.NewYork1.Level3.net (209.247.8.9) 185 ms 185 ms 185 ms
5 pos8-0.core1.NewYork1.Level3.net (209.247.10.34) 185 ms 185 ms 185 ms
6 gigaethernet6-0.ipcolo1.NewYork1.Level3.net (209.244.12.42) 184 ms 184 ms 185 ms
7 209.246.123.66 (209.246.123.66) 184 ms 185 ms 185 ms
8 10.32.2.13 (10.32.2.13) 185 ms 185 ms 185 ms
9 altavista.com (209.73.180.9) 185 ms 185 ms 185 ms
traceroute to head-fi.org (161.58.243.98), 30 hops max, 40 byte packets
1 ge-7-1-0.mpls2.tok1.japan.Level3.net (210.57.4.130) 1 ms 0 ms 0 ms
2 210.57.4.86 (210.57.4.86) 113 ms 114 ms 113 ms
3 at-7-1-0-285.mp1.LosAngeles1.Level3.net (209.244.19.26) 113 ms 113 ms 113 ms
4 so-0-1-0.mp2.SanJose1.Level3.net (209.247.8.82) 125 ms 125 ms 125 ms
5 pos9-0.core2.SanJose1.Level3.net (209.247.11.14) 125 ms 125 ms 125 ms
6 verio-level3-oc12.SanJose1.Level3.net (209.0.227.30) 126 ms 126 ms 126 ms
7 p4-7-2-0.r00.plalca01.us.bb.verio.net (129.250.3.117) 127 ms 127 ms 127 ms
8 p4-6-0-0.r02.mclnva02.us.bb.verio.net (129.250.2.246) 193 ms 193 ms 193 ms
9 vwh1.dca.verio.net (129.250.30.167) 193 ms 193 ms 193 ms
10 wusezine.com (161.58.243.98) 193 ms 193 ms 193 ms
From Washington DC
traceroute to altavista.com (209.73.164.92), 30 hops max, 40 byte packets
1 pos1-15.core1.Washington1.Level3.net (209.247.10.81) 1 ms 1 ms 1 ms
2 so-4-0-0.mp1.Washington1.Level3.net (209.247.10.65) 1 ms 1 ms 1 ms
3 so-0-1-0.mp2.SanJose1.Level3.net (209.247.8.82) 103 ms 103 ms 103 ms
4 pos9-0.core1.SanJose1.Level3.net (209.247.11.10) 103 ms 103 ms 103 ms
5 gigaethernet6-0.ipcolo1.SanJose1.Level3.net (209.244.13.42) 103 ms 103 ms 103 ms
6 POS11-0.ipcolo3.SanJose1.Level3.net (209.244.13.58) 103 ms 103 ms 103 ms
7 64.152.64.6 (64.152.64.6) 98 ms 98 ms 98 ms
8 10.28.2.9 (10.28.2.9) 98 ms 98 ms 98 ms
9 altavista.com (209.73.164.92) 89 ms 89 ms 89 ms
traceroute to head-fi.org (161.58.243.98), 30 hops max, 40 byte packets
1 pos1-15.core1.Washington1.Level3.net (209.247.10.81) 1 ms 1 ms 1 ms
2 so-4-0-0.mp2.Washington1.Level3.net (209.247.10.73) 1 ms 1 ms 1 ms
3 pos9-0.core2.Washington1.Level3.net (209.247.10.78) 1 ms 1 ms 1 ms
4 p4-6-3-0.r02.mclnva02.us.bb.verio.net (129.250.9.53) 1 ms 1 ms 1 ms
5 vwh1.dca.verio.net (129.250.30.167) 1 ms 1 ms 1 ms
6 wusezine.com (161.58.243.98) 1 ms 1 ms 1 ms
From Saint Louis
traceroute to altavista.com (209.73.164.91), 30 hops max, 40 byte packets
1 ge-6-0-1.mp1.Stlouis1.Level3.net (64.159.0.65) 1 ms 0 ms 0 ms
2 so-0-2-0.mp1.SanJose1.Level3.net (209.247.8.110) 61 ms 61 ms 61 ms
3 pos8-0.core2.SanJose1.Level3.net (209.247.11.6) 61 ms 61 ms 61 ms
4 gigaethernet6-1.ipcolo1.SanJose1.Level3.net (209.244.13.86) 61 ms 61 ms 61 ms
5 POS11-0.ipcolo3.SanJose1.Level3.net (209.244.13.58) 61 ms 61 ms 61 ms
6 64.152.64.6 (64.152.64.6) 83 ms 83 ms 83 ms
7 10.28.2.9 (10.28.2.9) 83 ms 83 ms 83 ms
8 altavista.com (209.73.164.91) 83 ms 83 ms 83 ms
traceroute to head-fi.org (161.58.243.98), 30 hops max, 40 byte packets
1 ge-6-0-1.mp2.Stlouis1.Level3.net (64.159.0.73) 1 ms 0 ms 0 ms
2 so-5-1-0.mp2.Chicago1.Level3.net (64.159.0.58) 6 ms 6 ms 6 ms
3 pos9-0.core2.Chicago1.Level3.net (209.247.10.174) 5 ms 5 ms 5 ms
4 p1-0-8.r00.chcgil01.us.bb.verio.net (129.250.9.9) 6 ms 6 ms 6 ms
5 p1-1-0.r00.mclnva02.us.bb.verio.net (129.250.4.17) 39 ms 39 ms 39 ms
6 vwh1.dca.verio.net (129.250.30.167) 39 ms 39 ms 39 ms
7 wusezine.com (161.58.243.98) 39 ms 39 ms 39 ms
From Cincinnati
traceroute to altavista.com (209.73.164.93), 30 hops max, 40 byte packets
1 ge-6-0-1.mp1.Cincinnati1.Level3.net (64.159.0.177) 1 ms 0 ms 0 ms
2 so-0-1-0.mp2.SanJose1.Level3.net (209.247.8.82) 72 ms 72 ms 72 ms
3 pos9-0.core1.SanJose1.Level3.net (209.247.11.10) 72 ms 72 ms 72 ms
4 gigaethernet9-0.ipcolo1.SanJose1.Level3.net (209.244.13.166) 72 ms 72 ms 72 ms
5 POS11-0.ipcolo3.SanJose1.Level3.net (209.244.13.58) 72 ms 72 ms 72 ms
6 64.152.64.6 (64.152.64.6) 89 ms 89 ms 89 ms
7 10.28.2.9 (10.28.2.9) 89 ms 89 ms 89 ms
8 altavista.com (209.73.164.93) 99 ms 98 ms 98 ms
traceroute to head-fi.org (161.58.243.98), 30 hops max, 40 byte packets
1 ge-6-0-1.mp1.Cincinnati1.Level3.net (64.159.0.177) 1 ms 0 ms 0 ms
2 so-5-0-0.mp1.Chicago1.Level3.net (64.159.0.162) 7 ms 7 ms 7 ms
3 pos8-0.core2.Chicago1.Level3.net (209.247.10.166) 7 ms 7 ms 6 ms
4 p1-0-8.r00.chcgil01.us.bb.verio.net (129.250.9.9) 7 ms 7 ms 7 ms
5 p1-1-0.r00.mclnva02.us.bb.verio.net (129.250.4.17) 31 ms 31 ms 31 ms
6 vwh1.dca.verio.net (129.250.30.167) 31 ms 31 ms 31 ms
7 wusezine.com (161.58.243.98) 32 ms 31 ms 32 ms
From Hong Kong
traceroute to altavista.com (209.73.180.8), 30 hops max, 40 byte packets
1 ge-0-3-0.mpls1.Hongkong1.Level3.net (210.57.2.129) 1 ms 0 ms 0 ms
2 at-7-1-0-284.mp1.LosAngeles1.Level3.net (209.244.19.10) 147 ms 150 ms 147 ms
3 so-0-1-0.mp1.NewYork1.Level3.net (209.247.8.9) 221 ms 221 ms 221 ms
4 pos8-0.core1.NewYork1.Level3.net (209.247.10.34) 221 ms 218 ms 218 ms
5 209.244.12.38 (209.244.12.38) 221 ms 221 ms 221 ms
6 209.246.123.66 (209.246.123.66) 221 ms 222 ms 221 ms
7 10.32.2.13 (10.32.2.13) 232 ms 219 ms 219 ms
8 altavista.com (209.73.180.8) 219 ms 219 ms 232 ms
traceroute to head-fi.org (161.58.243.98), 30 hops max, 40 byte packets
1 ge-7-1-0.mpls1.Hongkong1.Level3.net (210.57.2.193) 1 ms 0 ms 0 ms
2 at-7-0-0-285.mp1.LosAngeles1.Level3.net (209.244.19.18) 153 ms 153 ms 153 ms
3 so-0-1-0.mp2.SanJose1.Level3.net (209.247.8.82) 162 ms 162 ms 162 ms
4 pos9-0.core2.SanJose1.Level3.net (209.247.11.14) 162 ms 163 ms 162 ms
5 verio-level3-oc12.SanJose1.Level3.net (209.0.227.30) 162 ms 166 ms 165 ms
6 p4-7-2-0.r00.plalca01.us.bb.verio.net (129.250.3.117) 177 ms 177 ms 166 ms
7 p4-6-0-0.r02.mclnva02.us.bb.verio.net (129.250.2.246) 232 ms 232 ms 232 ms
8 vwh1.dca.verio.net (129.250.30.167) 229 ms 231 ms 230 ms
9 wusezine.com (161.58.243.98) 231 ms 230 ms 233 ms
From London
traceroute to 1 212.113.3.1 (212.113.3.1) 3 ms 2 ms 2 ms
2 loopback0.mp2.London1.Level3.net (212.113.2.12) 2 ms 2 ms 2 ms
3 altavista.com (209.73.164.92), 30 hops max, 40 byte packets
212.187.128.153 (212.187.128.153) 68 ms 68 ms 67 ms
4 so-0-2-0.mp1.SanJose1.Level3.net (209.247.8.110) 164 ms 164 ms 164 ms
5 pos8-0.core2.SanJose1.Level3.net (209.247.11.6) 164 ms 164 ms 164 ms
6 gigaethernet6-2.ipcolo1.SanJose1.Level3.net (209.244.13.94) 164 ms 164 ms 164 ms
7 POS11-0.ipcolo3.SanJose1.Level3.net (209.244.13.58) 164 ms 164 ms 164 ms
8 64.152.64.6 (64.152.64.6) 159 ms 159 ms 158 ms
9 10.28.2.9 (10.28.2.9) 159 ms 159 ms 159 ms
10 altavista.com (209.73.164.92) 150 ms 150 ms 150 ms
traceroute to head-fi.org (161.58.243.98), 30 hops max, 40 byte packets
1 212.113.3.2 (212.113.3.2) 2 ms 2 ms 2 ms
2 loopback0.mp2.London1.Level3.net (212.113.2.12) 2 ms 2 ms 2 ms
3 212.187.128.153 (212.187.128.153) 68 ms 68 ms 68 ms
4 pos9-0.core1.NewYork1.Level3.net (209.247.10.42) 68 ms 68 ms 67 ms
5 above-level3-oc3.nyc.above.net (209.244.160.182) 68 ms 68 ms 68 ms
6 p4-1-2-0.r00.nycmny01.us.bb.verio.net (129.250.4.65) 68 ms 68 ms 68 ms
7 p4-6-3-0.r00.nycmny06.us.bb.verio.net (129.250.4.50) 68 ms 68 ms 68 ms
8 p4-4-0-0.r01.mclnva02.us.bb.verio.net (129.250.3.182) 75 ms 74 ms 75 ms
9 vwh2.dca.verio.net (129.250.31.166) 74 ms 75 ms 74 ms
10 wusezine.com (161.58.243.98) 75 ms 75 ms 75 ms
From Paris
traceroute to altavista.com (209.73.164.93), 30 hops max, 40 byte packets
1 212.73.240.1 (212.73.240.1) 2 ms 1 ms 1 ms
2 so-1-0-0-0.mp2.London2.Level3.net (212.187.128.42) 7 ms 7 ms 7 ms
3 212.187.128.190 (212.187.128.190) 74 ms 74 ms 74 ms
4 so-0-2-0.mp1.SanJose1.Level3.net (209.247.8.110) 171 ms 171 ms 170 ms
5 pos8-0.core2.SanJose1.Level3.net (209.247.11.6) 171 ms 171 ms 171 ms
6 gigaethernet6-1.ipcolo1.SanJose1.Level3.net (209.244.13.86) 171 ms 171 ms 171 ms
7 POS11-0.ipcolo3.SanJose1.Level3.net (209.244.13.58) 171 ms 171 ms 170 ms
8 64.152.64.6 (64.152.64.6) 165 ms 165 ms 165 ms
9 Connection timed out - host may be temporarily unavailable.
traceroute to head-fi.org (161.58.243.98), 30 hops max, 40 byte packets
1 212.73.240.1 (212.73.240.1) 3 ms 1 ms 1 ms
2 so-1-0-0-0.mp2.London2.Level3.net (212.187.128.42) 7 ms 7 ms 7 ms
3 212.187.128.190 (212.187.128.190) 74 ms 74 ms 74 ms
4 pos8-0.core1.NewYork1.Level3.net (209.247.10.34) 74 ms 74 ms 74 ms
5 above-level3-oc3.nyc.above.net (209.244.160.182) 74 ms 74 ms 74 ms
6 p4-1-2-0.r00.nycmny01.us.bb.verio.net (129.250.4.65) 74 ms 74 ms 74 ms
7 p4-6-3-0.r00.nycmny06.us.bb.verio.net (129.250.4.50) 74 ms 74 ms 74 ms
8 p4-4-0-0.r01.mclnva02.us.bb.verio.net (129.250.3.182) 81 ms 81 ms 81 ms
9 vwh2.dca.verio.net (129.250.31.166) 81 ms 81 ms 82 ms
10 wusezine.com (161.58.243.98) 81 ms 82 ms 81 ms
Brussels
traceroute to altavista.com (209.73.164.93), 30 hops max, 40 byte packets
1 212.3.239.2 (212.3.239.2) 2 ms 2 ms 2 ms
2 so-2-0-0-0.mp2.London2.Level3.net (212.187.128.53) 6 ms 6 ms 6 ms
3 212.187.128.190 (212.187.128.190) 73 ms 73 ms 73 ms
4 so-0-2-0.mp1.SanJose1.Level3.net (209.247.8.110) 169 ms 170 ms 170 ms
5 pos8-0.core2.SanJose1.Level3.net (209.247.11.6) 170 ms 170 ms 170 ms
6 gigaethernet9-2.ipcolo1.SanJose1.Level3.net (209.244.13.186) 169 ms 170 ms 170 ms
7 POS11-0.ipcolo3.SanJose1.Level3.net (209.244.13.58) 169 ms 169 ms 169 ms
8 64.152.64.6 (64.152.64.6) 165 ms 164 ms 164 ms
9 10.28.2.9 (10.28.2.9) 164 ms 164 ms 164 ms
10 altavista.com (209.73.164.93) 155 ms 155 ms 155 ms
traceroute to head-fi.org (161.58.243.98), 30 hops max, 40 byte packets
1 212.3.239.2 (212.3.239.2) 2 ms 2 ms 2 ms
2 so-2-0-0-0.mp2.London2.Level3.net (212.187.128.53) 6 ms 6 ms 6 ms
3 212.187.128.190 (212.187.128.190) 73 ms 73 ms 73 ms
4 pos8-0.core1.NewYork1.Level3.net (209.247.10.34) 73 ms 73 ms 73 ms
5 above-level3-oc3.nyc.above.net (209.244.160.182) 73 ms 73 ms 73 ms
6 p4-1-2-0.r00.nycmny01.us.bb.verio.net (129.250.4.65) 73 ms 73 ms 73 ms
7 p4-6-3-0.r00.nycmny06.us.bb.verio.net (129.250.4.50) 73 ms 73 ms 73 ms
8 p4-4-0-0.r01.mclnva02.us.bb.verio.net (129.250.3.182) 80 ms 80 ms 80 ms
9 vwh2.dca.verio.net (129.250.31.166) 80 ms 80 ms 80 ms
10 wusezine.com (161.58.243.98) 80 ms 80 ms 80 ms
From Dallas
traceroute to altavista.com (209.73.164.92), 30 hops max, 40 byte packets
1 so-6-0-0.mp2.Dallas1.Level3.net (209.247.10.109) 1 ms 1 ms 1 ms
2 so-0-0-0.mp1.SanJose1.Level3.net (209.244.19.33) 45 ms 45 ms 45 ms
3 pos8-0.core2.SanJose1.Level3.net (209.247.11.6) 45 ms 45 ms 45 ms
4 gigaethernet9-2.ipcolo1.SanJose1.Level3.net (209.244.13.186) 45 ms 45 ms 45 ms
5 POS11-0.ipcolo3.SanJose1.Level3.net (209.244.13.58) 45 ms 45 ms 45 ms
6 64.152.64.6 (64.152.64.6) 76 ms 77 ms 76 ms
7 10.28.2.9 (10.28.2.9) 77 ms 77 ms 76 ms
8 altavista.com (209.73.164.92) 86 ms 86 ms 86 ms
traceroute to head-fi.org (161.58.243.98), 30 hops max, 40 byte packets
1 209.245.240.154 (209.245.240.154) 1 ms 1 ms 1 ms
2 p4-6-3-0.r02.dllstx01.us.bb.verio.net (129.250.5.3) 1 ms 1 ms 1 ms
3 p4-1-2-0.r00.stngva01.us.bb.verio.net (129.250.4.26) 37 ms 37 ms 37 ms
4 p16-7-0-0.r01.mclnva02.us.bb.verio.net (129.250.3.157) 37 ms 37 ms 37 ms
5 vwh2.dca.verio.net (129.250.31.166) 37 ms 37 ms 37 ms
6 wusezine.com (161.58.243.98) 37 ms 37 ms 37 ms
From San Jose
traceroute to altavista.com (209.73.164.94), 30 hops max, 40 byte packets
1 gigaethernet9-2.ipcolo1.SanJose1.Level3.net (209.244.13.186) 1 ms 0 ms 1 ms
2 POS11-0.ipcolo3.SanJose1.Level3.net (209.244.13.58) 0 ms 0 ms 0 ms
3 64.152.64.6 (64.152.64.6) 83 ms 83 ms 86 ms
4 10.28.2.9 (10.28.2.9) 83 ms 83 ms 83 ms
5 altavista.com (209.73.164.94) 84 ms 83 ms 83 ms
traceroute to head-fi.org (161.58.243.98), 30 hops max, 40 byte packets
1 verio-level3-oc12.SanJose1.Level3.net (209.0.227.30) 1 ms 1 ms 1 ms
2 p4-7-2-0.r00.plalca01.us.bb.verio.net (129.250.3.117) 2 ms 2 ms 2 ms
3 p4-6-0-0.r02.mclnva02.us.bb.verio.net (129.250.2.246) 92 ms 92 ms 92 ms
4 vwh1.dca.verio.net (129.250.30.167) 92 ms 92 ms 92 ms
5 wusezine.com (161.58.243.98) 92 ms 93 ms 92 ms
From Tokyo
traceroute to altavista.com (209.73.180.9), 30 hops max, 40 byte packets
1 ge-0-3-0.mpls2.tok1.japan.Level3.net (210.57.4.194) 1 ms 0 ms 0 ms
2 210.57.4.86 (210.57.4.86) 113 ms 113 ms 113 ms
3 at-7-0-0-285.mp1.LosAngeles1.Level3.net (209.244.19.18) 113 ms 114 ms 113 ms
4 so-0-1-0.mp1.NewYork1.Level3.net (209.247.8.9) 185 ms 185 ms 185 ms
5 pos8-0.core1.NewYork1.Level3.net (209.247.10.34) 185 ms 185 ms 185 ms
6 gigaethernet6-0.ipcolo1.NewYork1.Level3.net (209.244.12.42) 184 ms 184 ms 185 ms
7 209.246.123.66 (209.246.123.66) 184 ms 185 ms 185 ms
8 10.32.2.13 (10.32.2.13) 185 ms 185 ms 185 ms
9 altavista.com (209.73.180.9) 185 ms 185 ms 185 ms
traceroute to head-fi.org (161.58.243.98), 30 hops max, 40 byte packets
1 ge-7-1-0.mpls2.tok1.japan.Level3.net (210.57.4.130) 1 ms 0 ms 0 ms
2 210.57.4.86 (210.57.4.86) 113 ms 114 ms 113 ms
3 at-7-1-0-285.mp1.LosAngeles1.Level3.net (209.244.19.26) 113 ms 113 ms 113 ms
4 so-0-1-0.mp2.SanJose1.Level3.net (209.247.8.82) 125 ms 125 ms 125 ms
5 pos9-0.core2.SanJose1.Level3.net (209.247.11.14) 125 ms 125 ms 125 ms
6 verio-level3-oc12.SanJose1.Level3.net (209.0.227.30) 126 ms 126 ms 126 ms
7 p4-7-2-0.r00.plalca01.us.bb.verio.net (129.250.3.117) 127 ms 127 ms 127 ms
8 p4-6-0-0.r02.mclnva02.us.bb.verio.net (129.250.2.246) 193 ms 193 ms 193 ms
9 vwh1.dca.verio.net (129.250.30.167) 193 ms 193 ms 193 ms
10 wusezine.com (161.58.243.98) 193 ms 193 ms 193 ms
From Washington DC
traceroute to altavista.com (209.73.164.92), 30 hops max, 40 byte packets
1 pos1-15.core1.Washington1.Level3.net (209.247.10.81) 1 ms 1 ms 1 ms
2 so-4-0-0.mp1.Washington1.Level3.net (209.247.10.65) 1 ms 1 ms 1 ms
3 so-0-1-0.mp2.SanJose1.Level3.net (209.247.8.82) 103 ms 103 ms 103 ms
4 pos9-0.core1.SanJose1.Level3.net (209.247.11.10) 103 ms 103 ms 103 ms
5 gigaethernet6-0.ipcolo1.SanJose1.Level3.net (209.244.13.42) 103 ms 103 ms 103 ms
6 POS11-0.ipcolo3.SanJose1.Level3.net (209.244.13.58) 103 ms 103 ms 103 ms
7 64.152.64.6 (64.152.64.6) 98 ms 98 ms 98 ms
8 10.28.2.9 (10.28.2.9) 98 ms 98 ms 98 ms
9 altavista.com (209.73.164.92) 89 ms 89 ms 89 ms
traceroute to head-fi.org (161.58.243.98), 30 hops max, 40 byte packets
1 pos1-15.core1.Washington1.Level3.net (209.247.10.81) 1 ms 1 ms 1 ms
2 so-4-0-0.mp2.Washington1.Level3.net (209.247.10.73) 1 ms 1 ms 1 ms
3 pos9-0.core2.Washington1.Level3.net (209.247.10.78) 1 ms 1 ms 1 ms
4 p4-6-3-0.r02.mclnva02.us.bb.verio.net (129.250.9.53) 1 ms 1 ms 1 ms
5 vwh1.dca.verio.net (129.250.30.167) 1 ms 1 ms 1 ms
6 wusezine.com (161.58.243.98) 1 ms 1 ms 1 ms
From Saint Louis
traceroute to altavista.com (209.73.164.91), 30 hops max, 40 byte packets
1 ge-6-0-1.mp1.Stlouis1.Level3.net (64.159.0.65) 1 ms 0 ms 0 ms
2 so-0-2-0.mp1.SanJose1.Level3.net (209.247.8.110) 61 ms 61 ms 61 ms
3 pos8-0.core2.SanJose1.Level3.net (209.247.11.6) 61 ms 61 ms 61 ms
4 gigaethernet6-1.ipcolo1.SanJose1.Level3.net (209.244.13.86) 61 ms 61 ms 61 ms
5 POS11-0.ipcolo3.SanJose1.Level3.net (209.244.13.58) 61 ms 61 ms 61 ms
6 64.152.64.6 (64.152.64.6) 83 ms 83 ms 83 ms
7 10.28.2.9 (10.28.2.9) 83 ms 83 ms 83 ms
8 altavista.com (209.73.164.91) 83 ms 83 ms 83 ms
traceroute to head-fi.org (161.58.243.98), 30 hops max, 40 byte packets
1 ge-6-0-1.mp2.Stlouis1.Level3.net (64.159.0.73) 1 ms 0 ms 0 ms
2 so-5-1-0.mp2.Chicago1.Level3.net (64.159.0.58) 6 ms 6 ms 6 ms
3 pos9-0.core2.Chicago1.Level3.net (209.247.10.174) 5 ms 5 ms 5 ms
4 p1-0-8.r00.chcgil01.us.bb.verio.net (129.250.9.9) 6 ms 6 ms 6 ms
5 p1-1-0.r00.mclnva02.us.bb.verio.net (129.250.4.17) 39 ms 39 ms 39 ms
6 vwh1.dca.verio.net (129.250.30.167) 39 ms 39 ms 39 ms
7 wusezine.com (161.58.243.98) 39 ms 39 ms 39 ms
From Cincinnati
traceroute to altavista.com (209.73.164.93), 30 hops max, 40 byte packets
1 ge-6-0-1.mp1.Cincinnati1.Level3.net (64.159.0.177) 1 ms 0 ms 0 ms
2 so-0-1-0.mp2.SanJose1.Level3.net (209.247.8.82) 72 ms 72 ms 72 ms
3 pos9-0.core1.SanJose1.Level3.net (209.247.11.10) 72 ms 72 ms 72 ms
4 gigaethernet9-0.ipcolo1.SanJose1.Level3.net (209.244.13.166) 72 ms 72 ms 72 ms
5 POS11-0.ipcolo3.SanJose1.Level3.net (209.244.13.58) 72 ms 72 ms 72 ms
6 64.152.64.6 (64.152.64.6) 89 ms 89 ms 89 ms
7 10.28.2.9 (10.28.2.9) 89 ms 89 ms 89 ms
8 altavista.com (209.73.164.93) 99 ms 98 ms 98 ms
traceroute to head-fi.org (161.58.243.98), 30 hops max, 40 byte packets
1 ge-6-0-1.mp1.Cincinnati1.Level3.net (64.159.0.177) 1 ms 0 ms 0 ms
2 so-5-0-0.mp1.Chicago1.Level3.net (64.159.0.162) 7 ms 7 ms 7 ms
3 pos8-0.core2.Chicago1.Level3.net (209.247.10.166) 7 ms 7 ms 6 ms
4 p1-0-8.r00.chcgil01.us.bb.verio.net (129.250.9.9) 7 ms 7 ms 7 ms
5 p1-1-0.r00.mclnva02.us.bb.verio.net (129.250.4.17) 31 ms 31 ms 31 ms
6 vwh1.dca.verio.net (129.250.30.167) 31 ms 31 ms 31 ms
7 wusezine.com (161.58.243.98) 32 ms 31 ms 32 ms
From Hong Kong
traceroute to altavista.com (209.73.180.8), 30 hops max, 40 byte packets
1 ge-0-3-0.mpls1.Hongkong1.Level3.net (210.57.2.129) 1 ms 0 ms 0 ms
2 at-7-1-0-284.mp1.LosAngeles1.Level3.net (209.244.19.10) 147 ms 150 ms 147 ms
3 so-0-1-0.mp1.NewYork1.Level3.net (209.247.8.9) 221 ms 221 ms 221 ms
4 pos8-0.core1.NewYork1.Level3.net (209.247.10.34) 221 ms 218 ms 218 ms
5 209.244.12.38 (209.244.12.38) 221 ms 221 ms 221 ms
6 209.246.123.66 (209.246.123.66) 221 ms 222 ms 221 ms
7 10.32.2.13 (10.32.2.13) 232 ms 219 ms 219 ms
8 altavista.com (209.73.180.8) 219 ms 219 ms 232 ms
traceroute to head-fi.org (161.58.243.98), 30 hops max, 40 byte packets
1 ge-7-1-0.mpls1.Hongkong1.Level3.net (210.57.2.193) 1 ms 0 ms 0 ms
2 at-7-0-0-285.mp1.LosAngeles1.Level3.net (209.244.19.18) 153 ms 153 ms 153 ms
3 so-0-1-0.mp2.SanJose1.Level3.net (209.247.8.82) 162 ms 162 ms 162 ms
4 pos9-0.core2.SanJose1.Level3.net (209.247.11.14) 162 ms 163 ms 162 ms
5 verio-level3-oc12.SanJose1.Level3.net (209.0.227.30) 162 ms 166 ms 165 ms
6 p4-7-2-0.r00.plalca01.us.bb.verio.net (129.250.3.117) 177 ms 177 ms 166 ms
7 p4-6-0-0.r02.mclnva02.us.bb.verio.net (129.250.2.246) 232 ms 232 ms 232 ms
8 vwh1.dca.verio.net (129.250.30.167) 229 ms 231 ms 230 ms
9 wusezine.com (161.58.243.98) 231 ms 230 ms 233 ms
From London
traceroute to 1 212.113.3.1 (212.113.3.1) 3 ms 2 ms 2 ms
2 loopback0.mp2.London1.Level3.net (212.113.2.12) 2 ms 2 ms 2 ms
3 altavista.com (209.73.164.92), 30 hops max, 40 byte packets
212.187.128.153 (212.187.128.153) 68 ms 68 ms 67 ms
4 so-0-2-0.mp1.SanJose1.Level3.net (209.247.8.110) 164 ms 164 ms 164 ms
5 pos8-0.core2.SanJose1.Level3.net (209.247.11.6) 164 ms 164 ms 164 ms
6 gigaethernet6-2.ipcolo1.SanJose1.Level3.net (209.244.13.94) 164 ms 164 ms 164 ms
7 POS11-0.ipcolo3.SanJose1.Level3.net (209.244.13.58) 164 ms 164 ms 164 ms
8 64.152.64.6 (64.152.64.6) 159 ms 159 ms 158 ms
9 10.28.2.9 (10.28.2.9) 159 ms 159 ms 159 ms
10 altavista.com (209.73.164.92) 150 ms 150 ms 150 ms
traceroute to head-fi.org (161.58.243.98), 30 hops max, 40 byte packets
1 212.113.3.2 (212.113.3.2) 2 ms 2 ms 2 ms
2 loopback0.mp2.London1.Level3.net (212.113.2.12) 2 ms 2 ms 2 ms
3 212.187.128.153 (212.187.128.153) 68 ms 68 ms 68 ms
4 pos9-0.core1.NewYork1.Level3.net (209.247.10.42) 68 ms 68 ms 67 ms
5 above-level3-oc3.nyc.above.net (209.244.160.182) 68 ms 68 ms 68 ms
6 p4-1-2-0.r00.nycmny01.us.bb.verio.net (129.250.4.65) 68 ms 68 ms 68 ms
7 p4-6-3-0.r00.nycmny06.us.bb.verio.net (129.250.4.50) 68 ms 68 ms 68 ms
8 p4-4-0-0.r01.mclnva02.us.bb.verio.net (129.250.3.182) 75 ms 74 ms 75 ms
9 vwh2.dca.verio.net (129.250.31.166) 74 ms 75 ms 74 ms
10 wusezine.com (161.58.243.98) 75 ms 75 ms 75 ms
From Paris
traceroute to altavista.com (209.73.164.93), 30 hops max, 40 byte packets
1 212.73.240.1 (212.73.240.1) 2 ms 1 ms 1 ms
2 so-1-0-0-0.mp2.London2.Level3.net (212.187.128.42) 7 ms 7 ms 7 ms
3 212.187.128.190 (212.187.128.190) 74 ms 74 ms 74 ms
4 so-0-2-0.mp1.SanJose1.Level3.net (209.247.8.110) 171 ms 171 ms 170 ms
5 pos8-0.core2.SanJose1.Level3.net (209.247.11.6) 171 ms 171 ms 171 ms
6 gigaethernet6-1.ipcolo1.SanJose1.Level3.net (209.244.13.86) 171 ms 171 ms 171 ms
7 POS11-0.ipcolo3.SanJose1.Level3.net (209.244.13.58) 171 ms 171 ms 170 ms
8 64.152.64.6 (64.152.64.6) 165 ms 165 ms 165 ms
9 Connection timed out - host may be temporarily unavailable.
traceroute to head-fi.org (161.58.243.98), 30 hops max, 40 byte packets
1 212.73.240.1 (212.73.240.1) 3 ms 1 ms 1 ms
2 so-1-0-0-0.mp2.London2.Level3.net (212.187.128.42) 7 ms 7 ms 7 ms
3 212.187.128.190 (212.187.128.190) 74 ms 74 ms 74 ms
4 pos8-0.core1.NewYork1.Level3.net (209.247.10.34) 74 ms 74 ms 74 ms
5 above-level3-oc3.nyc.above.net (209.244.160.182) 74 ms 74 ms 74 ms
6 p4-1-2-0.r00.nycmny01.us.bb.verio.net (129.250.4.65) 74 ms 74 ms 74 ms
7 p4-6-3-0.r00.nycmny06.us.bb.verio.net (129.250.4.50) 74 ms 74 ms 74 ms
8 p4-4-0-0.r01.mclnva02.us.bb.verio.net (129.250.3.182) 81 ms 81 ms 81 ms
9 vwh2.dca.verio.net (129.250.31.166) 81 ms 81 ms 82 ms
10 wusezine.com (161.58.243.98) 81 ms 82 ms 81 ms
Brussels
traceroute to altavista.com (209.73.164.93), 30 hops max, 40 byte packets
1 212.3.239.2 (212.3.239.2) 2 ms 2 ms 2 ms
2 so-2-0-0-0.mp2.London2.Level3.net (212.187.128.53) 6 ms 6 ms 6 ms
3 212.187.128.190 (212.187.128.190) 73 ms 73 ms 73 ms
4 so-0-2-0.mp1.SanJose1.Level3.net (209.247.8.110) 169 ms 170 ms 170 ms
5 pos8-0.core2.SanJose1.Level3.net (209.247.11.6) 170 ms 170 ms 170 ms
6 gigaethernet9-2.ipcolo1.SanJose1.Level3.net (209.244.13.186) 169 ms 170 ms 170 ms
7 POS11-0.ipcolo3.SanJose1.Level3.net (209.244.13.58) 169 ms 169 ms 169 ms
8 64.152.64.6 (64.152.64.6) 165 ms 164 ms 164 ms
9 10.28.2.9 (10.28.2.9) 164 ms 164 ms 164 ms
10 altavista.com (209.73.164.93) 155 ms 155 ms 155 ms
traceroute to head-fi.org (161.58.243.98), 30 hops max, 40 byte packets
1 212.3.239.2 (212.3.239.2) 2 ms 2 ms 2 ms
2 so-2-0-0-0.mp2.London2.Level3.net (212.187.128.53) 6 ms 6 ms 6 ms
3 212.187.128.190 (212.187.128.190) 73 ms 73 ms 73 ms
4 pos8-0.core1.NewYork1.Level3.net (209.247.10.34) 73 ms 73 ms 73 ms
5 above-level3-oc3.nyc.above.net (209.244.160.182) 73 ms 73 ms 73 ms
6 p4-1-2-0.r00.nycmny01.us.bb.verio.net (129.250.4.65) 73 ms 73 ms 73 ms
7 p4-6-3-0.r00.nycmny06.us.bb.verio.net (129.250.4.50) 73 ms 73 ms 73 ms
8 p4-4-0-0.r01.mclnva02.us.bb.verio.net (129.250.3.182) 80 ms 80 ms 80 ms
9 vwh2.dca.verio.net (129.250.31.166) 80 ms 80 ms 80 ms
10 wusezine.com (161.58.243.98) 80 ms 80 ms 80 ms
From Dallas
traceroute to altavista.com (209.73.164.92), 30 hops max, 40 byte packets
1 so-6-0-0.mp2.Dallas1.Level3.net (209.247.10.109) 1 ms 1 ms 1 ms
2 so-0-0-0.mp1.SanJose1.Level3.net (209.244.19.33) 45 ms 45 ms 45 ms
3 pos8-0.core2.SanJose1.Level3.net (209.247.11.6) 45 ms 45 ms 45 ms
4 gigaethernet9-2.ipcolo1.SanJose1.Level3.net (209.244.13.186) 45 ms 45 ms 45 ms
5 POS11-0.ipcolo3.SanJose1.Level3.net (209.244.13.58) 45 ms 45 ms 45 ms
6 64.152.64.6 (64.152.64.6) 76 ms 77 ms 76 ms
7 10.28.2.9 (10.28.2.9) 77 ms 77 ms 76 ms
8 altavista.com (209.73.164.92) 86 ms 86 ms 86 ms
traceroute to head-fi.org (161.58.243.98), 30 hops max, 40 byte packets
1 209.245.240.154 (209.245.240.154) 1 ms 1 ms 1 ms
2 p4-6-3-0.r02.dllstx01.us.bb.verio.net (129.250.5.3) 1 ms 1 ms 1 ms
3 p4-1-2-0.r00.stngva01.us.bb.verio.net (129.250.4.26) 37 ms 37 ms 37 ms
4 p16-7-0-0.r01.mclnva02.us.bb.verio.net (129.250.3.157) 37 ms 37 ms 37 ms
5 vwh2.dca.verio.net (129.250.31.166) 37 ms 37 ms 37 ms
6 wusezine.com (161.58.243.98) 37 ms 37 ms 37 ms
- Joined
- Jun 20, 2001
- Posts
- 11,025
- Likes
- 6,633
Quote:
Anyone else having the same problem as Rotareneg?
| Originally posted by Rotareneg Ouch! No wonder the site's so painfully hard to navigate! |
Anyone else having the same problem as Rotareneg?
raymondlin
Architect &Musical Fidelity X-Man v2
- Joined
- Jun 21, 2001
- Posts
- 3,109
- Likes
- 54
That made no Sense to me.
mbriant
Headphoneus Supremus
- Joined
- Jun 21, 2001
- Posts
- 9,537
- Likes
- 48
Could someone tell me what this all means? Is the the routing that the internet info takes to get from point a to point b?
bootman
King o'Ping
- Joined
- Jun 22, 2001
- Posts
- 3,308
- Likes
- 11
I'm good here.
C:\>tracert www.head-fi.org
Tracing route to head-fi.org [161.58.243.98]
over a maximum of 30 hops:
1 80 ms 70 ms 10 ms cr1-hfc6.vron1.nj.home.net [24.3.143.1]
2 60 ms 70 ms 120 ms bb1-fe4-4-100bt.rdc1.nj.home.net [24.3.144.1]
3 110 ms 20 ms 60 ms c1-pos4-1.nwrknj1.home.net [24.7.75.173]
4 100 ms 50 ms 21 ms c1-pos4-0.nycmny1.home.net[24.7.69.6]
5 310 ms 81 ms 50 ms p1-2-0.r01.nycmny01.us.bb.verio.net [129.250.9.145]
6 80 ms 40 ms 80 ms p4-1-2-0.r00.nycmny01.us.bb.verio.net [129.250.4.65]
7 70 ms 70 ms 30 ms p4-6-3-0.r00.nycmny06.us.bb.verio.net [129.250.4.50]
8 170 ms 110 ms 60 ms p4-4-0-0.r01.mclnva02.us.bb.verio.net [129.250.3.182]
9 91 ms 30 ms 90 ms vwh2.dca.verio.net [129.250.31.166]
10 100 ms 60 ms 51 ms wusezine.com [161.58.243.98]
Trace complete.
C:\>tracert www.head-fi.org
Tracing route to head-fi.org [161.58.243.98]
over a maximum of 30 hops:
1 80 ms 70 ms 10 ms cr1-hfc6.vron1.nj.home.net [24.3.143.1]
2 60 ms 70 ms 120 ms bb1-fe4-4-100bt.rdc1.nj.home.net [24.3.144.1]
3 110 ms 20 ms 60 ms c1-pos4-1.nwrknj1.home.net [24.7.75.173]
4 100 ms 50 ms 21 ms c1-pos4-0.nycmny1.home.net[24.7.69.6]
5 310 ms 81 ms 50 ms p1-2-0.r01.nycmny01.us.bb.verio.net [129.250.9.145]
6 80 ms 40 ms 80 ms p4-1-2-0.r00.nycmny01.us.bb.verio.net [129.250.4.65]
7 70 ms 70 ms 30 ms p4-6-3-0.r00.nycmny06.us.bb.verio.net [129.250.4.50]
8 170 ms 110 ms 60 ms p4-4-0-0.r01.mclnva02.us.bb.verio.net [129.250.3.182]
9 91 ms 30 ms 90 ms vwh2.dca.verio.net [129.250.31.166]
10 100 ms 60 ms 51 ms wusezine.com [161.58.243.98]
Trace complete.
Braver
Will upgrade headphoneswhen there's a MX600.
it looks like he got overall better pingtimes and shorter routes to head-fi.org than to altavista.
what this all basically shows, is the route a packet of info takes to get to your comp.
what this all basically shows, is the route a packet of info takes to get to your comp.
- Joined
- Jun 20, 2001
- Posts
- 11,025
- Likes
- 6,633
Rotareneg may have had a bad route to us last night (and still might).
I log in from remote servers periodically to check access time, and all has been well for me. Of course, if any of you have problems, puh-leeze do not hesitate to contact me or neil via e-mail or PM.
-- Jude --
I log in from remote servers periodically to check access time, and all has been well for me. Of course, if any of you have problems, puh-leeze do not hesitate to contact me or neil via e-mail or PM.
-- Jude --
bootman
King o'Ping
- Joined
- Jun 22, 2001
- Posts
- 3,308
- Likes
- 11
mbriant and raymondlin,
Here is an online tutorial on the trace route command (tracert)
http://www.useforesite.com/tut_tracert.shtml
Here is one form NASA: (a bit dry, btw)
http://cne.gsfc.nasa.gov/tcpipsvcs/n...etutorial.html
But to put it in simple terms, a trace route (a map of the path a packet takes from point "A" to point "B" and all of the devices ie. routers, in between) can tell you were in the chain lag or slowdowns occur. It is an essential troubleshooting tool to pinpoint internet connectivity problems.
I know its a lot to digest, but a good visual trace route program like neotrace or visualroute will give you a better understanding on what is really going on when you try to reach a site on the web.
Here is an online tutorial on the trace route command (tracert)
http://www.useforesite.com/tut_tracert.shtml
Here is one form NASA: (a bit dry, btw)
http://cne.gsfc.nasa.gov/tcpipsvcs/n...etutorial.html
But to put it in simple terms, a trace route (a map of the path a packet takes from point "A" to point "B" and all of the devices ie. routers, in between) can tell you were in the chain lag or slowdowns occur. It is an essential troubleshooting tool to pinpoint internet connectivity problems.
I know its a lot to digest, but a good visual trace route program like neotrace or visualroute will give you a better understanding on what is really going on when you try to reach a site on the web.
- Joined
- Jun 20, 2001
- Posts
- 11,025
- Likes
- 6,633
bootman,
Thanks for answering their questions. mbriant and raymondlin, I apologize for not answering your questions quicker.
Thanks for answering their questions. mbriant and raymondlin, I apologize for not answering your questions quicker.
bootman
King o'Ping
- Joined
- Jun 22, 2001
- Posts
- 3,308
- Likes
- 11
My pleasure.
BTW, did you do a trace back to Rotareneg?
It just seems to me that Verio.net was having a bad day.
BTW, did you do a trace back to Rotareneg?
It just seems to me that Verio.net was having a bad day.
raymondlin
Architect &Musical Fidelity X-Man v2
- Joined
- Jun 21, 2001
- Posts
- 3,109
- Likes
- 54
I have a Degree in Architecture and those numbers still make no sense! I need to sit down and read through it from the begining.
- Joined
- Jun 20, 2001
- Posts
- 11,025
- Likes
- 6,633
Quote:
raymondlin,
For example, take the following:
----------
traceroute to altavista.com (209.73.164.94), 30 hops max, 40 byte packets
1 gigaethernet9-2.ipcolo1.SanJose1.Level3.net (209.244.13.186) 1 ms 0 ms 1 ms
2 POS11-0.ipcolo3.SanJose1.Level3.net (209.244.13.58) 0 ms 0 ms 0 ms
3 64.152.64.6 (64.152.64.6) 83 ms 83 ms 86 ms
4 10.28.2.9 (10.28.2.9) 83 ms 83 ms 83 ms
5 altavista.com (209.73.164.94) 84 ms 83 ms 83 ms
traceroute to head-fi.org (161.58.243.98), 30 hops max, 40 byte packets
1 verio-level3-oc12.SanJose1.Level3.net (209.0.227.30) 1 ms 1 ms 1 ms
2 p4-7-2-0.r00.plalca01.us.bb.verio.net (129.250.3.117) 2 ms 2 ms 2 ms
3 p4-6-0-0.r02.mclnva02.us.bb.verio.net (129.250.2.246) 92 ms 92 ms 92 ms
4 vwh1.dca.verio.net (129.250.30.167) 92 ms 92 ms 92 ms
5 wusezine.com (161.58.243.98) 92 ms 93 ms 92 ms
----------
Those are two different traceroutes, both originating from Level3's San Jose facility, one with the end destination at altavista.com, the other with the destination at head-fi.org. If you look at the first number in each line (unless it's wrapping for you), you'll notice that there is a 1, 2, 3, 4, or 5 beginning each line. The "1" represents the first "hop." The "2" represents the second "hop," and so on. For each of the two -- to get from Level3 San Jose to both Altavista and Head-Fi -- it took five total hops. So, for example, this is the first hope to Head-Fi from Level3 San Jose:
1 verio-level3-oc12.SanJose1.Level3.net (209.0.227.30) 1 ms 1 ms 1 ms
The "1" means the first hop. The next is the server name/dns. And then the last numbers represent the latency in ms (lower means faster).
The topmost line in each just gives the information about what's being sent:
traceroute to head-fi.org (161.58.243.98), 30 hops max, 40 byte packets
This says it's doing a traceroute to head-fi.org (which is at 161.58.243.98); the traceroute is limited to 30 hops maximum (it only took five for each in this case), using 40-byte packets.
I may not be explaining this 100% correctly, but if there are corrections to be made, I'm sure someone will step in.
| Originally posted by raymondlin I have a Degree in Architecture and those numbers still make no sense! I need to sit down and read through it from the begining. |
raymondlin,
For example, take the following:
----------
traceroute to altavista.com (209.73.164.94), 30 hops max, 40 byte packets
1 gigaethernet9-2.ipcolo1.SanJose1.Level3.net (209.244.13.186) 1 ms 0 ms 1 ms
2 POS11-0.ipcolo3.SanJose1.Level3.net (209.244.13.58) 0 ms 0 ms 0 ms
3 64.152.64.6 (64.152.64.6) 83 ms 83 ms 86 ms
4 10.28.2.9 (10.28.2.9) 83 ms 83 ms 83 ms
5 altavista.com (209.73.164.94) 84 ms 83 ms 83 ms
traceroute to head-fi.org (161.58.243.98), 30 hops max, 40 byte packets
1 verio-level3-oc12.SanJose1.Level3.net (209.0.227.30) 1 ms 1 ms 1 ms
2 p4-7-2-0.r00.plalca01.us.bb.verio.net (129.250.3.117) 2 ms 2 ms 2 ms
3 p4-6-0-0.r02.mclnva02.us.bb.verio.net (129.250.2.246) 92 ms 92 ms 92 ms
4 vwh1.dca.verio.net (129.250.30.167) 92 ms 92 ms 92 ms
5 wusezine.com (161.58.243.98) 92 ms 93 ms 92 ms
----------
Those are two different traceroutes, both originating from Level3's San Jose facility, one with the end destination at altavista.com, the other with the destination at head-fi.org. If you look at the first number in each line (unless it's wrapping for you), you'll notice that there is a 1, 2, 3, 4, or 5 beginning each line. The "1" represents the first "hop." The "2" represents the second "hop," and so on. For each of the two -- to get from Level3 San Jose to both Altavista and Head-Fi -- it took five total hops. So, for example, this is the first hope to Head-Fi from Level3 San Jose:
1 verio-level3-oc12.SanJose1.Level3.net (209.0.227.30) 1 ms 1 ms 1 ms
The "1" means the first hop. The next is the server name/dns. And then the last numbers represent the latency in ms (lower means faster).
The topmost line in each just gives the information about what's being sent:
traceroute to head-fi.org (161.58.243.98), 30 hops max, 40 byte packets
This says it's doing a traceroute to head-fi.org (which is at 161.58.243.98); the traceroute is limited to 30 hops maximum (it only took five for each in this case), using 40-byte packets.
I may not be explaining this 100% correctly, but if there are corrections to be made, I'm sure someone will step in.
chych
The butter knife's second victim.
- Joined
- Jun 21, 2001
- Posts
- 1,985
- Likes
- 13
Hmm, I dunno about you, but my pipe to head-fi.org is just fine...
My trace routes: (skip the first hop, thats my router)
From Woodbridge, CT:
www.head-fi.org
Average of 10 pings: 21 ms
<traceroute:161.58.243.98> www.head-fi.org
Hop Sent Received Seconds IP Address Name
1 YYY YYY 0.014 10.135.128.1 No host name found.
2 YYY YYY 0.011 167.206.254.145 r1-fe6-3.bb.nrwlct.cv.net
3 YYY YYY 0.015 167.206.108.241 r2-pos8-0-622m.bb.hcvlny.cv.net
4 YYY YYY 0.015 167.206.13.21 r1-ge12-0.in.hcvlny.cv.net
5 YYY YYY 0.016 157.130.92.177 pos3-0.gw8.nyc1.alter.net
6 YYY YYY 0.016 152.63.9.2 0.so-7-0-0.xr4.nyc1.alter.net
7 YYY YYY 0.016 152.63.27.225 208.at-2-0-0.xr2.nyc9.alter.net
8 YYY YYY 0.017 152.63.23.141 0.so-2-1-0.xl2.nyc9.alter.net
9 YYY YYY 0.017 152.63.22.229 pos7-0.br2.nyc9.alter.net
10 YYY YYY 0.017 129.250.9.165 a3-6-0-1.r01.nycmny01.us.bb.verio.net
11 YYY YYY 0.018 129.250.4.210 p4-2-1-0.r01.nycmny06.us.bb.verio.net
12 YYY YYY 0.017 129.250.3.129 p4-1-3-0.r00.nycmny06.us.bb.verio.net
13 YYY YYY 0.024 129.250.3.182 p4-4-0-0.r01.mclnva02.us.bb.verio.net
14 YYY YYY 0.021 129.250.31.166 vwh2.dca.verio.net
15 YYY YYY 0.029 161.58.243.98 wusezine.com
www.altavista.com
Average of 10 pings: 14 ms
<traceroute:209.73.164.91> www.altavista.com
Hop Sent Received Seconds IP Address Name
1 YYY YYY 0.014 10.135.128.1 No host name found.
2 YYY YYY 0.012 167.206.254.145 r1-fe6-3.bb.nrwlct.cv.net
3 YYY YYY 0.015 167.206.108.241 r2-pos8-0-622m.bb.hcvlny.cv.net
4 YYY YYY 0.015 167.206.13.21 r1-ge12-0.in.hcvlny.cv.net
5 YYY YYY 0.015 157.130.61.161 pos2-3.gw8.nyc1.alter.net
6 YYY YYY 0.015 152.63.9.2 0.so-7-0-0.xr4.nyc1.alter.net
7 YYY YYY 0.015 152.63.27.229 308.at-1-0-0.xr2.nyc9.alter.net
8 YYY YYY 0.016 152.63.23.141 0.so-2-1-0.xl2.nyc9.alter.net
9 YYY YYY 0.016 152.63.22.229 pos7-0.br2.nyc9.alter.net
10 YYY YYY 0.017 209.244.160.161 atm4-0-1.core2.newyork1.level3.net
11 YYY YYY 0.016 209.247.10.37 so-6-0-0.mp1.newyork1.level3.net
12 YYY YYY 0.11 209.247.8.110 so-0-2-0.mp1.sanjose1.level3.net
13 YYY YYY 0.11 209.247.11.6 pos8-0.core2.sanjose1.level3.net
14 YYY YYY 0.11 209.244.13.94 gigaethernet6-2.ipcolo1.sanjose1.level3.net
15 YYY YYY 0.11 209.244.13.58 pos11-0.ipcolo3.sanjose1.level3.net
16 YYY YYY 0.096 64.152.64.6 64.152.64.6
17 YYY YYY 0.098 10.28.2.9 No host name found.
18 YYY YYY 0.096 209.73.164.91 altavista.com
Sheesh, I'm so far from these servers...
My trace routes: (skip the first hop, thats my router)
From Woodbridge, CT:
www.head-fi.org
Average of 10 pings: 21 ms
<traceroute:161.58.243.98> www.head-fi.org
Hop Sent Received Seconds IP Address Name
1 YYY YYY 0.014 10.135.128.1 No host name found.
2 YYY YYY 0.011 167.206.254.145 r1-fe6-3.bb.nrwlct.cv.net
3 YYY YYY 0.015 167.206.108.241 r2-pos8-0-622m.bb.hcvlny.cv.net
4 YYY YYY 0.015 167.206.13.21 r1-ge12-0.in.hcvlny.cv.net
5 YYY YYY 0.016 157.130.92.177 pos3-0.gw8.nyc1.alter.net
6 YYY YYY 0.016 152.63.9.2 0.so-7-0-0.xr4.nyc1.alter.net
7 YYY YYY 0.016 152.63.27.225 208.at-2-0-0.xr2.nyc9.alter.net
8 YYY YYY 0.017 152.63.23.141 0.so-2-1-0.xl2.nyc9.alter.net
9 YYY YYY 0.017 152.63.22.229 pos7-0.br2.nyc9.alter.net
10 YYY YYY 0.017 129.250.9.165 a3-6-0-1.r01.nycmny01.us.bb.verio.net
11 YYY YYY 0.018 129.250.4.210 p4-2-1-0.r01.nycmny06.us.bb.verio.net
12 YYY YYY 0.017 129.250.3.129 p4-1-3-0.r00.nycmny06.us.bb.verio.net
13 YYY YYY 0.024 129.250.3.182 p4-4-0-0.r01.mclnva02.us.bb.verio.net
14 YYY YYY 0.021 129.250.31.166 vwh2.dca.verio.net
15 YYY YYY 0.029 161.58.243.98 wusezine.com
www.altavista.com
Average of 10 pings: 14 ms
<traceroute:209.73.164.91> www.altavista.com
Hop Sent Received Seconds IP Address Name
1 YYY YYY 0.014 10.135.128.1 No host name found.
2 YYY YYY 0.012 167.206.254.145 r1-fe6-3.bb.nrwlct.cv.net
3 YYY YYY 0.015 167.206.108.241 r2-pos8-0-622m.bb.hcvlny.cv.net
4 YYY YYY 0.015 167.206.13.21 r1-ge12-0.in.hcvlny.cv.net
5 YYY YYY 0.015 157.130.61.161 pos2-3.gw8.nyc1.alter.net
6 YYY YYY 0.015 152.63.9.2 0.so-7-0-0.xr4.nyc1.alter.net
7 YYY YYY 0.015 152.63.27.229 308.at-1-0-0.xr2.nyc9.alter.net
8 YYY YYY 0.016 152.63.23.141 0.so-2-1-0.xl2.nyc9.alter.net
9 YYY YYY 0.016 152.63.22.229 pos7-0.br2.nyc9.alter.net
10 YYY YYY 0.017 209.244.160.161 atm4-0-1.core2.newyork1.level3.net
11 YYY YYY 0.016 209.247.10.37 so-6-0-0.mp1.newyork1.level3.net
12 YYY YYY 0.11 209.247.8.110 so-0-2-0.mp1.sanjose1.level3.net
13 YYY YYY 0.11 209.247.11.6 pos8-0.core2.sanjose1.level3.net
14 YYY YYY 0.11 209.244.13.94 gigaethernet6-2.ipcolo1.sanjose1.level3.net
15 YYY YYY 0.11 209.244.13.58 pos11-0.ipcolo3.sanjose1.level3.net
16 YYY YYY 0.096 64.152.64.6 64.152.64.6
17 YYY YYY 0.098 10.28.2.9 No host name found.
18 YYY YYY 0.096 209.73.164.91 altavista.com
Sheesh, I'm so far from these servers...
Rotareneg
Internetus Quickus
- Joined
- Jun 25, 2001
- Posts
- 252
- Likes
- 10
It's back to normal, must have been really bad luck.
Tracing route to head-fi.org [161.58.243.98]
over a maximum of 30 hops:
1 9 ms 10 ms 8 ms 10.134.8.1
2 11 ms 10 ms 9 ms 24.94.192.153
3 30 ms 16 ms 17 ms 24.94.192.134
4 14 ms 15 ms 26 ms 24.218.189.132
5 49 ms 48 ms 66 ms acr1-serial3-1-0-0.Dallasdan.cw.net [208.172.131.149]
6 42 ms 40 ms 40 ms cable-and-wireless-peering.Dallasdan.cw.net [208.172.131.214]
7 40 ms 39 ms 42 ms p4-6-3-0.r02.dllstx01.us.bb.verio.net [129.250.5.3]
8 58 ms 59 ms 58 ms p4-1-2-0.r00.stngva01.us.bb.verio.net [129.250.4.26]
9 104 ms 106 ms 106 ms p16-7-0-0.r01.mclnva02.us.bb.verio.net [129.250.3.157]
10 63 ms 65 ms 62 ms vwh2.dca.verio.net [129.250.31.166]
11 62 ms 66 ms 75 ms head-fi.org [161.58.243.98]
Trace complete.
Tracing route to head-fi.org [161.58.243.98]
over a maximum of 30 hops:
1 9 ms 10 ms 8 ms 10.134.8.1
2 11 ms 10 ms 9 ms 24.94.192.153
3 30 ms 16 ms 17 ms 24.94.192.134
4 14 ms 15 ms 26 ms 24.218.189.132
5 49 ms 48 ms 66 ms acr1-serial3-1-0-0.Dallasdan.cw.net [208.172.131.149]
6 42 ms 40 ms 40 ms cable-and-wireless-peering.Dallasdan.cw.net [208.172.131.214]
7 40 ms 39 ms 42 ms p4-6-3-0.r02.dllstx01.us.bb.verio.net [129.250.5.3]
8 58 ms 59 ms 58 ms p4-1-2-0.r00.stngva01.us.bb.verio.net [129.250.4.26]
9 104 ms 106 ms 106 ms p16-7-0-0.r01.mclnva02.us.bb.verio.net [129.250.3.157]
10 63 ms 65 ms 62 ms vwh2.dca.verio.net [129.250.31.166]
11 62 ms 66 ms 75 ms head-fi.org [161.58.243.98]
Trace complete.
Users who are viewing this thread
