How can we help you?
- How can I pay?
You can pay with your Visa, Maestro, MasterCard, Discover/Novus, Diners Club and American Express card or use PayPal.
- What is the refund policy?
You may terminate your subscription to the Upgrade at any time and you will not be obligated to pay any additional fees for upcoming subscription renewal periods. However, any subscription fees you have paid in advance will not be refunded unless there has been 30 days or less since the payment. For payments made in the last 30 days or less, only those payments are refundable.
- Can I buy extra SMS and voice calls (for the free plan)?
Yes, you can buy Pro SMS (or voice calls) for both Pro and Free Plan in your
My Settings. Just click on the blue
Want to add more?button. Unfortunately, it’s only possible to use PayPal at the moment.
SMS / voice call alerts prices
Amount Price 100 messages/call $15.00/one-time 200 messages/calls $25.00/one-time 500 messages/calls $55.00/one-time 1000 messages/calls $100.00/one-time
SMS and voice calls are added to the account only once (they don't renew) and more messages/calls can be purchased anytime.
A notification is sent when a few messages/calls are left.
- How to cancel a subscription?
Log in to your account and go to
My Settings > Account profile > Plan > Manage subscription > Cancel subscription.
You will need to verify a captcha and enter an approval text to confirm the action.
- How can I download my invoices?
Find all your invoices in your account under
My Settings > Account Profile > Payment History.
- How do I update my credit card information?
To change the credit card details, please log in to your
Account's settings > Manage subscription > Change credit card used. You will be redirected to our payment processor’s page.
With the first visit, you need to create an account. For that use the order number you received in the order confirmation email from 2CheckOut and your email address used in the ordering process.
- Follow the instructions and set up your password.
- After you log in, go to
My Productsand click on
Update credit card info.
- Enter your card details and click on “Add credit card info”. Now you’re all set!
- You can also change your credit card details or remove the card from the “Payment Methods” page.
- Does UptimeRobot auto start the monitor whenever it is down?
The monitor is still active when it’s down and checking if the service is back up.
- Where are the monitoring locations and what are their IPs?
The main monitoring location is in Dallas-USA and there are other nodes in other countries/continents to verify down statuses.
Here are all the locations and IPs used:
- 18.104.22.168/28 (Dallas - USA)
- 22.214.171.124 - 2607:ff68:107::3 (engine5.uptimerobot.com) (Dallas - USA)
- 126.96.36.199 - 2607:ff68:107::4 (engine6.uptimerobot.com) (Dallas - USA)
- 188.8.131.52 - 2607:ff68:107::5 (engine7.uptimerobot.com) (Dallas - USA)
- 184.108.40.206 - 2607:ff68:107::6 (engine8.uptimerobot.com) (Dallas - USA)
- 220.127.116.11 - 2607:ff68:107::7 (engine9.uptimerobot.com) (Dallas - USA)
- 18.104.22.168 - 2607:ff68:107::8 (engine10.uptimerobot.com) (Dallas - USA)
- 22.214.171.124 - 2607:ff68:107::9 (engine11.uptimerobot.com) (Dallas - USA)
- 126.96.36.199 - 2607:ff68:107::10 (engine12.uptimerobot.com) (Dallas - USA)
- 188.8.131.52 - 2607:ff68:107::11 (engine13.uptimerobot.com) (Dallas - USA)
- 184.108.40.206 - 2607:ff68:107::12 (engine14.uptimerobot.com) (Dallas - USA)
- 220.127.116.11 -2607:ff68:107::13 (engine15.uptimerobot.com) (Dallas - USA)
- 18.104.22.168 - 2607:ff68:107::14 (engine16.uptimerobot.com) (Dallas - USA)
- 22.214.171.124/28 (Dallas - USA)
- 126.96.36.199 - 2607:ff68:107::15 (engine17.uptimerobot.com) (Dallas - USA)
- 188.8.131.52 - 2607:ff68:107::16 (engine18.uptimerobot.com) (Dallas - USA)
- 184.108.40.206 - 2607:ff68:107::17 (engine19.uptimerobot.com) (Dallas - USA)
- 220.127.116.11 - 2607:ff68:107::18 (engine20.uptimerobot.com) (Dallas - USA)
- 18.104.22.168 - 2607:ff68:107::19 (engine21.uptimerobot.com) (Dallas - USA)
- 22.214.171.124 - 2607:ff68:107::20 (engine22.uptimerobot.com) (Dallas - USA)
- 126.96.36.199 - 2607:ff68:107::21 (engine23.uptimerobot.com) (Dallas - USA)
- 188.8.131.52 - 2607:ff68:107::22 (engine24.uptimerobot.com) (Dallas - USA)
- 184.108.40.206 - 2607:ff68:107::23 (engine25.uptimerobot.com) (Dallas - USA)
- 220.127.116.11 - 2607:ff68:107::24 (engine26.uptimerobot.com) (Dallas - USA)
- 18.104.22.168 - 2607:ff68:107::25 (engine27.uptimerobot.com) (Dallas - USA)
- 22.214.171.124 - 2607:ff68:107::26 (engine28.uptimerobot.com) (Dallas - USA)
- 126.96.36.199/28 (Dallas - USA)
- 188.8.131.52 - 2607:ff68:107::27 (engine29.uptimerobot.com) (Dallas - USA)
- 184.108.40.206 - 2607:ff68:107::28 (engine30.uptimerobot.com) (Dallas - USA)
- 220.127.116.11 - 2607:ff68:107::29 (engine31.uptimerobot.com) (Dallas - USA)
- 18.104.22.168 - 2607:ff68:107::30 (engine32.uptimerobot.com) (Dallas - USA)
- 22.214.171.124 - 2607:ff68:107::31 (engine33.uptimerobot.com) (Dallas - USA)
- 126.96.36.199 - 2607:ff68:107::32 (engine34.uptimerobot.com) (Dallas - USA)
- 188.8.131.52 - 2607:ff68:107::33 (engine35.uptimerobot.com) (Dallas - USA)
- 184.108.40.206 - 2607:ff68:107::34 (engine36.uptimerobot.com) (Dallas - USA)
- 220.127.116.11 - 2607:ff68:107::35 (engine37.uptimerobot.com) (Dallas - USA)
- 18.104.22.168 - 2607:ff68:107::36 (engine38.uptimerobot.com) (Dallas - USA)
- 22.214.171.124 - 2607:ff68:107::37 (engine39.uptimerobot.com) (Dallas - USA)
- 126.96.36.199 - 2607:ff68:107::38 (engine40.uptimerobot.com) (Dallas - USA)
- 188.8.131.52 - 2604:a880:800:10::4e6:f001 (remote7.uptimerobot.com) (New York - USA)
- 184.108.40.206 (remote2.uptimerobot.com) (Singapore)
- 220.127.116.11 - 2400:6180:0:d0::16:d001 (remote18.uptimerobot.com) (Singapore-2)
- 18.104.22.168 - 2604:a880:cad:d0::18:f001 (remote19.uptimerobot.com) (Toronto-2 - Canada)
- 22.214.171.124 - 2a03:b0c0:1:d0::22:5001 (remote16.uptimerobot.com) (London-2 - UK)
- 126.96.36.199 - 2a03:b0c0:0:1010::2b:b001 (remote15.uptimerobot.com) (Amsterdam-2 - Netherlands)
- 188.8.131.52 - 2604:a880:cad:d0::122:7001 (remote10.uptimerobot.com) (Toronto - Canada)
- 184.108.40.206 - 2a03:b0c0:3:d0::44:f001 (remote14.uptimerobot.com) (Frankfurt-2 - Germany)
- 220.127.116.11 - 2604:a880:400:d0::4f:3001 (remote17.uptimerobot.com) (New York-2 - USA)
- 18.104.22.168 - 2a03:b0c0:1:d0::e54:a001 (remote4.uptimerobot.com) (London - UK)
- 22.214.171.124 - 2600:1f16:775:3a01:70d6:601a:1eb5:dbb9 (remote12.uptimerobot.com) (Ohio - USA)
- 126.96.36.199 - 2a03:b0c0:0:1010::832:1 (remote3.uptimerobot.com) (Amsterdam - Netherlands)
- 188.8.131.52 - (mail2.uptimerobot.com) (Dallas - USA)
- 184.108.40.206 - 2600:1f18:179:f900:88b2:b3d:e487:e2f4 (remote20.uptimerobot.com) (Virginia - USA)
- 220.127.116.11 - 2a03:b0c0:3:d0::33e:4001 (remote11.uptimerobot.com) (Frankfurt - Germany)
- 18.104.22.168 (remote1.uptimerobot.com) (Dublin - Ireland)
- 22.214.171.124 - 2600:1f11:56a:9000:23:651b:dac0:9be4 (remote13.uptimerobot.com) (Montreal - Canada)
- 126.96.36.199 (remote9.uptimerobot.com) (Tokyo - Japan)
- 188.8.131.52 (remote8.uptimerobot.com) (California - USA)
- 184.108.40.206 (remote5.uptimerobot.com) (Sydney - Australia)
- 220.127.116.11 (remote6.uptimerobot.com) (Seo Paulo - Brazil)
And, here they are in .txt format in case you prefer to whitelist them in the firewall rules automatically:
P.S. Remote nodes currently have dynamic IPv6 addresses and they are not mentioned for this reason.
- 18.104.22.168/28 (Dallas - USA)
- Do I need to whitelist UptimeRobot on my server? How?
- What are the differences between monitor types?
Here are short details about monitor types:
- http(s): it'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)
- port: good for monitoring services like SMTP, DNS, POP as all these services run from a specific port and UptimeRobot decides their statuses if they respond to the requests or not
- keyword: checks if a keyword exists or not exists in a web page
- 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
- I am monitoring a file availability, but the monitor status is “down”. Why?
The limit for the file size is 8 MB. If it’s bigger, we recommend setting the HTTP method to HEAD. You will find it under the “Advanced settings” when editing a monitor.
- How long does it take before I get a ConnectionTimeout?
Currently it's 45 seconds, but we will add a feature where you will be able to set your custom timeout soon.
- I am just wondering if there is a way to group monitors?
Unfortunately, this feature is not available at the moment, but it’s already on the feature requests list.
- When will I be notified about the SSL expiration date?
You will receive a notification 30 days in advance, in case of Let’s Encrypt certificate it’s 3 days before the expiration date.
- How do you detect downtime?
- UptimeRobot sends HTTP requests every x minutes from its main engine (US-Dallas)
- If no response is received, another request is sent from the same location (in case the previous one was just a hiccup)
- If no response is received again, it sends 2 other requests in parallel from 2 random and remote locations (the list of locations can be found at: https://uptimerobot.com/locations)
- If these 2 remote requests fail to get a response too, then the monitor is marked as down and notifications are triggered
- Or, if the monitor returns an erroneous HTTP status, it is instantly marked as down without verification (as the status is returned from the monitor itself)
- And, once a monitor is down, UptimeRobot keeps sending requests every 1 min (no matter the default monitor interval) for faster uptime recovery, only from the main location
- So, in case of a 30 min downtime (except HTTP-status-based downtimes), the monitor needs to:
- fail to respond twice from the main engine
- fail to respond from 2 remote locations
- and must have failed to respond at least 20-25 times in a row from the main location (as the requests are sent only from the main location once the monitor is down)
There are some rare/edge scenarios like:
- our requests/IPs may have been temporarily blocked by a firewall
- there may have been a problematic hop between UptimeRobot's servers and monitor's server. And, if all the requests UptimeRobot has sent passed from that problematic hop at some point, the requests may have failed and UptimeRobot would think that the site didn't respond. This is the main reason we send "verification requests" from multiple locations to minimize this risk and it is very very low
- both of these scenarios have a very low possibility, yet, still wanted to share.. just in case
For the Pro Plan, it is possible to:
- get a “DOWN” notification only if the monitor is down for x minutes
- and, optionally, keep getting the “DOWN” notifications every y minutes
Simply, you may configure your settings like “if down for x minutes alert once” or “if down for x minutes, alert every y minutes“. Please check our related blog post for details.
- Someone redirected my website to another one, is it possible to detect this?
Actually, you can use the Keyword monitor which is available for the Free-Plan as well.
Keyword Monitor is searching for the keyword you entered but that's not all of that, for there is a condition you must select too.
- Keyword Exists
- Keyword Not Exists
Based on the condition you select the Keyword Monitor will decide if the monitor will be “DOWN” or “UP”.
If the condition you selected becomes true, the monitor will show “DOWN” and notify you, if not, the monitor will keep showing “UP” and no alert notification fired.
For example: If you choose the condition Keyword Exists then the monitor will turn “DOWN” if it finds the Keyword on the page and will notify you.
- How can I test notifications?
The best way to get test notifications will be:
- Create a new monitor with URL: https://youromain.com and attach an alert contact to it.
- Wait for a minute.
- Update the URL to https://youromain.com/notExistsingURL.
- Wait for a minute and the "DOWN" notification must arrive.
- Update the URL back to https://youromain.com and the "UP" notification must arrive.
- Delete the monitor.
This way, you'll see the whole info regarding the notifications.
- How do we go about viewing logs after we hit the "reset" button on the dashboard for a URL that we are monitoring?
Unfortunately, if you clicked on the “Reset States” all logs for this monitor will be erased and there is no way to return them back.
- We have a website we've set up so it’s only accessible in the USA. Is it possible to lock in the check so even secondary requests come from servers in the USA?
Unfortunately, this feature is not available at the moment.
- If I set your service to monitor a webpage that is under Cloudflare always online caching, will it detect downtime?
In order to make it work correctly, you must disable the "cloud feature of Cloudflare for the related CNAME".
- Why is UptimeRobot free?
That's a good question. UptimeRobot is launched in January 2010 and it is totally free since then.
It all started with the desire to create a useful and available tool for the web community. After some time, the service grew so much, we spent lots of hours improving it and learned a lot.
Update 13 Jan 2015: We have introduced a Pro Plan today. And, the Free Plan is still here to stay :)
- Are my website stats affected?