Hey guys. I've been having issues with Shaw for about 2 years now with constant ping jumping and packet loss. I've tried to get them to fix it with probably over 300 requests through their chat system, around 15 tech visits and 8 different modems. I shrugged the issue off as a Puma 6 issue for most of the 2 years I've been with Shaw and kept pestering them about the XB6 as I had high hopes it would solve me issues. It didn't, but little did I know the XB6 wasn't defective (to my knowledge). So to test it out I swapped to the Broadcom Chipset Cisco and found out the jumping and packet loss was still persisting. I was in disbelief and knew they would do everything in their power to not have to fix the connection as most ISPs do. They've spent more effort so far in an attempt to do nothing about it.
Unfortunately I've gotten to a point where I was hoping you guys could confirm my suspicions, or tell me I'm crazy, whichever you feel is more correct. I've ran 100s of tests using WinMTR and when I show Shaw they tell me 'those results are normal, the ping jumping on the first hop doesn't affect the rest of the hops'. However even when running the Puma 6 test on a broadcom modem (which should come out clean) the results show the same ping jumping ranging from 149ms-599ms. On occasion it comes out mostly clean but it seems to vary from test to test (I've testing in multiple browsers, it always comes out the same).
Below is a test showing the jumping I've been having. This is a test during the day around 3pm-5pm which I would consider a peak time for the neighbourhood as most of the kids come home from school in the area and I'd imagine start putting stress on their connections. If I run the exact same test at midnight the highest jump I get is 200ms and the connection is more stable; not perfect but still more stable. With that being said the only culprit I can possibly conclude is node saturation. I've tried multiple configurations (bridge, unbridged, bridge with my own modem, etc.) with no difference.
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 96.52.128.1 - 1 | 309 | 308 | 6 | 30 | 810 | 7 |
| rh9we-cmts.ed.shawcable.net - 0 | 313 | 313 | 8 | 9 | 67 | 8 |
| 66.163.70.77 - 0 | 313 | 313 | 21 | 25 | 82 | 26 |
| rc4ec-be25-1.il.shawcable.net - 0 | 313 | 313 | 38 | 39 | 46 | 38 |
| 66.163.75.230 - 0 | 313 | 313 | 37 | 39 | 54 | 41 |
| No response from host - 100 | 63 | 0 | 0 | 0 | 0 | 0 |
| 216.239.42.154 - 0 | 313 | 313 | 37 | 43 | 423 | 41 |
| 108.170.244.2 - 0 | 313 | 313 | 37 | 40 | 55 | 38 |
| 216.239.57.77 - 0 | 313 | 313 | 38 | 39 | 56 | 43 |
| 209.85.241.43 - 0 | 313 | 313 | 52 | 57 | 93 | 57 |
| 209.85.248.158 - 0 | 313 | 313 | 52 | 54 | 66 | 53 |
| No response from host - 100 | 63 | 0 | 0 | 0 | 0 | 0 |
| 209.85.240.255 - 0 | 313 | 313 | 50 | 54 | 65 | 59 |
| sea15s01-in-f3.1e100.net - 0 | 313 | 313 | 52 | 54 | 68 | 55 |
|________________________________________________|______|______|______|______|______|______|
Anyone have any ideas? I've ordered Telus for next week to test the connections side by side. But I've had Telus before with clean results.
↧