Here is a small and handy addition for having an extra level of security for the accounts. Two-factor authentication is a widely-used mechanism for making sure that the account is only reachable by you and Uptime Robot now supports it.
Uptime Robot can already check the status of servers/devices who have public IPs with its ping and port monitoring feature. Yet, there are many other servers/computers/devices that are inside an intranet (but connected to the internet) and need to be monitored.
A status page is a very easy-to-setup, nice and automated way to share the status of the websites/servers with visitors, users and teammates. And, the ability to share additional info with users like current issues or an upcoming maintenance can only make it better.
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.
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 the site or the caching is only time-based..).
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...
Uptime Robot is already integrated with the major team communication apps and here is another addition: Google Hangouts Chat.
Google had announced that Chrome would begin distrusting certificates issued by Symantec Corporation’s PKI and the decision is followed by other major browsers. These are the certificates by Thawte, VeriSign, Equifax, GeoTrust, and RapidSSL that are issued before 1st of December 2017.
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). So, here comes the HTTP method selection which enables us to choose the method, send the parameters to be sent (if needed) and also decide if the data will be sent as JSON or not.
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 :).
