8/6 Bell Canada latency issues

  • Getting lots of lag out of nowhere today - was fine last night.
    ISP is Bell Canada

    Tracing route to 12.129.222.10 over a maximum of 30 hops

    0 Chris-PC.home [192.168.2.58]
    1 SAGEMCOM [192.168.2.1]
    2 bas6-kingston08_lo0_SYMP.net.bell.ca [64.230.8.117]
    3 dis7-kingston08_8-2-0_100.net.bell.ca [64.230.101.238]
    4 core1-kingston08_8-0.net.bell.ca [64.230.165.97]
    5 tcore4-toronto63_hu2-4-0-2.net.bell.ca [64.230.51.5]
    6 newcore2-chicago23_so1-0-0.net.bell.ca [64.230.147.170]
    7 bx5-chicagodt_xe0-1-0_0 [64.230.186.255]
    8 12.249.212.9
    9 cr1.cgcil.ip.att.net [12.122.99.22]
    10 12.123.251.21
    11 * * *
    Computing statistics for 250 seconds...
    Source to Here This Node/Link
    Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
    0 Chris-PC.home [192.168.2.58]
    0/ 100 = 0% |
    1 0ms 0/ 100 = 0% 0/ 100 = 0% SAGEMCOM [192.168.2.1]
    0/ 100 = 0% |
    2 11ms 0/ 100 = 0% 0/ 100 = 0% bas6-kingston08_lo0_SYMP.net.bell.ca [64.230.8.117]
    0/ 100 = 0% |
    3 9ms 0/ 100 = 0% 0/ 100 = 0% dis7-kingston08_8-2-0_100.net.bell.ca [64.230.101.238]
    0/ 100 = 0% |
    4 17ms 0/ 100 = 0% 0/ 100 = 0% core1-kingston08_8-0.net.bell.ca [64.230.165.97]
    0/ 100 = 0% |
    5 18ms 0/ 100 = 0% 0/ 100 = 0% tcore4-toronto63_hu2-4-0-2.net.bell.ca [64.230.51.5]
    0/ 100 = 0% |
    6 25ms 0/ 100 = 0% 0/ 100 = 0% newcore2-chicago23_so1-0-0.net.bell.ca [64.230.147.170]
    0/ 100 = 0% |
    7 32ms 0/ 100 = 0% 0/ 100 = 0% bx5-chicagodt_xe0-1-0_0 [64.230.186.255]
    0/ 100 = 0% |
    8 72ms 0/ 100 = 0% 0/ 100 = 0% 12.249.212.9
    100/ 100 =100% |
    9 --- 100/ 100 =100% 0/ 100 = 0% cr1.cgcil.ip.att.net [12.122.99.22]
    0/ 100 = 0% |
    10 --- 100/ 100 =100% 0/ 100 = 0% 12.123.251.21

    Trace complete.

    Tracing route to 12.129.222.10 over a maximum of 30 hops

    1 <1 ms <1 ms <1 ms SAGEMCOM [192.168.2.1]
    2 10 ms 10 ms 9 ms bas6-kingston08_lo0_SYMP.net.bell.ca [64.230.8.117]
    3 10 ms 9 ms 9 ms dis7-kingston08_8-2-0_100.net.bell.ca [64.230.101.238]
    4 28 ms 26 ms 24 ms core1-kingston08_8-0.net.bell.ca [64.230.165.97]
    5 27 ms 30 ms 33 ms tcore4-toronto63_hu2-4-0-2.net.bell.ca [64.230.51.5]
    6 27 ms 23 ms 23 ms newcore2-chicago23_so1-0-0.net.bell.ca [64.230.147.170]
    7 172 ms 65 ms 23 ms bx5-chicagodt_xe3-1-0-0.net.bell.ca [64.230.186.246]
    8 23 ms 24 ms 23 ms 12.249.212.9
    9 27 ms 23 ms 29 ms cr1.cgcil.ip.att.net [12.122.99.22]
    10 25 ms 25 ms 25 ms 12.123.251.21
    11 * * * Request timed out.
    12 * * * Request timed out.
    13 * * * Request timed out.
    14 * * * Request timed out.
    15 * * * Request timed out.
  • Thanks for the reports, all.

    We are currently looking into this issue now. If you have not done so already, please post a Path Ping and a Looking Glass report.
  • Not much of an update so far, from what we're seeing it looks to be an issue as it's routing to us, so if you haven't already I would get in touch with the ISP let them know what's going on. We're also still looking to the issue from this end as well.
  • Hey all,

    As a heads up, I'm heading out for the night here in a few. Small update, we've passed this information along to be looked into further from everything that you've been able to provide us with so far.

    I will be in tomorrow as well so if we get any updates I'll make sure to update everyone to anything new from this end. Past that I would still keep with the prior suggestion of contacting the ISP which it sounds like most have already done.

    Also worth a shot to try Google's public DNS as it could change the routing enough to get you around the node we're seeing the delay on.
  • I'm afraid not much news from this end. We haven't heard anything back as of yet regarding the issue. The moment we have any sort of updates we'll be posting here right away.

    In the mean time I would keep on trying to reach out to your ISP regarding the issue.