Types of monitors: Check HTTP, ping, ports and keywords
Get alerted: Email alerts are really easy to setup
Stats: View the uptime, downtime and response-times
Verification: Multiple servers perform the monitor check
Public Status Page: Display your stats on the web (demo)
Common Answers & Question
Why (or what) reason do I want to monitor uptime?
It is a useful, affordable tool that you can use to hold people accountable for. Also, it provides more insight and stats into what kind of service you are paying for.
Where are the uptime monitoring locations?
The main monitoring location is in Dallas Texas because everything they do is bigger. There are other nodes in other locations to verify the down status. Countries like Ireland, Singapore, Netherlands, Brazil, Australia Germany, and Japan plus our buddy to the north... Canada.
Nope, not at all. This service is entirely white-labeled and unobtrusive. This means, you'll never have to worry about skewed stats or bad requests.
What are the differences between Monitoring Types?
http(s): that's perfect for website monitoring. The service regularly sends requests (which are the same as if a visitor is browsing your website) to the URL and decides if it is up or down depending on the HTTP statuses returned from the website (200-success, 404-not found, etc.)
ping: is good for monitoring a server. Ping (ICMP) requests are sent and up/down status is decided according to the "if responses are received or not". Ping is not a good fit for monitoring websites as a website (its IP) can respond to ping requests while it is down (which means that the site is down but the server hosting the site is up)
keyword: checks if a keyword exists or not exists in a web page
port: good for monitoring services like smtp, dns, pop as all these services run from a specific port and Uptime Robot decides their statuses if they respond to the requests or not.
You'll wanna read our emails...
We send just a few out each year, but they are packed with tips, tricks, hints and advice.