Following our latest updates, which, from now on, we’d love to share with you regularly, we’re happy to announce last month’s news. There’s always space for improvements while doing necessary maintenance, so let’s take a look at it.
While the world is getting more optimistic with the wave of vaccine options, we’re looking forward to introducing you to our latest news. We’re happy to say we managed to fulfill some of our last year’s promises and are still working on our plans and improving UptimeRobot. We introduced a completely redesigned mobile app and new status pages, with many new features. We entered the new year enthusiastically and kept on being busy. Let’s take a look at what’s new!
As promised in our latest update in June, we have prepared the new public status pages. We’ll deploy them after this beta period so your feedback will be much appreciated! What’s new, how does it look and how can you use it?
Hello everyone, Peter here, nice to e-meet you. Let me briefly introduce myself and share some insights about what has been going on with UptimeRobot lately and what the future plans are.
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...
