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

I have been tasked with finding the cause of sporadic performance issues on a website that I didn't build or host, after doing a number of tests I suspect it may be an issue with the network rather than the server or the webapp its self.

I was wondering if anyone knows of a good too do monitor network performance remotely over a period of time, for example I would like to do a traceroute repeatedly over several hours and record the results.

share|improve this question
traceroute really isn't the right tool for performance monitoring\measuring. – joeqwerty Nov 22 '10 at 13:36
up vote 1 down vote accepted

From your description it sounds to me like you are looking to do a quick one-off solution to this monitoring situation that something permanent and robust. If this is true than I recommend seeing if you can:

  1. Quickly set up pingdom to get latency as an hourly average. If you need more detail, just leave a ping running from your home PC.
  2. Contact that ISP to see if they keep network graphs.

If you want to do something more extensive than I would recommend both a remote and local Nagios installation to monitor all of this. You will also be able to capture the hosts resource usage.

Lastly, for what it is worth I usually find it is not the network if you have decent hosting. Make sure you checked all the logs. scheduled tasks, and monitored the DB for long running queries.

share|improve this answer
ISP in question is a 3rd tier ISP and the performance of the website in question is worse and has more sporadic connection problems in the same building than on my home broadband, every test I have run suggests the server, the webapp and the database are all humming along nicely. But if i go back to the network guys and tell them I think its there problem they won't listen unless I have evidence. – 3urdoch Nov 22 '10 at 13:50
In that case I would just leave a ping running from the building. Once that shows packet loss or high latency that should be enough evidence ... – Kyle Brandt Nov 22 '10 at 13:55

A tool like MTR (or WinMTR) or PingPlotter that tracks per-hop (like traceroute) latency over time can be really useful for a problem like that - it can allow you to see where in the network path the problem is.

share|improve this answer

Check out SmokePing. It does pretty-much exactly what you are asking.

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.