|
Post by hawkeyex on Sept 28, 2011 19:09:06 GMT -5
My connection to the box looks fine. Garlen said his was fine until to the box...
looks like verizon is heavily bogged down towards the last three hops.
Can you help?
|
|
Rox
Full Member
Posts: 195
|
Post by Rox on Sept 29, 2011 8:22:51 GMT -5
Looks like the problem is still there.
|
|
Mal
Full Member
Posts: 231
|
Post by Mal on Sept 30, 2011 1:31:27 GMT -5
Still the odd spurt of lag but it has been much better.
|
|
wehr
Junior Member
Posts: 61
|
Post by wehr on Dec 4, 2011 9:58:59 GMT -5
Its starting up again, looks like the jedimud box or its immediate network is at fault.
------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.1.1 - 0 | 131 | 131 | 0 | 0 | 2 | 0 |
| No response from host - 100 | 23 | 0 | 0 | 0 | 0 | 0 |
| wwcksysc02-gex0203000.ri.ri.cox.net - 0 | 131 | 131 | 6 | 8 | 15 | 7 |
| ip98-190-33-38.ri.ri.cox.net - 0 | 131 | 131 | 7 | 10 | 28 | 7 |
| provdsrj02-ae3.0.rd.ri.cox.net - 0 | 131 | 131 | 7 | 13 | 65 | 10 |
| nyrkbprj01-ae2.0.rd.ny.cox.net - 2 | 122 | 120 | 13 | 19 | 115 | 14 |
| vlan90.csw4.NewYork1.Level3.net - 0 | 131 | 131 | 13 | 20 | 36 | 15 |
| ae-92-92.ebr2.NewYork1.Level3.net - 0 | 131 | 131 | 13 | 16 | 36 | 16 |
| ae-6-6.ebr2.NewYork2.Level3.net - 0 | 131 | 131 | 13 | 16 | 34 | 14 |
| ae-2-52.edge2.NewYork2.Level3.net - 7 | 100 | 93 | 0 | 15 | 38 | 14 |
| 4.68.111.138 - 1 | 126 | 125 | 13 | 18 | 77 | 15 |
| 0.ae3.NY5030-BB-RTR2.verizon-gni.NET - 2 | 122 | 120 | 0 | 26 | 212 | 18 |
| as0-0.PITT2-CORE-RTR2.verizon-gni.net - 4 | 113 | 109 | 24 | 27 | 45 | 27 |
|A4-0-0-1711.PITT2-DSL-RTR1.verizon-gni.net - 7 | 100 | 93 | 0 | 27 | 45 | 26 |
|static-151-201-143-150.pitt.east.verizon.net - 79 | 28 | 6 | 0 | 54 | 58 | 54 |
|________________________________________________|______|______|______|______|______|______|
There is about 70% packet loss on the DSL link to jedi, so that is close to the culprit...
|
|