jeffster2k
join:2004-11-13
| Chicago bellnexxia routers again?
Hey,
I'm a new sympatico subscriber and I've been getting some pretty bad packet loss to my dedicated server in florida. After some troubleshooting, I've narrowed the problem down to a couple of routers in the Chicago area. I notice the same group of routers were a problem a couple of years ago, and I'm wondering if anyone else is noticing the same problems. I don't see any of them on the bad routers page, but I'm pretty sure that's because the line test doesn't use that route. I've disconnected and reconnected my modem, getting 3 different class A ip blocks, but no matter what, I still go through the chicago routing. To give you an indication of how bad it is, I get 95-98% packet loss from this specific router:
206.108.108.218
It doesn't even have a hostname. Anyone else notice a problem with this router? If possible, could someone do a traceroute to www.sagonet.com and see if you're encountering the same router? If you are, could you do a pathping -n www.sagonet.com? I know this takes a few mins of your time but I'd be grateful for any help. Also, do you know of any way to resolve issues like this? I can't imagine emailing or calling them would help.
Thanks,
Jeff |
|
my3cents4
join:2004-06-19
Ottawa, ON
| Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\tracert www.sagonet.com
Tracing route to sagonet.com [66.118.128.5]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.2.1
2 8 ms 7 ms 7 ms 64.230.254.47
3 7 ms 6 ms 6 ms 64.230.228.45
4 6 ms 6 ms 6 ms 64.230.241.221
5 12 ms 12 ms 12 ms core2-toronto63-pos1-0.in.bellnexxia.net [64.230
.229.25]
6 12 ms 12 ms 12 ms 64.230.242.105
7 23 ms 23 ms 23 ms core1-chicago23-pos0-0.in.bellnexxia.net [206.10
8.103.130]
8 23 ms 22 ms 23 ms bx2-chicago23-pos11-0.in.bellnexxia.net [206.108
.103.138]
9 23 ms 23 ms 23 ms 206.108.108.218
10 71 ms 71 ms 71 ms so1-0-0-2488M.ar2.TPA1.gblx.net [67.17.66.169]
11 * * 119 ms ExpedientSago-NetworksDashboard-Communications.g
e-2-0-0.ar2.TPA1.gblx.net [64.215.80.66]
12 72 ms 71 ms 71 ms gi0-49.ds03.tpa.sagonet.net [65.110.32.10]
13 71 ms 66 ms 65 ms nazgul.sagonet.com [66.118.128.5]
Trace complete.
C:\Documents and Settings\
not much there from downtown ottawa things go up outside the bell network, not much can be done about that |
|
Kringle
Dr.D
Premium
join:2004-02-27
Pierrefonds, QC
 ·Bell Sympatico
| reply to jeffster2k
said by jeffster2k  :
If possible, could someone do a traceroute to www.sagonet.com
The router I'm having trouble with is a Global Crossings router. I've run into situations before where they caused me grief (even routing to Ireland to get from Montreal to New York). Here's what I got as an average of about 50 pings:
|
|
jeffster2k
join:2004-11-13
| Check my output from pathping -n www.sagonet.com:
Tracing route to sagonet.com [66.118.128.5]
over a maximum of 30 hops:
0 192.168.1.101
1 192.168.1.1
2 64.230.254.109
3 64.230.234.29
4 64.230.221.105
5 206.108.103.118
6 206.108.103.122
7 206.108.108.218
8 67.17.66.169
9 64.215.80.66
10 65.110.32.10
11 66.118.128.5
Computing statistics for 275 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 192.168.1.101
0/ 100 = 0% |
1 7ms 0/ 100 = 0% 0/ 100 = 0% 192.168.1.1
0/ 100 = 0% |
2 22ms 0/ 100 = 0% 0/ 100 = 0% 64.230.254.109
1/ 100 = 1% |
3 17ms 1/ 100 = 1% 0/ 100 = 0% 64.230.234.29
1/ 100 = 1% |
4 17ms 2/ 100 = 2% 0/ 100 = 0% 64.230.221.105
0/ 100 = 0% |
5 28ms 2/ 100 = 2% 0/ 100 = 0% 206.108.103.118
0/ 100 = 0% |
6 28ms 2/ 100 = 2% 0/ 100 = 0% 206.108.103.122
3/ 100 = 3% |
7 --- 100/ 100 =100% 95/ 100 = 95% 206.108.108.218
0/ 100 = 0% |
8 --- 100/ 100 =100% 95/ 100 = 95% 67.17.66.169
0/ 100 = 0% |
9 86ms 41/ 100 = 41% 36/ 100 = 36% 64.215.80.66
0/ 100 = 0% |
10 77ms 5/ 100 = 5% 0/ 100 = 0% 65.110.32.10
1/ 100 = 1% |
11 77ms 6/ 100 = 6% 0/ 100 = 0% 66.118.128.5
Trace complete.
Obviously there is something wrong here no?
Jeff |
|
jeffster2k
join:2004-11-13 | Nobody else notice this? |
|
dirtyjeffer
Lest We Forget
Premium
join:2002-02-21
London, ON
 ·Rogers Hi-Speed
| said by jeffster2k :Nobody else notice this? yes, but by the looks of the tracerts, it isn't Bell Nexxia's problem...it is something with sagonet.
--
"The only thing more greedy than a corporation, are its customers." |
|
Dustyn
Premium
join:2003-02-26
Ontario, CAN | reply to jeffster2k
»dis10-toronto12-Gigabite1-1.in.bellnexxia.net |
|
micron06
Premium
join:2003-11-19
York Region
| reply to jeffster2k
From home connection:
Tracing route to sagonet.com [66.118.128.5]
over a maximum of 30 hops:
1 2 ms 2 ms 3 ms 10.9.8.7
2 11 ms 13 ms 16 ms 64.230.254.220
3 9 ms 9 ms 10 ms dis3-stcatharines10-Vlan102.in.bellnexxia.net [64.230.232.21]
4 9 ms 9 ms 9 ms core3-stcatharines10-Gigabite4-1.in.bellnexxia.net [64.230.232.45]
5 11 ms 12 ms 12 ms core1-toronto12-pos5-1.in.bellnexxia.net [64.230.234.117]
6 12 ms 12 ms 12 ms 64.230.242.197
7 22 ms 22 ms 22 ms core1-chicago23-pos10-0.in.bellnexxia.net [206.108.103.134]
8 22 ms 22 ms 23 ms bx2-chicago23-pos11-0.in.bellnexxia.net [206.108.103.138]
9 22 ms 22 ms 22 ms 206.108.108.218
10 71 ms 71 ms 71 ms so1-0-0-2488M.ar2.TPA1.gblx.net [67.17.66.169]
11 71 ms 71 ms * ExpedientSago-NetworksDashboard-Communications.ge-2-0-0.ar2.TPA1.gbl
x.net [64.215.80.66]
12 71 ms 70 ms 71 ms gi0-49.ds03.tpa.sagonet.net [65.110.32.10]
13 71 ms 72 ms 71 ms nazgul.sagonet.com [66.118.128.5]
Trace complete.
From my box in chicago:
traceroute to sagonet.com (66.118.128.5), 30 hops max, 38 byte packets
1 66.90.82.1 (66.90.82.1) 0.477 ms 1.372 ms 0.383 ms
2 209.120.155.13 (209.120.155.13) 0.566 ms 0.506 ms 0.534 ms
3 4.79.72.41 (4.79.72.41) 0.773 ms 0.920 ms 0.842 ms
4 so-3-3-0.bbr2.Chicago1.Level3.net (4.68.96.49) 0.933 ms 0.765 ms 0.825 ms
5 so-2-0-0.mp1.Tampa1.Level3.net (209.247.11.201) 51.754 ms 37.557 ms 36.872 ms
6 so-6-0-0.gar1.Tampa1.Level3.net (4.68.124.10) 37.148 ms 37.231 ms 36.849 ms
7 * * 4.79.172.2 (4.79.172.2) 37.596 ms
8 gi0-49.ds03.tpa.sagonet.net (65.110.32.10) 69.309 ms 38.011 ms 37.942 ms
9 * * *
10 * * *
11 * * * |
|
