Operations | Monitoring | ITSM | DevOps | Cloud

SSL failures don’t usually break a site all at once. A certificate expires, a chain changes, or a browser update tightens rules, and users start seeing warnings before teams notice. By the time alerts fire, trust has already taken a hit. This post reviews SSL monitoring tools from an operational standpoint. How they detect upcoming expirations, validate certificate chains, and surface issues across environments and domains.

On November 18th, 2025, a large Cloudflare outage briefly broke big chunks of the internet. For several hours, users around the world were greeted with 500 errors, including platforms like X, ChatGPT, Spotify, and many others that run behind Cloudflare’s network. At UptimeRobot, we sit in a slightly unusual spot during events like this: So when Cloudflare has a bad day, we see it twice: once in the alerts we send to our customers, and again in how it affects parts of our own infrastructure.

As you may have noticed, we released the latest version of the UptimeRobot API a few weeks ago. Don’t worry, the v2 will remain available; however, it will no longer receive support or updates. New features will be added only to v3. Built on a RESTful architecture, v3 unlocks more flexibility, cleaner workflows, and expanded capabilities for developers who want tighter control over their monitoring. Below, we’ll highlight what’s new and how it compares to the legacy v2 API.

We’re excited to introduce Monitor Grouping, a new way to organize your monitors directly from the UptimeRobot dashboard. This feature makes it easier to keep track of large sets of monitors and quickly see the health of related services at a glance. Monitor Grouping is available on Solo, Team, and Enterprise plans starting today. Downtime happens. Get notified! Join the world's leading uptime monitoring service with 2.1M+ happy users. Register for FREE.

We’re excited to announce the official release of the UptimeRobot Terraform provider, a feature that many of you have been requesting. Starting today, you can manage your UptimeRobot resources, including monitors, alerting integrations, maintenance windows, and public status pages, directly in your Terraform configuration. Let’s take a closer look.

We’re excited to announce a powerful new addition to your monitoring toolkit: DNS Monitoring is now available on UptimeRobot! DNS (Domain Name System) is a core component of internet functionality. When DNS records are misconfigured, hijacked, or simply expire, they can lead to serious outages, broken email services, or even security risks. That’s why we’ve introduced DNS Monitoring – to help you stay in control of your domain’s health at all times.

Performance issues can sneak up before they turn into full-blown outages. Get notified when your website or service takes longer than usual to respond. We’re excited to announce that you can now set up response time thresholds and receive alerts when performance dips below your expected level. This means you can take action early, improve user experience, and prevent minor slowdowns from becoming major problems.

We’re excited to unveil a long-awaited feature—Location-specific monitoring! Track uptime from the regions that matter to you and identify localized outages in time. You’ll also receive alerts for each monitor you create, ensuring you never miss a beat in any location.

Hey everyone! We’re back with some exciting news for all Status page users. Thanks to your feedback, we’ve added the option to switch your status page to any of the following languages with a single click: You can create separate status pages for each language in all paid plans. Go try it now! Translate Status Page Now Tip: Want to be part of future improvements? Drop your feature ideas on our Nolt board or vote on existing ones.

Hi everyone! Slack has updated the process for adding webhooks. If you created your Slack integration after November 2024, it will continue to work. However, if it was created before that date, it is now obsolete. We strongly recommend updating it to prevent potential issues in case Slack discontinues support.