O Canada! > Canadian > Bell Canada > Bell messes up routing to Chicago AGAIN?

Bell messes up routing to Chicago AGAIN?

Just checked and it seems so. But I also noticed the worst ping is from pc to router! Time to tweak something.

reply to 63353372
1 1 ms 1 ms 1 ms 192.168.2.1
2 8 ms 8 ms 8 ms 64.230.254.65
3 6 ms 6 ms 6 ms HSE-Sherbrooke-ppp98704.qc.sympatico.ca [64.230.222.97]
4 6 ms 5 ms 5 ms 64.230.240.57
5 6 ms 6 ms 6 ms 64.230.240.50
6 6 ms 6 ms 5 ms if-1-0.core1.Montreal.Teleglobe.net [207.45.204.1]
7 19 ms 19 ms 19 ms if-6-0.core1.Newark.Teleglobe.net [64.86.84.185]
8 18 ms 18 ms 18 ms if-5-0.core2.Ashburn.Teleglobe.net [66.110.8.17]
9 18 ms 18 ms 19 ms so-1-2-0.e1.Washington1.Level3.net [65.59.88.209]
10 19 ms 19 ms 19 ms so-2-1-0.bbr2.Washington1.Level3.net [209.244.11.13]
11 35 ms 34 ms 35 ms so-0-0-0.bbr2.Chicago1.Level3.net [209.247.10.129]
12 34 ms 34 ms 35 ms so-5-0.ipcolo2.Chicago1.Level3.net [4.68.112.210]
13 36 ms 35 ms 35 ms unknown.Level3.net [166.90.208.206]
14 36 ms 35 ms 35 ms dns.chi1.speakeasy.net [64.81.159.2]

nope.

reply to 63353372
Tracing route to oops.EOF.com [207.88.53.7]
over a maximum of 30 hops:

1 8 ms 9 ms 7 ms 64.230.254.206
2 6 ms 6 ms 6 ms 64.230.239.237
3 6 ms 6 ms 7 ms 64.230.240.234
4 8 ms 8 ms 8 ms 64.230.242.54
5 8 ms 8 ms 8 ms 64.230.242.93
6 51 ms 51 ms 51 ms core2-chicago23-pos0-0.in.bellnexxia.net [206.10
8.103.114]
7 51 ms 52 ms 51 ms bx1-chicago23-pos11-0.in.bellnexxia.net [206.108
.103.125]
8 51 ms 51 ms 51 ms p5-2.IR1.Chicago2-IL.us.xo.net [207.88.50.173]
9 51 ms 52 ms 51 ms p5-0-0.RAR1.Chicago-IL.us.xo.net [65.106.6.133]

10 52 ms 52 ms 52 ms ge1-0.DCR1.DC-Chicago-IL.us.xo.net [64.220.0.195
]
11 52 ms 52 ms 52 ms ge1-1.CDR1.DC-Chicago-IL.us.xo.net [66.89.0.2]
12 52 ms 52 ms 52 ms oops.EOF.com [207.88.53.7]

Was just 18-20 ping yesterday....

reply to 63353372

Tracing the route to chi.speakeasy.net (64.81.159.2)

  1 dis40-toronto63-fe5-0-0.in.bellnexxia.net (205.207.238.210) 0 msec 0 msec 0 msec
  2 core1-toronto63-pos11-5.in.bellnexxia.net (206.108.98.21) 0 msec 0 msec 0 msec
  3 core3-toronto63-pos0-1.in.bellnexxia.net (64.230.242.93) 0 msec 0 msec 4 msec
  4 bx1-toronto63-pos1-0.in.bellnexxia.net (64.230.242.114) 0 msec 0 msec 0 msec
  5 if-7-0.core2.Scarborough.Teleglobe.net (207.45.198.1) [AS 6453] 4 msec 0 msec 0 msec
  6 if-4-0.core1.Scarborough.Teleglobe.net (207.45.222.205) [AS 6453] 28 msec 24 msec 24 m sec
  7 if-8-0.core2.NewYork.Teleglobe.net (64.86.80.221) [AS 6453] 24 msec 24 msec 24 msec
  8 if-9-0.core1.Newark.Teleglobe.net (207.45.223.81) [AS 6453] 20 msec 20 msec 20 msec
  9 if-5-0.core2.Ashburn.Teleglobe.net (66.110.8.17) 24 msec 24 msec 24 msec
 10 so-1-2-0.e1.Washington1.Level3.net (65.59.88.209) 44 msec 44 msec 48 msec
 11 so-2-1-0.bbr2.Washington1.Level3.net (209.244.11.13) 44 msec 44 msec 48 msec
 12 so-0-0-0.bbr2.Chicago1.Level3.net (209.247.10.129) [AS 3356] 40 msec 40 msec 40 msec
 13 so-5-0.ipcolo2.Chicago1.Level3.net (4.68.112.210) [AS 3356] 40 msec 44 msec 40 msec
 14 unknown.Level3.net (166.90.208.206) [AS 3356] 40 msec 40 msec 44 msec
 15 chi.speakeasy.net (64.81.159.2) [AS 23504] 40 msec 44 msec 40 msec


Tracing the route to oops.EOF.com (207.88.53.7)

  1 dis40-toronto63-fe5-0-0.in.bellnexxia.net (205.207.238.210) 0 msec 0 msec 0 msec
  2 core2-toronto63-pos11-5.in.bellnexxia.net (206.108.98.141) 0 msec 0 msec 0 msec
  3 core3-toronto63-pos6-0.in.bellnexxia.net (64.230.242.101) 0 msec 0 msec 0 msec
  4 core2-chicago23-pos0-0.in.bellnexxia.net (206.108.103.114) 44 msec 44 msec 44 msec
  5 bx1-chicago23-pos11-0.in.bellnexxia.net (206.108.103.125) 44 msec 40 msec 44 msec
  6 p5-2.IR1.Chicago2-IL.us.xo.net (207.88.50.173) [AS 2828] 44 msec 44 msec 48 msec
  7 p5-0-0.RAR1.Chicago-IL.us.xo.net (65.106.6.133) [AS 2828] 44 msec 44 msec 44 msec
  8 ge1-0.DCR1.DC-Chicago-IL.us.xo.net (64.220.0.195) [AS 2828] 44 msec 44 msec 44 msec
  9 ge1-1.CDR2.DC-Chicago-IL.us.xo.net (66.89.0.10) [AS 2828] 48 msec 44 msec 44 msec
 10 oops.EOF.com (207.88.53.7) [AS 2828] 44 msec 44 msec 44 msec

reply to 63353372
1 1 ms 1 ms 1 ms 192.168.2.1
2 7 ms 7 ms 17 ms 64.230.254.65
3 6 ms 6 ms 6 ms HSE-Sherbrooke-ppp98704.qc.sympatico.ca [64.230.
4 6 ms 6 ms 5 ms 64.230.240.57
5 14 ms 13 ms 13 ms 64.230.240.78
6 14 ms 13 ms 13 ms bx3-newyork83-pos1-0.in.bellnexxia.net [206.108.
7 14 ms 14 ms 14 ms p4-3.IR1.NYC-NY.us.xo.net [206.111.13.17]
8 14 ms 14 ms 14 ms p5-0-0.RAR2.NYC-NY.us.xo.net [65.106.3.41]
9 73 ms 32 ms 19 ms p6-0-0.RAR1.Washington-DC.us.xo.net [65.106.0.2]
10 19 ms 19 ms 18 ms p0-0-0d0.RAR2.Washington-DC.us.xo.net [65.106.1.
11 46 ms 47 ms 47 ms p11-0.DCR2.DC-Chicago-IL.us.xo.net [65.106.2.142
12 48 ms 47 ms 47 ms ge1-2.CDR2.DC-Chicago-IL.us.xo.net [66.89.0.14]
13 48 ms 47 ms 50 ms oops.EOF.com [207.88.53.7]

hmm i ts just a bad serv
cause the other chi servs i know are fine.

said by rewket:

---

1 1 ms 1 ms 1 ms 192.168.2.1
2 7 ms 7 ms 17 ms 64.230.254.65
3 6 ms 6 ms 6 ms HSE-Sherbrooke-ppp98704.qc.sympatico.ca [64.230.
4 6 ms 6 ms 5 ms 64.230.240.57
5 14 ms 13 ms 13 ms 64.230.240.78
6 14 ms 13 ms 13 ms bx3-newyork83-pos1-0.in.bellnexxia.net [206.108.
7 14 ms 14 ms 14 ms p4-3.IR1.NYC-NY.us.xo.net [206.111.13.17]
8 14 ms 14 ms 14 ms p5-0-0.RAR2.NYC-NY.us.xo.net [65.106.3.41]
9 73 ms 32 ms 19 ms p6-0-0.RAR1.Washington-DC.us.xo.net [65.106.0.2]
10 19 ms 19 ms 18 ms p0-0-0d0.RAR2.Washington-DC.us.xo.net [65.106.1.
11 46 ms 47 ms 47 ms p11-0.DCR2.DC-Chicago-IL.us.xo.net [65.106.2.142
12 48 ms 47 ms 47 ms ge1-2.CDR2.DC-Chicago-IL.us.xo.net [66.89.0.14]
13 48 ms 47 ms 50 ms oops.EOF.com [207.88.53.7]

hmm i ts just a bad serv
cause the other chi servs i know are fine.

---

reply to 63353372
im having the exact same problem with mine in durham region, i hope they change the routing back soon

reply to 63353372
also all my routing to american servers are going through chicago, which is 50 ms to start + additional hops, i hope they fix this soon

reply to 63353372
Wierd, I'm getting about 45ms ping to chi.speakeasy.net as well... but then I've never pinged to Chicago before, so I don't know if it was always like that.

reply to 63353372
wassup rewket, you pimp. routing issues are usually nothing more then pure congestion on the network somewhere. Easiest way around it... there is no way around it deal with it and move on. If the jump was at your first hop you could do something about it, otherwise your sol.

reply to Sean
All of Bells routing has been done through their Chicago router in the past. This is why it's been said that Sympatico is a good gaming ISP for low latency to central U.S servers. I remember distinctively being 16 ms to chi.speakeasy.net

Good work Bell.

reply to 63353372
1 9 ms 9 ms 9 ms 64.230.254.108
2 7 ms 7 ms 7 ms dis10-toronto12-Vlan101.in.bellnexxia.net [64.230.234.25]
3 8 ms 7 ms 8 ms core3-toronto12-Gigabite4-0.in.bellnexxia.net [206.108.107.213]
4 18 ms 19 ms 19 ms core2-chicago23-pos10-0.in.bellnexxia.net [206.108.103.118]
5 18 ms 18 ms 18 ms bx1-chicago23-pos11-0.in.bellnexxia.net [206.108.103.125]
6 19 ms 19 ms 19 ms p5-2.IR1.Chicago2-IL.us.xo.net [207.88.50.173]
7 19 ms 19 ms 19 ms p5-0-0.RAR1.Chicago-IL.us.xo.net [65.106.6.133]
8 19 ms 19 ms 19 ms ge1-0.DCR1.DC-Chicago-IL.us.xo.net [64.220.0.195]
9 19 ms 19 ms 21 ms ge1-1.CDR1.DC-Chicago-IL.us.xo.net [66.89.0.2]
10 20 ms 20 ms 19 ms oops.EOF.com [207.88.53.7]

no probs here

reply to 63353372
seems to be fixed ;]

Yea it looks like there was just a problem with their router.