Look at this sad network performance.
C:\>ping -n 10 24.82.128.1
Pinging 24.82.128.1 with 32 bytes of data:
Reply from 24.82.128.1: bytes=32 time=41ms TTL=254
Reply from 24.82.128.1: bytes=32 time=70ms TTL=254
Reply from 24.82.128.1: bytes=32 time=159ms TTL=254
Reply from 24.82.128.1: bytes=32 time=94ms TTL=254
Reply from 24.82.128.1: bytes=32 time=60ms TTL=254
Reply from 24.82.128.1: bytes=32 time=349ms TTL=254
Reply from 24.82.128.1: bytes=32 time=29ms TTL=254
Reply from 24.82.128.1: bytes=32 time=36ms TTL=254
Reply from 24.82.128.1: bytes=32 time=533ms TTL=254
Reply from 24.82.128.1: bytes=32 time=28ms TTL=254
Ping statistics for 24.82.128.1:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 28ms, Maximum = 533ms, Average = 139ms
Is it just me or are the major cable and DSL providers in the Vancouver area ripping us off? This has been going on for a week now, with the worst performance during prime time. A shaw support tech informed me this area needs to be “segmented”. In otherwords the company has oversold its infrastructure.
If someone wrote a small background program that monitored the performance of critical services such as my next hop router and my ISP’s DNS and sent that back to a central site I’d gladly run it. It would be nice to know which ISP sucks the least. The anadoctal evidence available now isn’t good enough. I heard some calls for community based monitoring of ISPs as use of deep packet inspection and throttling by providers has increased, but I don’t see much action.
Posted by seancomeau
Posted by seancomeau
Posted by seancomeau