|reply to kevinds |
Re: [BC] Something fishy going on in Nelson with shaw speeds!
The problems with Youtube could be the fact that Shaw doesn't seem to know how peering works and the paths are ridiculously long (17+ hops to most major web presences and services).
I don't know what they are doing for peering if much at all but the latency changes plus packet loss plus slow transit speeds in the evenings point to peak usage issues they are not resolving.
That's mostly what pisses me off - they know about them but aren't fixing them. I could deal with slow transfer speeds in the evenings if the latency didn't shoot up and there was no packet loss. The jitter is ridiculous too which causes havoc on any gaming I might try to do.
Google provides cache servers for most medium sized and bigger ISPs so peering doesn't matter.
Yes, I am not employed and looking for IT work. Have passport, will travel.