thanks , I managed to find some time to reach out to Sha...

[mattywaggleburn]

thanks @shaw-tony ,

I managed to find some time to reach out to Shaw's cancellation team this morning.  I provided them with a link to this discussion as well as the discussions on reddit. Hopefully they'll either be able to escalate this issue towards a resolution or wave my cancellation fee's.

[Durandal]

If you need any testing today I am home all day and can do any tests you need done. 

[CapnCrunch]

@mattywaggleburn 

Please keep us posted how that goes for you. I will take the same approach if they can't resolve the issues for me. 

@shaw-tony thank you again for helping us with this issue. 

[mattywaggleburn]

@CapnCrunch @Durandal 

did you guys wanna try now?

Someone is changing something behind the scenes, Connection for me right now sticks at excellent.

Here is a trace route from this morning compared to this afternoon... maybe it's just a coincidence?

1 <1 ms <1 ms <1 ms 10.24.72.1
2 12 ms 10 ms 11 ms 70.75.96.1
3 226 ms 105 ms 31 ms rc3no-be134-1.cg.shawcable.net [64.59.133.53]
4 146 ms 28 ms 25 ms rc2wt-be100.wa.shawcable.net [66.163.75.233]
5 34 ms 28 ms 185 ms 72.14.242.90
6 * * * Request timed out.
7 31 ms 30 ms 29 ms 209.85.254.236
8 32 ms 31 ms 31 ms 172.217.78.75
9 31 ms 30 ms 29 ms 172.217.78.124
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 30 ms 26 ms 27 ms 136.112.66.151

This afternoon, same stadia ip

1 <1 ms <1 ms <1 ms 10.24.72.1
2 12 ms 10 ms 13 ms 70.75.96.1
3 11 ms 13 ms 14 ms rc3no-be134-1.cg.shawcable.net [64.59.133.53]
4 31 ms 32 ms 28 ms rc2wt-be100.wa.shawcable.net [66.163.75.233]
5 64 ms 38 ms 37 ms 72.14.242.90
6 * * * Request timed out.
7 30 ms 31 ms 32 ms 209.85.254.248
8 33 ms 32 ms 33 ms 172.253.140.9
9 * 30 ms 30 ms 172.253.140.124
10 27 ms 28 ms 27 ms 136.116.0.216

10 hops with a lower latency is a huge improvement.

@shaw-tony I wouldnt call this fixed until we can confirm something was changed or until we can confirm it lasts?

[Durandal]

I myself am still seeing the same issue as before looks like you start in Calgary where I start in Edm.

[mattywaggleburn]

@Durandal Yup, i'm afraid after a about 15 minutes it just dropped back to where it was... 

[talios]

Yeah..it was actually working for me most of this last week, good connection etc. Today my connection quality has dropped and doing a trace route it looks like the routing is screwed again..I think I'm going to bite the bullet, pay the fee for getting out of my Shaw contract earlier and switch to Telus' at this point..thanks to @shaw-tony for trying to get it fixed and doing his best but the Shaw engineers are obviously incompent 😕  it's been what, 3 weeks now it's been having issues while every other ISP works fine? (I even have friends on teksavvy which uses Shaw's mile end network and their routings been fine since 2 days after the slide...)

[CapnCrunch]

@mattywaggleburn 

No luck with them letting you cancel early ? 

I'd also like to get over to another provider, but I don't want to pay the fee. To me they should let you leave, my internet has been useless to me for almost a month

[mattywaggleburn]

@CapnCrunch  haven't heard back yet. Waiting for a supervisor to investigate and get back to me. 

[Durandal]

Noticed something totally strange today..

This trace route to 136.116.0.216 from any of my computers has the same time out issues as before never ever ending.

But my trace route from my phone behind the same router actually resolves all the way.

Its like once it gets to the seventh hop

72.14.242.90

The 8th always times out but the 9th hop on the phone goes to

209.85.254.170

And finishes after the 12 hop while my computer routes to this on the 9th and never ever completes the trace route.

209.85.254.246

209.85.242.36

209.85.254.246

Seems super odd.

Sad thing is only my iOS devices finish the trace routes nothing else I run trace routes on ever does including the Shaw Modem and my router.