Blog.

Uptime Robot sends HEAD requests for HTTP monitors and GET request for keyword monitors by default (and, this is a good default setting for most monitors). On the other hand, there are cases when a customization may be needed, like: Checking if a form in the website works as expected Monitoring your APIs which expect specific methods (a […]

There is never “too much” when it comes to the ways of getting notified about an emergency. And, in some cases, this emergency can be a website or server going down. Today, voice call notification is added to Uptime Robot and it can be very helpful when we want to make sure that a notification is heard :). How to […]

Uptime Robot sends notifications for down and up notifications by default for each alert contact type. However, there can be cases where you may only need the down or up notifications like: minimizing the SMS use handling only the up or down events via web-hooks getting only the SSL expiry notifications but ignoring up/down events There […]

Uptime Robot supports multiple methods to get notified about downtimes on mobile (SMS, push notifications via the mobile app, Pushbullet, Pushover or Boxcar). And, SMS is one of the most reliable notification methods specially when no data plan exists. Also, many users prefer to configure their SMS alert contacts as: “alert if down for x minutes” […]

Getting the notifications inside the team communication app you use can make things easy as this may be where you’ll be discussing how to make that website/server back online. Besides the Slack integration, Uptime Robot now has support for Microsoft Teams too. It simply works by creating an incoming webhook URL at the Teams app and creating a […]

In case you haven’t seen or used it, there is a “Bulk Actions link” just under the “Add Monitor button” in the left sidebar. It simply opens the “Bulk Actions dialog” and presents a set of actions that can be applied to monitors in bulk.   This feature is now more powerful with few important additions […]