Tracert shows three gateways trapping packets by routing in a circle when tracing hockey.fantasysports.yahoo.com. This address resolves to tracing fantasy.edge.g03.yahoodns.net [69.147.65.252]. The issue likely affects Shaw users from Calgary to Sault Ste. Marie judging from a yahoo outages heatmap. This issue has been ongoing since around 2022-04-08 16:00 CST. I can't find anywhere to report technical issues like this to Shaw, so just hoping someone can pass this on to someone who can sort the issue out.
The three devices that are routing in a loop are: rc4ec-be25-1.il.shawcable.net [66.163.75.134] rc3ec-hge0-9-0-1.il.shawcable.net [66.163.65.109] rc3sc-be25-2.wp.shawcable.net [66.163.75.177]
Tracing route to fantasy.edge.g03.yahoodns.net [69.147.65.252] over a maximum of 30 hops:
1 1 ms 1 ms <1 ms 2 10 ms 10 ms 7 ms 3 12 ms 9 ms 9 ms rc3sc-be115-1.wp.shawcable.net [64.59.181.41] 4 9 ms 9 ms 9 ms 24.244.61.13 5 9 ms 11 ms 9 ms 24.244.61.225 6 10 ms 8 ms 9 ms rc3sc-be2.wp.shawcable.net [24.244.58.169] 7 24 ms 25 ms 24 ms rc4ec-be25-1.il.shawcable.net [66.163.75.134] 8 24 ms 25 ms 24 ms rc3ec-hge0-9-0-1.il.shawcable.net [66.163.65.109] 9 24 ms 24 ms 24 ms rc3sc-be25-2.wp.shawcable.net [66.163.75.177] 10 40 ms 39 ms 40 ms rc4ec-be25-1.il.shawcable.net [66.163.75.134] 11 40 ms 40 ms 39 ms rc3ec-hge0-9-0-1.il.shawcable.net [66.163.65.109] 12 40 ms 40 ms 40 ms rc3sc-be25-2.wp.shawcable.net [66.163.75.177] 13 55 ms 55 ms 55 ms rc4ec-be25-1.il.shawcable.net [66.163.75.134] 14 55 ms 56 ms 56 ms rc3ec-hge0-9-0-1.il.shawcable.net [66.163.65.109] 15 55 ms 55 ms 55 ms rc3sc-be25-2.wp.shawcable.net [66.163.75.177] 16 71 ms 71 ms 70 ms rc4ec-be25-1.il.shawcable.net [66.163.75.134] 17 70 ms 71 ms 71 ms rc3ec-hge0-9-0-1.il.shawcable.net [66.163.65.109] 18 71 ms 70 ms 70 ms rc3sc-be25-2.wp.shawcable.net [66.163.75.177] 19 87 ms 86 ms 86 ms rc4ec-be25-1.il.shawcable.net [66.163.75.134] 20 87 ms 85 ms 87 ms rc3ec-hge0-9-0-1.il.shawcable.net [66.163.65.109] 21 86 ms 86 ms 86 ms rc3sc-be25-2.wp.shawcable.net [66.163.75.177] 22 102 ms 102 ms 101 ms rc4ec-be25-1.il.shawcable.net [66.163.75.134] 23 102 ms 101 ms 102 ms rc3ec-hge0-9-0-1.il.shawcable.net [66.163.65.109] 24 101 ms 101 ms 109 ms rc3sc-be25-2.wp.shawcable.net [66.163.75.177] 25 117 ms 116 ms 116 ms rc4ec-be25-1.il.shawcable.net [66.163.75.134] 26 117 ms 116 ms 117 ms rc3ec-hge0-9-0-1.il.shawcable.net [66.163.65.109] 27 117 ms 118 ms 117 ms rc3sc-be25-2.wp.shawcable.net [66.163.75.177] 28 132 ms 133 ms 132 ms rc4ec-be25-1.il.shawcable.net [66.163.75.134] 29 133 ms 132 ms 132 ms rc3ec-hge0-9-0-1.il.shawcable.net [66.163.65.109] 30 134 ms 132 ms 131 ms rc3sc-be25-2.wp.shawcable.net [66.163.75.177]
