This is interesting for me to see, explains a lot for wha...

[GBLawlz]

This is interesting for me to see, explains a lot for what's going on. Would seem like nothing is broken in Winnipeg, its the link between ED>CG, like was mentioned before. Your hop form WPG>CHI is only around 15ms, while mine to the same spot is 23-24ms. Looks like all outside traffic is getting the priority in an effort to make things feel normal for them. The result for me here is an increase of about 8ms, due to my traffic getting the yellow light once it gets to the WPG routing point. 

[talios]

It’s been a week now since this screwup made online gaming impossible and no fix in sight; this is ridiculous 😞 I ended up signing up for express VPN because their New Jersey address doesn’t go through shaws overloaded Winnipeg hop; so since my traffic is still going to the east coast first it’s still 40 ms higher; but better that than the 80-100 I get on shaws horribly overloaded Winnipeg hop

[kalamalka123]

mine just got fixed!!! check yours.

[mdk]

@GBLawlz -- imagine yourself driving in Winnipeg, going east on Highway 1, and learning that it was closed eastbound of the intersection with Highway 62. If you (and everybody else) detours onto southbound 62, traffic would be very congested on 62.

There's nothing wrong with 62, given its normal traffic-load, but with the extra traffic taking the detour, instead of staying on 1/Broadway, you will see a slowdown of the average speed from 80 Km/hour to 50 or 60 Km/hour. Similarly, there is an increase in PING-times from Winnipeg to the USA, due to the extra traffic.

@talios -- It’s been a week now

Do you think that Shaw is deliberately delaying the repair? What does it gain them to do so?

If parts for a router, or a replacement router, is needed, and the parts are not available in the Cisco warehouse in Vancouver (BC), it will take longer to get parts express-shipped (and through Canada Customs) to get from Northern California to Alberta.  If it's a broken fiber-optic cable, try digging through frozen Alberta ground, to access the break.

[mdk]

@kalamalka123 -- check yours

I just did, and I still see:

  11 ms  rc1bb-be20.vc.shawcable.net [66.163.75.245]
  27 ms  rc3so-be6-1.cg.shawcable.net [66.163.78.37]
  42 ms  rc3sc-be110-1.wp.shawcable.net [66.163.76.62]
  40 ms  rc2ar-be128-1.ed.shawcable.net [64.59.184.113]

Vancouver -> Calgary -> Winnipeg -> Edmonton.

Maybe, it's just that the routing-tables in the routers in Calgary (and maybe Vancouver) need to be rebooted, to get updated routing information ?

[talios]

@mdk Not deliberately slowing it down so much as just not caring. I’m a network engineer for a major datacenter chain and you best believe if there’s parts not in stock at a Cisco warehouse we get it overnighted from Taiwan via our rep and a fix in place within 12 hours if it’s affecting major business clients; Shaw just doesn’t care about residential users

[talios]

I also happen to know Telus keeps enough equipment for redundant routes between cities which is why they don’t have frequent routing issues like this (the last Shaw one was less than a year ago)  alas my building isn’t wired for fibre

[b0dak]

the fact you keep making excuses for a MASSIVE company that shows no remorse for resident customers, customer service is ABSOLUTLY HORRIBLE. I called 9 different times and had a new modem put in becuase of this problem, to be told by every person from Shaw that its a problem on my end and there end is fine. Even after sending them multiple traceroutes they still continued to blame me and say there connection was completely fine. AND then they say NOTHING about this routing issue to ANYONE and basically hide it. 

[mdk]

@talios -- if it’s affecting major business clients; Shaw just doesn’t care about residential users

Are you saying that Shaw has separate network segments between YYC and YEG for their "residential" versus "business" customers?  I doubt it.

I would expect that most "major business" customers have most of their Internet traffic starting and ending within Canada, i.e., store-to-store or store-to-headquarters or store-to-MasterCard/VISA payment processors, and thus would not be going through the Winnipeg -> USA network segment. Unless, of course, their employees are misusing company computers to connect to USA-based game-servers.  🙂

[mdk]

@b0dak -- they say NOTHING about this routing issue to ANYONE and basically hide it

I think that @rstra (above) hit the nail on the head -- front-line staff are either not trained to help with "network congestion" issues, and/or are not informed (or self-informed by reading internal company bulletins) about such system-wide "backbone" issues.