Website down monitor
Custom HTTP requests responses
Uptime & response times ping
SSL monitoring and domain expiration date monitoring
Configurable weekly/monthly email reports
Email notifications on incidents Slack, Twilio, Discord, Telegram, Webhook notifications on incidents
Our UptimeRobot has an easy-to-use API. It lets you get the details of your monitors, logs, create / edit / delete monitors, alert contacts and maintenance windows.
Public status pages
Create public or private status pages to showcase the availability of your monitors.
Display up to date stats, including history data.
Lightweight & fast (GTmetrix grade A)
Custom Domains system
Customizable, password protection, search engine block, social links and much more...
Monitoring cron jobs
You simply need to send a GET or POST request each time your cronjob runs, thats it.
Get notified when your cronjob stops working
Configurable weekly/monthly email reports about website downtime
Start tracking your website uptime.
Minimize your downtime by being the first to know about it!
Web page monitoring tool
Every status page you create gets useful and ready to go analytics.
Day by day analytics
Referrers & UTMs
Devices, browsers & operating systems.
Choose your plan
Frequently Asked Questions
Here are some answers to the most asked questions regarding this product.
How to check if website is down
After registration, add the site to the monitoring and set up notifications in a convenient messenger.
Are my website stats affected?
What are the differences between monitor types?
Here are short details about monitor 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: this 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.
- cron-job (heartbeat): good for servers/computers/devices that are inside an intranet (but connected to the Internet) and need to be monitored. The feature works in the opposite way compared to other monitoring types. UptimeRobot provides a unique URL for each heartbeat monitor created and expects the monitored item to send regular requests to this URL. Once a regular request doesn’t arrive on time, the monitor is marked as down