Blog.

HTTPS is becoming the “default” for any website whether it is a blog, portal, e-commerce or corporate one. And, this year, Uptime Robot has sponsored 2 great projects, Let’s Encrypt (a free SSL CA) and Caddy (a free web server with SSL built-in) to help to push this forward. However, a website with an SSL certificate requires […]

Cloudflare is an impressive service/platform for securing and speeding up websites. If you use Cloudflare and have a “status page with a custom-domain” in Uptime Robot, “there may be a small configuration needed” to make sure things work smooth. IMPORTANT: These settings don’t work with flattened CNAMEs, disable this feature first. Who needs the custom configuration? If […]

For HTTP monitors, Uptime Robot considers them as up or down according to the HTTP statuses returned (or if “no response returns at all”). If the HTTP status returned is: between 200 and 399, it is considered as “up” bigger than 399, is considered as “down” with an exception: equals 401 and no authentication info is defined, it […]

Uptime Robot, by default, sends all HTTP requests with pre-defined HTTP headers. Now, it is possible to customize this totally with the “Custom HTTP Headers” feature that can be found in the Pro Plan’s “Add/Edit Monitor Dialog>Advanced>Custom Headers” option. Sample use cases: For monitoring the mobile version of a web page, we can use a mobile “User-Agent” […]

Getting notifications of downtime/uptime via Slack or HipChat is widely used. Yet, until now, it was only possible to “target” rooms and not users. There is now a “custom text” feature in the “Add/Edit Alert Contact” dialogs for HipChat and Slack where the text mentioned there will be sent with each notification. As an example, we can […]

Public Status Pages, a feature to easily share the statuses of the monitors with others, was introduced few months ago. The standard status page URLs (like https://stats.uptimerobot.com/xyz) were HTTPs-enabled since day one. However, the ones behind a custom domain (like http://status.mywebsite.com) were not as it was a little more tricky to get a SSL certificate for […]