Bell customers should notice that pings have improved significantly over what they have been seeing the past few days on our new primary server. The issue was a routing problem caused by Bell, and was never a problem with the quality, or configuration of the server.
I’m pleased with the new GSP’s ability to track down the issue, and get the ISP to take action. It would have been very easy for them to dismiss this issue as “not their problem”.
Please join us on our newly upgraded high performance server.
Thanks!
September 24th, 2009 at 7:41 pm
Bell’s routing is so stupid, you see here it goes all the way to Chicago to New York and back to Toronto.
2 44 ms 47 ms 44 ms bas1-toronto09_lo0_SYMP.net.bell.ca [64.230.197.215]
3 41 ms 41 ms 42 ms core1-toronto12_13-0-5_148.net.bell.ca [64.230.139.193]
4 41 ms 41 ms 42 ms core4-toronto12_POS0-1.net.bell.ca [64.230.242.197]
5 52 ms 52 ms 51 ms core2-chicago23_pos3-0-0.net.bell.ca [64.230.147.22]
6 52 ms 53 ms 52 ms bx3-chicagodt_so-1-0-0-0.net.bell.ca [64.230.203.42]
7 51 ms 51 ms 51 ms chi-bb1-link.telia.net [213.248.85.25]
8 97 ms 99 ms 97 ms sjo-bb1-link.telia.net [213.248.80.25]
9 98 ms 99 ms 99 ms hurricane-113209-sjo-bb1.c.telia.net [213.248.86.54]
10 100 ms 99 ms 99 ms 10gigabitethernet4-1.core1.sjc2.he.net [72.52.92.70]
11 121 ms 124 ms 124 ms 10gigabitethernet1-3.core1.nyc4.he.net [72.52.92.26]
12 119 ms 120 ms 124 ms 10gigabitethernet1-2.core1.nyc1.he.net [72.52.92.46]
13 120 ms 120 ms 120 ms 10gigabitethernet1-1.core1.nyc5.he.net [72.52.92.154]
14 141 ms 135 ms 135 ms 10gigabitethernet1-1.core1.tor1.he.net [72.52.92.166]
15 137 ms 136 ms 137 ms gw-spdnetwork.torontointernetxchange.net [198.32.245.81]
16 136 ms 135 ms 135 ms bb2.yyz01.spdnetwork.net [208.68.88.2]
17 136 ms 135 ms 138 ms 67.213.68.2