Same thing tonight... but pinging the content server with ping plotter doesn't really reveal anything.
The content server I was hitting was. ipv4_1.lagg0.c035.sea001.ix.nflxvideo.net which resolves to 220.127.116.11
Tomorrow i'll bring my work laptop home to prove a point... i'm guessing I'll have the same problem on that laptop... until I fire up my VPN connection to work. So i will still be using my connection to Shaw, but the traffic will be routed to my work before getting to netflix. (they don't use shaw at work)