Operations | Monitoring | ITSM | DevOps | Cloud

Managing monitors has meant one of two things: the dashboard, or writing your own API calls. There is now a third. The official UptimeRobot CLI is live on npm, and it drives every monitor, incident, and status page in your account from the shell you already have open. It is free, open source under Apache 2.0, and works on every plan including the free one.

If your API answers on QUERY, you can now point a monitor straight at it. QUERY joins HEAD, GET, POST, PUT, PATCH, DELETE, and OPTIONS in the HTTP method list for HTTP, keyword, and API monitors. You can find it under the “Advanced settings” when editing or adding your monitor. QUERY became a standard in June 2026 as RFC 10008. It’s safe, idempotent, and it carries a request body.

We’re happy to introduce you to the first agentic uptime monitoring setup! Now your AI agents can continue their coding, testing, and deploy flows into setting up the monitors, including a free account. The agent submits your site’s URL and your email, you confirm with one click in the email you receive, and you have a working monitor plus a free account. No registration form, API key, or dashboard configuration needed.

For 15 years, UptimeRobot has answered one question for millions of people: is my site up? Today we’re taking on a related question that’s become just as important: is everything my site depends on up? We’ve acquired IsDown, which tracks the status of more than 6,000 cloud and SaaS providers in one place. Here are the details on what it is, why we bought it, and what we’re building with it.

In the evening of May 5th, 2026, large parts of the German web briefly went dark. For a few hours, anyone trying to load a.de address through a major DNS resolver got errors instead of websites. Bahn.de, Amazon.de, and Spiegel.de were among the affected. Major brands like Telekom, DHL, and Sparkassen felt it too, along with hosting providers Hetzner, Strato, and Ionos.

Most website monitoring tools look similar until the first real incident. That is when alert speed, false positives, check coverage, and day-to-day usability matter more than a long feature page. UptimeRobot often comes up early for a reason: it is easy to start with, clear to manage, and focused on the checks many teams need first. Still, it is not the only option worth looking at.

Are you one of those trying to desperately get your hands on a new RTX 3080, 3070, 3060 Ti, & 3090 in 2021? Or maybe you prefer the new PlayStation 5 or Xbox Series X console. Basically, any item that’s on pre-sale or hard to get (including the uniquely designed piece of clothing for your girlfriend). If your favorite online store doesn’t have a “watchdog”, we have the best solution for you. Now how would you know it’s already back in stock? There’s an easy way!

Port failures don’t always take a service offline. A port stops accepting connections, times out intermittently, or gets blocked by a firewall change, while everything else looks healthy. When that happens, users feel the break long before uptime checks notice. This article reviews port monitoring tools from an operational point of view. It looks at how they detect closed or slow ports, how alerts behave in noisy environments, and where basic checks fall short during real incidents.

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.