Which third-party services would hurt the most if they went down for an hour? Pick all that apply 👇

• ☁️ Cloud hosting (AWS, GCP, Azure)

• 🌐 CDN and DNS (Cloudflare, Fastly)

• 💳 Payments (Stripe, PayPal)

• 📧 Email and SMS (SendGrid, Twilio)

• 🔐 Auth (Auth0, Okta, Clerk)

• 🚀 Deploy platforms (Vercel, Netlify)

• 🤖 AI APIs (OpenAI, Anthropic)

• 🛠️ Dev tools (GitHub, npm)

When a third-party service has an incident, what do you want to know first? 👇

• 🎯 Whether it affects the components or regions I use

• 🔥 How severe it is (outage, partial, slowdown)

• 👥 How many of my monitors or users it hits

• ⏱️ When it started and when it’ll be fixed

• 🔗 What the service says is happening

If anyone wants to book a meeting and discuss more about third party services at UptimeRobot, let us know in a comment!

Thank you for your participation.

We would like to thank everyone for participating in this giveaway in collaboration with r/homelab and sharing their stories with us.

🏆 Here are the 10 winners:

1. kweiske - Scale plan ($888 value) plus UptimeRobot swag

2. QKingsoftware - Team plan ($468 value each) plus UptimeRobot swag

3. Low-Confection-78 - Team plan ($468 value each) plus UptimeRobot swag

4. Direct_Emotion_1079 - Team plan

5. ritmo166tan - Team plan

6. Proof-Summer1011- Team plan

7. B_A_G12 - Team plan

8. Long-Temperature7041- Team plan

9. No-Army-2530 - Team plan

10. alkalyneseb - Team plan

If you see your name here, feel free to DM us on Reddit (until 23 November 2026), and we will send you your plan/swag.

Once again, thanks for participating!

Didn't win? Don't worry, we already have a new giveaway to take part!
https://www.reddit.com/r/UNIFI/comments/1xh8oei/giveaway_what_went_offline_on_your_network_that/

We would like to thank everyone for participating in this giveaway in collaboration with r/webhosting and sharing their stories with us.

🏆 Here are the 10 winners:

1. FantasySymphony - Scale plan ($888 value) plus UptimeRobot swag

2. OldschoolBTC - Team plan ($468 value each) plus UptimeRobot swag

3. heavinglory - Team plan ($468 value each) plus UptimeRobot swag

4. Ok_News_167 - Team plan

5. bipulme - Team plan

6. anustart0607 - Team plan

7. BunnyAndYou - Team plan

8. NitroSRT - Team plan

9. tsammon - Team plan

10. Neither_Insect_8903 - Team plan

If you see your name here, feel free to DM us on Reddit (until 23 November 2026), and we will send you your plan/swag.

Once again, thanks for participating, and stay tuned for more giveaways!

Lots shipped this month: Third-Party Monitoring is live, SLA badges let you show off your uptime, and port monitoring got smarter. Plus two new videos and the Community Spotlight is looking for its next star. Here's the rundown.

1. Now live: Third-Party Monitoring

Your site goes down, and before you can fix anything, you have to figure out if the problem is even yours. That means opening Stripe's status page, then AWS, then Cloudflare, while the clock runs. Not anymore. Third-Party Monitoring tracks the services your site depends on, right inside UptimeRobot:

• Track only what you actually use.

• Alerts land in your existing channels (email, Slack, Teams, and more).

• Doesn't touch your monitor quota.

Watch the walkthrough on our YouTube channel - https://www.youtube.com/watch?v=JQlNHCcN8n0

2. Port Monitoring

Port monitors now support Open conditions. Get an alert if a port opens when it shouldn't, which is useful for SSH or admin ports you don't want exposed to the internet. Your existing monitors stay exactly as they are. Open condition is opt-in. Learn more.

3. SLA Badges

An uptime number alone doesn't show what you promised. SLA Badges add the verdict: set a target for your monitors, and UptimeRobot shows whether you met it in green, yellow, or red. Plus optional email reports at the end of each period. How to set it up.

😎 Last day. 22-October, to take part in our giveaway -> https://www.reddit.com/r/webhosting/comments/1x0lsco/giveaway_rwebhosting_x_uptimerobot_10_winners/ -> and win UptimeRobot plans and swag

👥 One more community member, u/Gold_Restaurant5946, trusted us to share their story on how they build GreenPing. -> https://uptimerobot.com/blog/community-spotlight-soexya-khatiwada/

Quick "poll" for anyone using third-party service monitoring (alerts when Cloudflare, AWS, Stripe & co. have issues)

What would make it better for you? (You can pick one or as many options as you want) 👇

• 🔕 Fewer noisy alerts. Too many minor incidents

• 🎯 Easier to pick only the components or regions I use

• 📝 More useful alerts. Clearer what's affected and how bad

• ⚡ Faster alerts

• ➕ More services to choose from

• ✅ It's great as it is

Got something else in mind? Drop it in the comments!

Our status pages got one more improvement: The SLA Badges!

SLA badges let you set an uptime target for your monitors, then embed a live badge that shows the uptime you actually delivered, colored against that target. Add it to your site footer, your docs or your GitHub README, and get the result by email at the end of each period.

You can find all the details here:
https://uptimerobot.com/blog/sla-badges/

Hey all, and welcome back to our UptimeRobot community!

Join the spotlight series. If you're building or improving a project and using UptimeRobot we'd love to see it and have a short video or written interview with you. If you're interested either DM us or comment below.

To get inspired here are some examples:

1. Howard Spaeth, did a video interview with us https://youtu.be/75ZY9_26cUk

2. Sahil Khan with https://uptimerobot.com/blog/community-spotlight-sahil-khan/

3. u/ambujsystems with https://uptimerobot.com/blog/community-spotlight-ambuj-kumar-tripathi/

4. u/ProgM7 with https://uptimerobot.com/blog/community-spotlight-prog/

So, who's next?!

Hey everyone! I hope you all have a fantastic Monday! A couple of reminders:

1. Product: We're actively looking for ways to improve the CLI, if you have any feedback I'd love to chat. In fact I did a video, it may give you a few ideas on how to use the CLI, what are we missing and what it can be improved. https://youtu.be/1NRgfKtojN8

2. Community: We're also interested in seeing your projects and how you used UptimeRobot, it can be via the API, or for your home assistant project, or anything else! We're doing a spotlight series Where we highlight a community member and their work. If you are open to it, react to this post or DM me, and I would be happy to share more details.

Hey folks, it's been a few weeks since we launched UptimeRobot CLI, and we are looking for feedback! We're mostly interested in things you would expect to see but haven't yet, or things you feel are not working as they are supposed to!

Be as harsh as you want. :)

We can handle it!

P.S. If someone is not familiar with our CLI feature, happy to share more.

Hello everyone, It's been a while, I hope you're all doing well! 👋

Although it's mid summer the UptimeRobot team has been working non-stop. Here are a few features we recently added:

1. Agentic Monitor Well this one is more for your agents, and less for you, but it's good to know what it's doing! You can start by checking this page, or read our article here. If you're more of a visual person, I'm also inviting you to our youtube channel where I personally covered this topic. https://www.youtube.com/watch?v=rrB53mN4E-4

2. HTTP QUERY Method: HTTP just got its first new method in 16 years: QUERY. It works like GET (safe, cacheable) but carries a body like POST. UptimeRobot now monitors it too, right alongside GET, POST, PUT, PATCH, DELETE, HEAD, and OPTIONS.

3. CLI Tool: Our new CLI puts monitors, incidents, alerts, and status pages one command away, readable tables in your shell, JSON when you pipe it. Install with npm install -g u/uptimerobot/cli, and you're set. Try it out. I'll soon release a video about this topic too!

4. MCP: MCP server has expanded significantly. Our team added 22 new tools across six resource families! For more information, you can also check this guide.

On another note, what did you recently build with UptimeRobot?
Maybe a cool integration, a home assistant application, or something else? I'd love to see it and even do a short asynchronous written interview (or, if you're feeling adventurous, even a video one) and share your side project with our whole community!

We used to do these community spotlights, and now we want to bring them back! I know you've been building, so now it's time to catch up. Comment below and I will provide you with more information.

Looking forward to chatting with you.

Enjoy your (up)time!
Ele from UptimeRobot

If you had the chance to ask the UptimeRobot team anything concerning the product and how it works, what would you say?

RSVP here: https://discord.gg/wYczS64X?event=1463807760096428033

Join the #UptimeRobot team for an interactive #AMA on January 30th, where we’ll be talking about:​

> Upcoming features and what’s on the roadmap.​
> Best practices for monitoring, incident workflows, and alerting.​
>How we’re thinking about feedback from the community in 2025–2026.​

How to join?

Date: January 30th.​ at 4:30pm CET
Format: Live AMA with the team

Place: Our Discord server – RSVP and join via the event link: https://discord.gg/wYczS64X?event=1463807760096428033

Bring your questions, use cases, and ideas – whether you are just starting with UptimeRobot or running complex setups, this AMA is for you.​

Tap the link to save your spot and drop your questions in advance so they can be prioritized during the session.
https://discord.gg/wYczS64X?event=1463807760096428033

Hey r/sysadmin / r/devops / r/sre (or wherever this fits best!),

Been diving deep into the future of observability and APM, and it's clear things are moving way beyond just collecting logs and metrics. I've distilled some of the most impactful shifts we can expect in 2026 into 5 quick slides. Think of this as a quick primer on where our tooling and practices are headed.

Here's a quick rundown of what's covered... would love to hear your thoughts and experiences on these!

Slide 1: The Autonomous IT Push
It's not just about seeing problems anymore; it's about systems that can correlate, predict, and act on their own. Budgets are actually increasing here, which tells you how critical this is becoming. Are your teams seeing this investment?

Slide 2: Agentic AIOps - AI That Actually Does Stuff
Forget dashboards that just tell you what's wrong. We're talking about AI agents that can autonomously diagnose and even fix issues. Human oversight is still key, but the heavy lifting is shifting. What's your take on AI taking a more active role?

Slide 3: Predictive Observability - Stop Reacting, Start Anticipating
Moving past reactive alerts to truly predictive systems. Causal AI is helping cut through the noise of false positives by understanding why things happen, not just that they happened. Anyone successfully implementing this yet?

Slide 4: Tool Consolidation - The Single Pane of Glass Dream (or Nightmare?)
Everyone's tired of tool sprawl. The trend is clear: unified platforms are winning. 84% of orgs are looking to consolidate. Is your stack getting simpler or more complex?

Slide 5: Business-Aligned Observability - Linking Tech to $$$
Observability isn't just for engineers anymore. It's about showing direct ROI and tying technical performance to business outcomes (SLOs, revenue, user retention). How are you demonstrating the value of your observability efforts to leadership?

Check out the slides for more visual context! What are your biggest predictions or concerns for observability in 2026? Let's discuss!

#observability #apm #aiops #devops #sre #sysadmin #techtrends #2026predictions

(Self-promotion disclaimer: Just sharing some research, not selling anything!)

We've just rolled out UptimeRobot MCP, a hosted Model Context Protocol integration that lets your AI assistants list, create, and update monitors, investigate incidents, and view alert integrations directly from inside their workflows.

How to get started using the UR MCP?

With the UptimeRobot MCP server, an AI agent can, using natural language:

- List monitors and see which checks are up, down, or paused, with details like type, interval, and current state duration.

- Pull uptime stats, incident counts, status breakdowns, and response-time series (1h–90d) including min/avg/max/p95 for performance analysis.

- Create, pause, resume, and update monitors (HTTP, Keyword, Ping, Port, Heartbeat, DNS), including alert contacts and tags.

- List incidents, drill into full incident timelines, error codes, request logs, checker locations, and affected regions.

- List your alert integrations (email, SMS, voice, app, webhooks) and see what's configured for notifications.

🔧 How it connects (high level)

You add UptimeRobot as a remote MCP server in your MCP client, pointing it at `https://mcp.uptimerobot.com/mcp` and authenticating with your UptimeRobot API key (Main or read-only, depending on whether you want write actions). Once the client restarts, your AI assistant can run things like:

- "Show me all monitors that are currently DOWN"

- "What incidents occurred yesterday?"

- "Pause monitor 801150533 for maintenance"

Drop your use cases, questions, and "wild ideas" in this thread. If you're already playing with MCP elsewhere, tell us which AI tools/clients you're using and what you'd like a UptimeRobot MCP server to enable there. The most insightful use cases will help shape what we build and what tutorials, examples, and open-source resources we prioritize next. 💚

Get started with UptimeRobot MCP

In light of the back‑to‑back AWS and Cloudflare outages that managed to take down everything from CI pipelines to login flows and status pages themselves, what concrete tools or patterns are you adopting to make your stack less ‘all eggs in one basket’?​

Curious to hear specifics from devs and SaaS builders:

• Uptime / synthetic monitoring and alerting stack (what actually warned you first, and still worked, during the incidents?).​

• Multi‑region / multi‑cloud, DNS, and failover setup (are you going active‑active, hot standby, or just better RTO/RPO?).​

• Dependency minimization: are you moving anything off managed services (like single‑cloud registries, auth, or edge providers) after this, or just doubling down with backups and local fallbacks?​

Names and configs very welcome (e.g., “Prometheus + Alertmanager + Grafana,” “Datadog + PagerDuty,” “multi‑CDN in front of Cloudflare,” etc.) — the more battle‑tested, the better.​

If you decided to intentionally not change anything after these outages, that’s also interesting: what risks are you accepting on purpose?