Uptime Robot provided 2 api-key types: a master api_key and monitor-specific api_key. The master api_key can be used to perform almost every action exists in the dashboard and it must not be revealed for the security of the accounts. Yet, there are cases where the api_key may needed to be revealed like using it in […]
Caching is a great way to improve website performance and minimize the load. An ideal cache displays the cached version until the content changes and flushes the cache when there is a change. Yet, there may be cases where the cached version is not the most up-to-date one (if there is a DB error on […]
All the requests sent from Uptime Robot are using pre-defined IPs to make sure that we all know the source of the requests. A new IP block is being added to the system: 216.245.221.80/28 And, if exists, please make sure it is whitelisted in your firewalls. Also, the full list of the IPs used can be found here. P.S.> […]
Uptime Robot treats all HTTP statuses equally. They mean either up or down… except HTTP 401. HTTP 401 is expected in some situations and not expected in others. Currently, HTTP 401 is handled as: If auth info is mentioned in monitor’s settings but HTTP 401 is returned, monitor is marked as down if no auth […]
Last Thursday (10 Jan 2019), starting with 02:30, we experienced an issue that caused a full downtime of ~12 hours and intermittent issues more than that afterwards. First of all, so so sorry about this. And, as a summary, it was totally our fault. Uptime Robot is available since Jan 2010 and it is the […]
Uptime Robot is already integrated with the major team communication apps and here is another addition: Google Hangouts Chat. If you already use Hangouts Chat (which is part of the G Suite of Google), the integration can be setup with just these few steps: Inside Hangouts Chat, create a new web-hook URL in Room menu>Configure webhooks>Add new. Inside Uptime Robot, create […]
Subscribe
