Slow network to this forum (and my site)...
Anyone else seeing this problem for the last couple of hours?
First was a good traceroute for comparison....Code:------------------------------------------------------- Tracing route xxxxxxxxxxxxxxxxxxxxxx over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 192.168.0.1 2 2 ms 2 ms 2 ms 10.9.44.4 3 2 ms 2 ms 1 ms P2-2.LCR-02.BSTNMA.verizon-gni.net [130.81.32.182] 4 12 ms 12 ms 11 ms so-7-0-0-0.PEER-RTR1.NY111.verizon-gni.net [130.81.17.131] 5 12 ms 12 ms 12 ms so-6-0-0.pr2.lga1.us.above.net [64.125.13.33] 6 12 ms 12 ms 11 ms so-5-0-0.cr2.lga1.us.above.net [64.125.27.138] 7 17 ms 17 ms 17 ms so-1-0-0.mpr2.iad1.us.above.net [64.125.28.65] 8 18 ms 18 ms 18 ms so-6-0-0.cr2.dca2.us.above.net [64.125.27.210] 9 49 ms 49 ms 49 ms so-3-2-0.cr2.dfw2.us.above.net [64.125.28.205] 10 54 ms 54 ms 54 ms so-3-0-0.mpr2.iah1.us.above.net [64.125.31.41] 11 280 ms 140 ms 54 ms 209.133.90.85.available.above.net [209.133.90.85] 12 54 ms 54 ms 54 ms hou-rtr3-vl3.cyrusone.com [69.7.175.35] 13 55 ms 54 ms 55 ms vl2-rtr1.nocdirect.com [69.7.160.227] 14 54 ms 54 ms 57 ms xxxxxxxxxxxxxxx Trace complete. ---------------------------------------------------- Tracing route to xxxxxxxxxxxxxxxxxxxxx over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 192.168.0.1 2 2 ms 1 ms 1 ms 10.9.44.4 3 2 ms 2 ms 1 ms P2-2.LCR-02.BSTNMA.verizon-gni.net [130.81.32.182] 4 12 ms 12 ms 11 ms so-7-0-0-0.PEER-RTR1.NY111.verizon-gni.net [130.81.17.131] 5 12 ms 12 ms 12 ms so-6-0-0.pr2.lga1.us.above.net [64.125.13.33] 6 12 ms 12 ms 12 ms so-5-0-0.cr2.lga1.us.above.net [64.125.27.138] 7 17 ms 18 ms 17 ms so-1-0-0.mpr2.iad1.us.above.net [64.125.28.65] 8 18 ms 18 ms 18 ms so-6-0-0.cr2.dca2.us.above.net [64.125.27.210] 9 49 ms 49 ms 49 ms so-3-2-0.cr2.dfw2.us.above.net [64.125.28.205] 10 54 ms 53 ms 53 ms so-3-0-0.mpr2.iah1.us.above.net [64.125.31.41] 11 204 ms 199 ms 199 ms 209.133.90.85.available.above.net [209.133.90.85] 12 54 ms 54 ms 54 ms hou-rtr3-vl3.cyrusone.com [69.7.175.35] 13 * 56 ms 56 ms vl2-rtr1.nocdirect.com [69.7.160.227] 14 54 ms 55 ms 54 ms xxxxxxxxxxxxxxxxxxxx -------------------------------------------------------- Tracing route to xxxxxxxxxxxxxxxxxxxxxxx over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 192.168.0.1 2 2 ms 2 ms 1 ms 10.9.44.4 3 2 ms 2 ms 1 ms P2-2.LCR-02.BSTNMA.verizon-gni.net [130.81.32.182] 4 11 ms 12 ms 11 ms so-7-0-0-0.PEER-RTR1.NY111.verizon-gni.net [130.81.17.131] 5 12 ms 11 ms 11 ms so-6-0-0.pr2.lga1.us.above.net [64.125.13.33] 6 12 ms 12 ms 20 ms so-5-0-0.cr2.lga1.us.above.net [64.125.27.138] 7 17 ms 22 ms 17 ms so-1-0-0.mpr2.iad1.us.above.net [64.125.28.65] 8 18 ms 18 ms 17 ms so-6-0-0.cr2.dca2.us.above.net [64.125.27.210] 9 49 ms 49 ms 49 ms so-3-2-0.cr2.dfw2.us.above.net [64.125.28.205] 10 54 ms 53 ms 54 ms so-3-0-0.mpr2.iah1.us.above.net [64.125.31.41] 11 149 ms 247 ms 192 ms 209.133.90.85.available.above.net [209.133.90.85] 12 54 ms 54 ms 54 ms hou-rtr3-vl3.cyrusone.com [69.7.175.35] 13 54 ms 54 ms 55 ms vl2-rtr1.nocdirect.com [69.7.160.227] 14 * 54 ms 54 ms xxxxxxxxxxxxxxxxxx Trace complete. -------------------------------------------------------- Tracing route to xxxxxxxxxxxxxxxxxxxxxx over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 192.168.0.1 2 2 ms 2 ms 1 ms 10.9.44.4 3 2 ms 2 ms 2 ms P2-2.LCR-02.BSTNMA.verizon-gni.net [130.81.32.182] 4 12 ms 12 ms 11 ms so-7-0-0-0.PEER-RTR1.NY111.verizon-gni.net [130.81.17.131] 5 12 ms 11 ms 12 ms so-6-0-0.pr2.lga1.us.above.net [64.125.13.33] 6 12 ms 12 ms 12 ms so-5-0-0.cr2.lga1.us.above.net [64.125.27.138] 7 17 ms 17 ms 17 ms so-1-0-0.mpr2.iad1.us.above.net [64.125.28.65] 8 18 ms 18 ms 18 ms so-6-0-0.cr2.dca2.us.above.net [64.125.27.210] 9 49 ms 49 ms 49 ms so-3-2-0.cr2.dfw2.us.above.net [64.125.28.205] 10 54 ms 53 ms 54 ms so-3-0-0.mpr2.iah1.us.above.net [64.125.31.41] 11 54 ms 54 ms 54 ms 209.133.90.85.available.above.net [209.133.90.85] 12 54 ms 54 ms 54 ms hou-rtr3-vl3.cyrusone.com [69.7.175.35] 13 382 ms 133 ms 56 ms vl2-rtr1.nocdirect.com [69.7.160.227] 14 54 ms 54 ms 56 ms xxxxxxxxxxxxxxxxxxxx Trace complete. ---------------------------------------------------------- Tracing route to xxxxxxxxxxxxxxxxxxxx over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 192.168.0.1 2 2 ms 2 ms 1 ms 10.9.44.4 3 2 ms 1 ms 1 ms P2-2.LCR-02.BSTNMA.verizon-gni.net [130.81.32.182] 4 12 ms 79 ms 12 ms so-7-0-0-0.PEER-RTR1.NY111.verizon-gni.net [130.81.17.131] 5 12 ms 12 ms 12 ms so-6-0-0.pr2.lga1.us.above.net [64.125.13.33] 6 12 ms 11 ms 12 ms so-5-0-0.cr2.lga1.us.above.net [64.125.27.138] 7 18 ms 17 ms 17 ms so-1-0-0.mpr2.iad1.us.above.net [64.125.28.65] 8 18 ms 17 ms 17 ms so-6-0-0.cr2.dca2.us.above.net [64.125.27.210] 9 81 ms 49 ms 49 ms so-3-2-0.cr2.dfw2.us.above.net [64.125.28.205] 10 53 ms 53 ms 63 ms so-3-0-0.mpr2.iah1.us.above.net [64.125.31.41] 11 54 ms 54 ms 56 ms 209.133.90.85.available.above.net [209.133.90.85] 12 54 ms 54 ms 54 ms hou-rtr3-vl3.cyrusone.com [69.7.175.35] 13 54 ms 54 ms 54 ms vl2-rtr1.nocdirect.com [69.7.160.227] 14 * * 55 ms xxxxxxxxxxxxxxxxx Trace complete. ----------------------------------
Seems like the problem has been shifting around between the server, the last router and the last outside router...
I've looked at the server and it's doing just fine; in fact I'm running stuff through SSH that's interactive and there is 0 lag, so this is HTTP and HTTPS (since I can just barely interact with the JAG ticket system) Also this forum is dreadfully slow (more than 3 tries and then 2 minutes to get to this text entry page).
Support says things are all better now...![]()


LinkBack URL
About LinkBacks




Reply With Quote

Bookmarks