I have subscribed to a new ISP and I am experiencing problems with this new ISP. The problems are several micro interruptions on the internet connection, kind of lags, that is probably related to timeouts on their proxies or in my connection to their network.

As these micro interruptions occur at random, I cannot prove that, because every time they send a technician to my office the problem is not detectable, specially because the service may be stable for 3, 4 hours and then start to show the problem again.

It is very annoying for two reasons. I am downloading something and then the download stops suddenly and I have to start again. Another reason is that I use a VoIP box connected to my phone using ethernet and this VoIP box loses connection every time, and my VoIP phone stops receiving/making calls, forcing me to restart the box every time I detect it and to stay hours with the phone down, without noticing.

My question is: How can I monitor the internet service for a period, telling me when the service is down, plot a graphic or something like that? Any tool or some way for monitoring the quality of the network or connection that can run on a Mac?

My idea is to have something to show them and prove I am right.

  • 1
    This Q may really be on topic, it fits the "good question" template (from How do I ask a question that may require recommending software? ) "I have <problem-x - network interruptions > that I don't know how to solve. I've already tried X, Y, Z (restart VoIP when I detect it) , but those programs don't work because this or that. How do I do this?" Is the only problem basically asking for a "Tool for monitoring internet connection" instead of saying "How to monitor internet connection for interruptions? – Xen2050 Apr 6 '16 at 14:52

Take a look in the logs there as a start.

You could also look into ntop or Little Snitch.

  • 1
    ntop.org < correct link to ntop (i think) – Frank Lämmer Mar 14 '15 at 13:35
  • Search for en0 or en1 once you open console.app (your network interface name(s)) to see network info. – Justin Sep 30 '15 at 20:52

If you use the following:

ping -A -i 10 --apple-time > monitor.txt

It will run continuously until stopped and ping every 10 seconds to (change for your address)

The --apple-time means that it will log the time of each ping so you can see failures. Like so:

11:33:10.793801 64 bytes from icmp_seq=0 ttl=58 time=27.744 ms
11:33:11.780250 64 bytes from icmp_seq=1 ttl=58 time=9.757 ms
11:33:12.781136 64 bytes from icmp_seq=2 ttl=58 time=10.150 ms
11:33:13.782932 64 bytes from icmp_seq=3 ttl=58 time=11.779 ms
11:33:14.785446 64 bytes from icmp_seq=4 ttl=58 time=11.254 ms
  • This doesn't timestamp when the request times out. If you're manually reading the logs you could infer based on the times of successful pings, but if you're trying to analyze it in another program or graph or something it might not work out as well. – tenmiles Oct 6 '20 at 16:58

How about ping running in Terminal? Just find a server that's on and responds to pings. While it doesn't show the exact times, it gives you some kind of proof that something's wrong.

Edited to add: I've used it myself a while ago for a similar. While they maintained that my (aging, to be honest) wireless access point might be at fault, since they didn't find anything, "I have ping timeouts at least once every hour" helped in getting the engineer to check on stuff.


This app logs your connection status and even claims it is used internally by Apple.

Log your network outages, graph speeds over time, and more. Network Logger Pro can also be used to monitor web sites and produce historical graphs of their speeds, outages, and response times.


It's $10 though :/



To monitor internet connection, you can simply use ping command. It just sends ICMP ECHO_REQUEST and expects the response.

Ping your router IP, when it's not responding, you can report to your ISP as internet interruption.

If your router has firewall, use arping instead, or simply chose another remote host, e.g.

$ ping
PING ( 56 data bytes
64 bytes from icmp_seq=0 ttl=57 time=37.710 ms
64 bytes from icmp_seq=1 ttl=57 time=32.051 ms


To monitor your physical connection to the router, you can use arping, e.g.

$ sudo arping

This is especially useful when your WiFi keeps dropping and your router doesn't respond to standard ICMP packets. Install via Brew (brew install arping).


There is tcpdump which can dump traffic on a network. For example to dump all outgoing packets into port 80 and 443, the syntax could be:

sudo tcpdump -i en0 port http or port https

To write into the file, add -w file, then read it via -r file. This will include exact timestamps of each network packets being received or sent.

To check whether the internet is interrupted, look for SYN packets (in Flags section) which your computer sends, and for each one the server should reply with a SYN-ACK. If that is not happening and there is no any traffic going back (just SYN packets, then there is no internet connection).

  • Is there an easy way (like a script) that automatically searches the tcpdump output looking for SYN packets that have no corresponding SYN-ACK reply? – Xen2050 Apr 6 '16 at 14:55
  • @Xen2050 I think I would grep the dump or output by looking for S flag like: sudo tcpdump -i en0 -nl | grep -C5 "Flags .S", from there, if you've ack in the context (extra | grep ack), than means something responded. So you need something opposite. I think you you find some awk/sed syntax that can find 5 SYN packet in a row, then it can alert that something wrong (unless you're contacting some dead host). – kenorb Apr 6 '16 at 15:06
  • For live monitoring, ping -A www.yahoo.com will beep when connection goes down. While you can use an IP address, using a human-readable address will test DNS failures as well. – brianfit Jan 23 '17 at 15:09

For my own usage, I have written a simple Bash script to check for this. It uses ping as way to monitor for timeouts, exactly as most answer suggest you do. The advantage of the script is that the output on your screen only shows the pings that timed out, rather than including successful pings as well. In addition you can pass a parameter for the duration of the monitoring, rather than the number of ping attempts. In short it's just a wrapper for the following: ping google.com -i 1 -c 60 | grep "timeout\|statistics\|transmitted\|avg" Its source and simple installation instructions are available at the below link:


I tested the script on macOS and Ubuntu Linux.

#Usage: ./monitor-timeouts.sh [duration] [target]
#example: ./monitor-timeouts.sh 60
if [ $# -eq 0 ]; then
if [ -z "$2" ]; then
pings=$((60 * $minutes))

if [[ $system == *"Linux"* ]]; then

echo "Start monitor for network timeouts at `date` for $minutes minute(s)."
echo "Target host: $target"
ping $target -i 1 -c $pings $extraflag | grep -i "timeout\|unreachable\|no answer\|statistics\|transmitted\|avg"
echo "End monitoring at `date`."

  • Welcome to Super User! Your script is short enough to include in your post; you should edit your answer to include it – bertieb Mar 8 '19 at 8:39
  • Thanks for the suggestion – Superman.Lopez Mar 8 '19 at 9:03

That was one of the symptoms I was having, besides low throughput. It turned out to be the cable modem. The good news is you may not have to convince anybody to get a new cable modem. My ISP turned out to have the policy that you could just swap your cable modem for a new one pretty much at will. Check and see if yours will do that.

  • Interesting, but you got to the point. Yes, my connection unfortunately is by cable modem, but it is a brand new (it was installed by them a month ago). I suspect the problem is their cable network. I never liked cable internet (I was forced to use them, because there's no other broadband company offering services in my region). – Duck Oct 27 '10 at 12:48

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

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