
Originally Posted by
Alexika
Raist, at first I was really thinking you may be right, but I don't think our ISP is to blame at all. I have done numerous long term pings now to my server and the problem does not arise until it leaves my ISPs network. In fact, the majority of my packet loss is actually once it hits SEs network. I am starting to believe that SE is not paying for enough bandwidth.
I thought I was seeing issues there, but it turns out it is just an anti-DDoS feature. Want the MTR I am running right now?
Code:
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| Wireless_Broadband_Router.home - 1 | 1060 | 1058 | 0 | 4 | 473 | 2 |
|lo0-100.PRVDRI-VFTTP-306.verizon-gni.net - 0 | 1068 | 1068 | 4 | 10 | 428 | 6 |
| T0-2-0-9.PRVDRI-LCR-22.verizon-gni.net - 0 | 1068 | 1068 | 4 | 10 | 422 | 8 |
| xe-1-0-8-0.BOS-BB-RTR2.verizon-gni.net - 0 | 1068 | 1068 | 6 | 24 | 428 | 7 |
|xe-4-1-0-0.NY325-BB-RTR2.verizon-gni.net - 0 | 1068 | 1068 | 17 | 27 | 461 | 21 |
| 0.ae7.BR1.NYC1.ALTER.NET - 0 | 1068 | 1068 | 15 | 21 | 410 | 17 |
| No response from host - 100 | 213 | 0 | 0 | 0 | 0 | 0 |
| ae-11-11.car2.Montreal2.Level3.net - 1 | 1053 | 1049 | 56 | 89 | 652 | 108 |
| ae-11-11.car2.Montreal2.Level3.net - 1 | 1052 | 1048 | 56 | 89 | 620 | 270 |
| ORMUCO-COMM.car2.Montreal2.Level3.net - 1 | 1041 | 1034 | 56 | 63 | 534 | 60 |
| 192.34.76.10 - 13 | 719 | 632 | 68 | 78 | 534 | 72 |
| 199.91.189.242 - 15 | 682 | 585 | 0 | 78 | 492 | 74 |
| 199.91.189.33 - 17 | 645 | 539 | 0 | 81 | 503 | 75 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider