VDS with 4cores, 4GB Ram 400GB HD.
I jsut bought this server. It was running amazingly a day ago, then out of the blue, this started happening. There is something wrong with INTERNAP switch that the timeout is almost 90%. Please help!
Really bad latency/timeout on VDS
-
- New to forums
- Posts: 11
- https://www.youtube.com/channel/UC40BgXanDqOYoVCYFDSTfHA
- Joined: Thu Oct 28, 2010 6:54 am
Re: Really bad latency/timeout on VDS
Have your tried a restart? Also have you sent in a support ticket? One last thing. Are you the only one having these problems?
@Kraze^NFo> Juski has a very valid point
@Juski> Got my new signature, thanks!
@Kraze^NFo> Out of context!
@Juski> Doesn't matter!
@Juski> You said I had a valid point! You can't take it back now! It's out there!
@Juski> Got my new signature, thanks!
@Kraze^NFo> Out of context!
@Juski> Doesn't matter!
@Juski> You said I had a valid point! You can't take it back now! It's out there!
Re: Really bad latency/timeout on VDS
Seeing timeouts before the last hop is nothing to be concerned about, as some routers de-prioritize ping requests for real traffic. You are still reaching the destination without that high level of loss. We talk about this more here: http://www.nfoservers.com/forums/viewto ... =25&t=4706
Beyond that, you are showing high ping on your route almost right away, and go over 100 before even leaving the Comcast network. It seems Comcast is having some issues from the looks of that trace, but historically, HLSW has not been a reliable tool for testing network connections. I would recommend running an MTR instead, which we show how to do in our guide here: http://www.nfoservers.com/forums/viewto ... =25&t=4272
Beyond that, you are showing high ping on your route almost right away, and go over 100 before even leaving the Comcast network. It seems Comcast is having some issues from the looks of that trace, but historically, HLSW has not been a reliable tool for testing network connections. I would recommend running an MTR instead, which we show how to do in our guide here: http://www.nfoservers.com/forums/viewto ... =25&t=4272
TimeX
- rlm850
- This is my homepage
- Posts: 141
- Joined: Thu Dec 10, 2009 12:17 am
- Location: Staten Island, NY
- Contact:
Re: Really bad latency/timeout on VDS
I've known comcast to have many problems. I used to do radio broadcasting via shoutcast, and also help users of comcast and other ISPs get their station setup. I would rate comcast a 3/10 as an ISP for their lack of quality and peak time limits.
I can tell you it's not your server.
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Rob>tracert 63.251.20.181
Tracing route to v-63-251-20-181.virt-machine.internap-nyc.nfoservers.com [63.25
1.20.181]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms 192.168.1.1
2 8 ms 7 ms 11 ms 10.240.180.25
3 10 ms 8 ms 7 ms dstswr1-vlan4.rh.nyk4ny.cv.net [67.83.221.193]
4 9 ms 9 ms 14 ms dstswr1-ge3-12.rh.nyk4ny.cv.net [67.83.221.137]
5 12 ms 14 ms 12 ms 64.15.2.29
6 * * * Request timed out.
7 12 ms 10 ms 13 ms cr2-nyiix-peer.nym009.internap.net [198.32.160.1
85]
8 11 ms 11 ms 15 ms nym008-nym009-82-core3.nym008.internap.net [66.7
9.152.130]
9 11 ms 11 ms 10 ms border2.pc1-bbnet1.ext1.nym.pnap.net [216.52.95.
15]
10 11 ms 11 ms 12 ms v-63-251-20-181.virt-machine.internap-nyc.nfoser
vers.com [63.251.20.181]
Trace complete.
C:\Users\Rob>
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Rob>tracert 63.251.20.181
Tracing route to v-63-251-20-181.virt-machine.internap-nyc.nfoservers.com [63.25
1.20.181]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms 192.168.1.1
2 8 ms 7 ms 11 ms 10.240.180.25
3 10 ms 8 ms 7 ms dstswr1-vlan4.rh.nyk4ny.cv.net [67.83.221.193]
4 9 ms 9 ms 14 ms dstswr1-ge3-12.rh.nyk4ny.cv.net [67.83.221.137]
5 12 ms 14 ms 12 ms 64.15.2.29
6 * * * Request timed out.
7 12 ms 10 ms 13 ms cr2-nyiix-peer.nym009.internap.net [198.32.160.1
85]
8 11 ms 11 ms 15 ms nym008-nym009-82-core3.nym008.internap.net [66.7
9.152.130]
9 11 ms 11 ms 10 ms border2.pc1-bbnet1.ext1.nym.pnap.net [216.52.95.
15]
10 11 ms 11 ms 12 ms v-63-251-20-181.virt-machine.internap-nyc.nfoser
vers.com [63.251.20.181]
Trace complete.
C:\Users\Rob>
Run a speedtest at http://www.speedtest.net - click the big blue bar on top of the map that says "Begin Test", it will ping to the closest server near you.
I'm running Optimum Online Boost, and I would recommend anyone in the NY area to do the same. the total for your internet p/month would be $39.90 a month, and I can tell you it's well worth it, speeds get higher than what you see on my speedtest.
The server on a good day when it's equivalent I've seen run at 200mbps ^ and 200mbps v. I've seen it reach 600mbps ^ and 100mbps v when I first ordered it, but for all you know it could be better than both, as a speedtest is never ever 100% accurate.
You may also be receiving packetloss via comcast > line > modem. If you're using a 3-way coaxial converter, get one directly from comcast, not one from a hardware or appliance store. The same thing happened to me with optimum after viewing thousands of T3 timeouts in my modem logs. If you're using a router you can also try going directly to the modem, just for a test, anyway. Or maybe permanently if that helps.
I can tell you it's not your server.
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Rob>tracert 63.251.20.181
Tracing route to v-63-251-20-181.virt-machine.internap-nyc.nfoservers.com [63.25
1.20.181]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms 192.168.1.1
2 8 ms 7 ms 11 ms 10.240.180.25
3 10 ms 8 ms 7 ms dstswr1-vlan4.rh.nyk4ny.cv.net [67.83.221.193]
4 9 ms 9 ms 14 ms dstswr1-ge3-12.rh.nyk4ny.cv.net [67.83.221.137]
5 12 ms 14 ms 12 ms 64.15.2.29
6 * * * Request timed out.
7 12 ms 10 ms 13 ms cr2-nyiix-peer.nym009.internap.net [198.32.160.1
85]
8 11 ms 11 ms 15 ms nym008-nym009-82-core3.nym008.internap.net [66.7
9.152.130]
9 11 ms 11 ms 10 ms border2.pc1-bbnet1.ext1.nym.pnap.net [216.52.95.
15]
10 11 ms 11 ms 12 ms v-63-251-20-181.virt-machine.internap-nyc.nfoser
vers.com [63.251.20.181]
Trace complete.
C:\Users\Rob>
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Rob>tracert 63.251.20.181
Tracing route to v-63-251-20-181.virt-machine.internap-nyc.nfoservers.com [63.25
1.20.181]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms 192.168.1.1
2 8 ms 7 ms 11 ms 10.240.180.25
3 10 ms 8 ms 7 ms dstswr1-vlan4.rh.nyk4ny.cv.net [67.83.221.193]
4 9 ms 9 ms 14 ms dstswr1-ge3-12.rh.nyk4ny.cv.net [67.83.221.137]
5 12 ms 14 ms 12 ms 64.15.2.29
6 * * * Request timed out.
7 12 ms 10 ms 13 ms cr2-nyiix-peer.nym009.internap.net [198.32.160.1
85]
8 11 ms 11 ms 15 ms nym008-nym009-82-core3.nym008.internap.net [66.7
9.152.130]
9 11 ms 11 ms 10 ms border2.pc1-bbnet1.ext1.nym.pnap.net [216.52.95.
15]
10 11 ms 11 ms 12 ms v-63-251-20-181.virt-machine.internap-nyc.nfoser
vers.com [63.251.20.181]
Trace complete.
C:\Users\Rob>
Run a speedtest at http://www.speedtest.net - click the big blue bar on top of the map that says "Begin Test", it will ping to the closest server near you.
I'm running Optimum Online Boost, and I would recommend anyone in the NY area to do the same. the total for your internet p/month would be $39.90 a month, and I can tell you it's well worth it, speeds get higher than what you see on my speedtest.
The server on a good day when it's equivalent I've seen run at 200mbps ^ and 200mbps v. I've seen it reach 600mbps ^ and 100mbps v when I first ordered it, but for all you know it could be better than both, as a speedtest is never ever 100% accurate.
You may also be receiving packetloss via comcast > line > modem. If you're using a 3-way coaxial converter, get one directly from comcast, not one from a hardware or appliance store. The same thing happened to me with optimum after viewing thousands of T3 timeouts in my modem logs. If you're using a router you can also try going directly to the modem, just for a test, anyway. Or maybe permanently if that helps.
Re: Really bad latency/timeout on VDS
The last hop looks about the same as your first hop, in terms of red lines, and that indicates that there isn't a problem with InterNAP, or even with Comcast. The problem that I am seeing is with your router -- if HLSW is accurate, you're seeing packet loss and high latencies right there in your house. If you're on wireless, this probably indicates a poor wireless connection; if you're connected by wire to the router, you may be having a problem with the router itself, or someone or something on your network might be using up a significant portion of your available bandwidth.
I would recommend that you start your troubleshooting with that router, by rebooting it. If that doesn't help, try connecting directly up to your cable modem. If that doesn't work, run the test with a different computer.
(I also agree with TimeX that HLSW is not a very good tool for this. Using MTR would be best: http://www.nfoservers.com/forums/viewto ... =25&t=4272)
I would recommend that you start your troubleshooting with that router, by rebooting it. If that doesn't help, try connecting directly up to your cable modem. If that doesn't work, run the test with a different computer.
(I also agree with TimeX that HLSW is not a very good tool for this. Using MTR would be best: http://www.nfoservers.com/forums/viewto ... =25&t=4272)
-
- New to forums
- Posts: 11
- Joined: Thu Oct 28, 2010 6:54 am
Re: Really bad latency/timeout on VDS
Thanks Edge and everyone,
After Sunday, it seemed that the Server was back to normal- no lag, and everything was smooth. I guess it was just a bad connection on the InterNap side of things. Hopefully everything works out well from here on out. Thanks for all the help guys!
After Sunday, it seemed that the Server was back to normal- no lag, and everything was smooth. I guess it was just a bad connection on the InterNap side of things. Hopefully everything works out well from here on out. Thanks for all the help guys!
Re: Really bad latency/timeout on VDS
I'm glad that it fixed itself. This wasn't on the InterNAP side of things, though .