Packet Loss - US Servers

Hi all, I was wondering if anyone more network savvay then myself can shed any light on the below trace - I've been getting a horrible connection over the last couple days to POE, and nothing I've been able to do helps it. TWC tells me everything looks good on their end also....not sure if the below is indicative of a problem with my area, with some routers, or with server side area....Thanks for any insight.


|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.0.1 - 0 | 117 | 117 | 0 | 0 | 1 | 0 |
| cpe-69-204-168-1.nycap.res.rr.com - 1 | 113 | 112 | 15 | 45 | 1734 | 27 |
|gig1-21.troynydv-rtr003.alb.east.twcable.com - 4 | 101 | 97 | 18 | 49 | 1739 | 27 |
| 24.58.33.138 - 1 | 113 | 112 | 9 | 29 | 1720 | 14 |
| be26.albynyyf01r.northeast.rr.com - 0 | 117 | 117 | 8 | 28 | 1722 | 11 |
|bu-ether46.nycmny837aw-bcr00.tbone.rr.com - 3 | 105 | 102 | 19 | 42 | 1731 | 24 |
| 0.ae1.pr1.nyc20.tbone.rr.com - 1 | 113 | 112 | 19 | 39 | 1729 | 24 |
| 66.109.7.42 - 1 | 113 | 112 | 19 | 39 | 1729 | 22 |
| ae8.cr1.lga5.us.zip.zayo.com - 2 | 109 | 107 | 19 | 45 | 2232 | 22 |
| ae9.mpr3.phl2.us.zip.zayo.com - 1 | 113 | 112 | 20 | 40 | 1734 | 24 |
| ae4.mpr4.phl2.us.zip.zayo.com - 1 | 113 | 112 | 19 | 41 | 1733 | 32 |
| ae6.cr2.dca2.us.zip.zayo.com - 4 | 101 | 97 | 0 | 52 | 2242 | 27 |
| ae15.er5.iad10.us.zip.zayo.com - 4 | 101 | 97 | 23 | 53 | 2242 | 32 |
| 209.66.94.62 - 3 | 105 | 102 | 23 | 44 | 1740 | 26 |
| ae0.dar01.wdc01.networklayer.com - 3 | 105 | 102 | 25 | 48 | 1739 | 30 |
| po1.fcr06a.wdc01.networklayer.com - 2 | 109 | 107 | 0 | 51 | 2241 | 33 |
| 6f.28.559e.ip4.static.sl-reverse.com - 2 | 109 | 107 | 0 | 51 | 2240 | 29 |
|________________________________________________|______|______|______|______|______|______|

I'm pretty sure you need to call your ISP for this one. Just to be extra sure, we should look at another trace, but run it for 5 minutes (300 cycles) instead of 2.

Ran it a bit longer this time :

|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.0.1 - 0 | 728 | 728 | 0 | 0 | 12 | 0 |
| cpe-69-204-168-1.nycap.res.rr.com - 2 | 678 | 666 | 10 | 49 | 3150 | 31 |
|gig1-21.troynydv-rtr003.alb.east.twcable.com - 2 | 693 | 684 | 13 | 40 | 1826 | 22 |
| 24.58.33.138 - 2 | 696 | 688 | 8 | 20 | 1815 | 10 |
| be26.albynyyf01r.northeast.rr.com - 2 | 699 | 692 | 8 | 23 | 1814 | 12 |
|bu-ether46.nycmny837aw-bcr00.tbone.rr.com - 2 | 685 | 674 | 17 | 31 | 1842 | 30 |
| 0.ae1.pr1.nyc20.tbone.rr.com - 1 | 701 | 694 | 16 | 29 | 1822 | 21 |
| 66.109.7.42 - 2 | 685 | 674 | 16 | 30 | 1822 | 23 |
| ae8.cr1.lga5.us.zip.zayo.com - 2 | 681 | 669 | 17 | 30 | 1821 | 25 |
| ae9.mpr3.phl2.us.zip.zayo.com - 2 | 684 | 673 | 18 | 32 | 1791 | 24 |
| ae4.mpr4.phl2.us.zip.zayo.com - 2 | 677 | 664 | 18 | 31 | 1823 | 27 |
| ae6.cr2.dca2.us.zip.zayo.com - 2 | 685 | 674 | 0 | 35 | 1827 | 30 |
| ae15.er5.iad10.us.zip.zayo.com - 2 | 677 | 664 | 23 | 36 | 1852 | 25 |
| 209.66.94.62 - 3 | 673 | 659 | 0 | 34 | 1829 | 24 |
| ae0.dar01.wdc01.networklayer.com - 3 | 665 | 649 | 0 | 36 | 1840 | 31 |
| po1.fcr06a.wdc01.networklayer.com - 3 | 673 | 659 | 0 | 35 | 1748 | 31 |
| 6f.28.559e.ip4.static.sl-reverse.com - 3 | 653 | 634 | 0 | 36 | 1829 | 31 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

You could do that test on any website, like google.com, and it should have the same results for packet loss on hop 2 there (and packet loss all the way to the end).

Turn the modem and router off for a minute, and turn them on again, to see if that fixes it.

Send that MTR report to your ISP, or call them, they should diagnose and fix this.