THIS IS NOT SUPPORTED BY ME - JUST MIRRORING THIS SO PEOPLE CAN GET ACCESS

This is a copy of the standalone Monitor-IO image that was released when the service was discontinued.

Here is the README:

NetMonitor by monitor-io.com

NetMonitor is a standalone and open reuse of our previous I/O Monitor hardware.
Although the online services of monitor-io are no longer applicable, continuous
connectivity tests will be performed by NetMonitor directly.

Unlike the monitor-io service, there is no online web portal with NetMonitor and
everything is handled locally. All that is required to use this software is to
write the included image file to a microSD card using a microSD-to-USB adapter
and a software utility such as Win32 Disk Imager. You may reuse the microSD card
that is currently in the I/O monitor (found behind the black sticker on the
device).

What does NetMonitor do: By default, the netmonitor will continuously test
reachability to your default gateway and several Internet targets. It uses both
explicit IP addresses and site host names as targets, with packet loss and delay
being reported. In addition to the display, accumulated test results can be
viewed by using a web browser and going to the unit's IP address (which is shown
on the display periodically).

To login to the device (to either change the Internet targets, customize the
netmonitor script, or modify the configuration - all of which are optional),
use ssh with the username 'system' and password 'n3tm0n1t0r' (where 'e', 'i',
and 'o' are replaced by '3', '1', and '0' respectively). The default root
password is '2.7182818284'. The user can change either password if desired.

NOTE: Because the device uses a standard Linux operating system, unexpected
power interruptions should be avoided to maximize the SD card's filesystem
integrity. The recommendation is to login to the unit and perform a 'poweroff'
command whenever the unit is to be power cycled. If the filesystem does become
corrupted, the image file can be rewritten to the SD card (i.e., keep the
NetMonitor zip file saved somewhere as a backup).

Network impairment scenarios based on NetMonitor test results

• If all targets are seeing zero packet loss and the delay range is below the
  threshold set within the NetMonitor script (30 ms), connectivity should be good.

• If impairments are only observed with the Internet targets defined with a host
  name, but NOT those defined with an explicit IP address, there may be an issue
  with local DNS name resolutions. This may involve the local home router if it is
  performing a DNS proxy function for the home network. This can determined by
  checking if other home devices are using the default gateway IP address as their
  DNS server.

• If impairments are observed to all Internet targets but NOT to the local
  default gateway, the issue is likely with the connection to the ISP or the ISP
  itself (i.e., it's outside the home).

• If there are impairments to the local default gateway as well as the various
  Internet targets, the problem may be the local home router or the connection to
  it (i.e., it's inside the home).

• If impairments occur daily, but only during certain periods of time, the issue
  may be congestion during prime-time usage. If the impairments include the default
  gateway, the congestion is likely internal...else it's external.

• If small amounts of packet loss are observed all the time, without a higher
  than normal delay, the condition is likely a cable or equipment fault. If the
  loss includes the default gateway, the fault is likely internal...else it's
  external.