Customer Help

The “Bulk Actions” feature is a bit hidden, true (we’re already working on a redesign, don’t worry). You can pause, start, reset or delete your monitors, change intervals, alert contacts and SSL settings, or add a maintenance window.

You can also change the notification settings for your attached alert contacts to be notified every “xy minutes if down for xy minutes”. This is a Pro Plan feature.

The monitor is still active when it’s down and checking if the service is back up.

To get a full list of our IPs, please, follow this article.

In some special cases you have to give an access to the monitored location manually. It depends on server or software you are using. If you need to whitelist UptimeStudio, here are the IPs.

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 UptimeStudio 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. UptimeStudio 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

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.

• UptimeStudio 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 here)
• 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, UptimeStudio 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 UptimeStudio’s servers and monitor’s server. And, if all the requests UptimeStudio has sent passed from that problematic hop at some point, the requests may have failed and UptimeStudio 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.

If your monitor status changed and you didn’t receive a notification, make sure you have attached the alert contact to your monitor. Click on the Settings button next to your monitor on the left side and then “edit”.

Here on the right side you can find all your alert contacts where you can add them.

In the Pro Plan you can find “advanced options” under your alert contacts and set the notification to be sent after “xy minutes” “if down for xy minutes”. This is a Pro Plan feature.

Click on the “Add Alert Contact” in your Dashboard after you have logged in at UptimeStudio.in and choose Slack Alert Contact type.

Enter the Friendly Name of your contact and your Slack Webhook URL. You can find the link to where it can be created in the blue windows below. You will be redirected to the app to create the webhook.

Custom value would add a specific text to each notification you receive on Slack.

Click on the “Add Alert Contact” in your Dashboard after you have logged in at UptimeStudio.in and choose Pro SMS Contact type.

Here you need to enter a Friendly Name of your contact, select the country and enter your Number in a correct format.

Important: You need to activate your number by clicking on the lock icon and entering the activation code you will receive through an SMS message sent to your number.

You will receive a notification 10,15, days in advance, in case of Let’s Encrypt certificate it’s 3 days before the expiration date.

The best way to get test notifications will be:

1. Create a new monitor with URL: https://youromain.com and attach an alert contact to it.
2. Wait for a minute.
3. Update the URL to https://youromain.com/notExistsingURL.
4. Wait for a minute and the “DOWN” notification must arrive.
5. Update the URL back to https://youromain.com and the “UP” notification must arrive.
6. Delete the monitor.

This way, you’ll see the whole info regarding the notifications.