Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Our hosted servers are experiencing periods of very slow network access. During these periods pinging from any of our servers to the default gateway results in ping times of up to 500ms (instead of the normal 2-3ms). There are no packets lost.

The ISP is claiming their network is OK and the problem must be with the hosting service. The hosting service guys claim they have nothing at level 3 and everything according to them is OK.

I'm think our servers are connected to a switch which is connected the default gateway over a shared ATM line. Traceroute doesn't show any routers on the path.

Before changing my service providers, is there anything I could check that might explain what is causing this issue?

share|improve this question
I'm confused about your claim that "pinging from any of our servers to the default gateway results in ping times of up to 500ms". Are you talking about your LAN servers to your own gateway?, or the hosted servers to their own gateway? – l0c0b0x Jun 8 '09 at 6:14
my hosted servers to their gateway. Their gateway is not on the same lan, but ping should be less than 4ms – DanJ Jun 11 '09 at 22:32
up vote 2 down vote accepted

Routers don't prioritize handling ICMP to themselves. Pinging a router and getting high latency means nothing (well, not what you want anyway). What happens if you ping a unix system one router-hop away? Or since we are dealing with 500ms if that is the latency then that will show up clearly if you ping anyone on you continent.

share|improve this answer

You might also want to try mtr (mtr-tiny is a nice package I have on every server).

It will give you details about all the hops that are between you and the target. Give it a try.

share|improve this answer

Are pings equally slow using hostname and IP address? This could be an issue of a slow DNS server.

share|improve this answer
That (DNS problem) would affect only the first ping of the set. – gbarry Jun 8 '09 at 6:31
It would also not affect the displayed time, only the time it takes to ping. – Thomas Jun 8 '09 at 6:37

PingPlotter will give you graphs of traceroute data over time so you can see exactly where and at what time you are getting problems.

share|improve this answer

Normally, I'd avoid pinging the default gateway to measure delay. Answering ICMP is about the least-prioritised task that routers do, so all that 500 ms delay means is that the router's busy (may not even be busy routing packets, if lots of people are pinging it, because they think that's a good way of gauging the network).

If at all possible, find a host on the other side of the default gateway and ping that. It gives you a much better idea if there's anything wrong.

One of the reasons that sort of thing (answering ICMP EHO requests and other non-essential traffic handling) is de-prioritised is to make it harder to cause a denial of service, simply by smurfing the router.

share|improve this answer

You could try arping as an alternative to the oft prioritised ICMP echo.

share|improve this answer

Pings are accurate only as far as ICMP is left to its defaults on their end, even then its really only an indication that something is alive and connected to the network.

ICMP is (almost) never left to its defaults and is sometimes ignored completely. If you want a better test, set up a simple echoreply service on your server then measure the round trip time for a packet filling {insert frame size here}.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.