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!
New IP Block
We are constantly expanding the infrastructure as the demand for our services increases. Lately, we have added another block of IPs we will start using for our monitoring engines in a few months.
Nothing will change regarding our current IPs. In case you need to whitelist them, you can always check the up-to-date list of UptimeRobot’s IPs.
The new IP block is 208.115.199.XX
Integrations
What you can start looking into already is the new UptimeRobot Plesk integration!
We’ve also partnered with PagerDuty to make our integration more official and more publicly visible on their side as well. Nothing will change in terms of your existing configurations, but we’re exploring the possibilities of closer collaboration.
Improved Heartbeat and SSL Monitoring
The Heartbeat monitor was in public BETA until recently, and even though there still were some small issues after the full release, we managed to improve the reliability and stability.
We also added support for more SSL errors to widen the use of our SSL monitoring and improved the reliability as well.
Mobile App Updates
We’re really happy you like our new mobile app for iOS and Android. The 4.5-star rating in Google Play and 4.7 in the App Store are proving it.
As promised, we are adding localization support for Spanish, German, French and Portuguese. We’ll consider adding more languages based on the needs of our community.
We also added notification on auto-signout and improved the stability and performance.
APIv2 Updates
Last but not least, we made some updates last month regarding our API (CORS Headers, etc.). In case you missed it you can read about it in more detail in the dedicated blog post.
What’s next?
We’d like to keep on posting monthly updates and news, so fingers crossed! There’s still a lot on our plate this year, including sub-accounts, email reports, root causes and custom HTTP(S) timeouts.
See you all in a month!
