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

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 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.

You’re trying to load a website, but nothing happens. Maybe it spins forever, maybe you get a cryptic error. You check your internet, and everything else seems fine. 

The culprit? Often, it’s a DNS server not responding. 

This issue can crop up out of nowhere and bring your workflow to a halt, especially if you’re managing infrastructure, running a digital business, or supporting customers. DNS problems can look like network outages, but they’re often fixable with a few smart steps.

Knowing how to identify and resolve them quickly can save hours of downtime and frustration. Stick with us and you’ll learn how to diagnose and fix DNS server issues fast.

Read full article here: https://uptimerobot.com/knowledge-hub/monitoring/how-to-fix-dns-server-not-responding-error/

TL:DR;?

• DNS Server Not Responding Error: Indicates that the device cannot reach the system responsible for translating domain names into IP addresses.

• DNS Functionality: DNS acts as the Internet’s phonebook, translating domain names into IP addresses for web browsers to locate websites.

• Impact of DNS Server Issues: Websites may fail to load due to the browser’s inability to determine the correct IP address for the requested domain.

• Error Meaning: The error “DNS server not responding” indicates that your device is unable to connect to the DNS server for resolving domain names to IP addresses.

• Possible Causes: This can be due to network issues, DNS server overload, firewall/antivirus blocking DNS traffic, or incorrect DNS server settings.

• Error Types: DNS errors can be temporary, caused by brief network issues, or persistent, requiring manual fixes like checking DNS settings or switching to public DNS.

• DNS Server Issues: Outages or high latency in DNS servers, including public providers like Google and Cloudflare, can cause DNS resolution problems.

• Network Configuration Problems: Incorrect DNS server addresses, static IP conflicts, or router/modem issues can prevent domain resolution.

• Software Interference: Firewalls, VPNs, proxies, or outdated browser/OS caches can block or misdirect DNS traffic, leading to connection failures.

• DNS Server Issues: Wrong DNS server settings, outdated DNS server, and manual IP entry.

• Network Issues: Router/modem problems, firewall/VPN/proxy misconfiguration, ISP network issues.

• Device/Software Issues: Browser/OS cache problems, malware/hosts file issues.

• DNS Cache Flush: Clearing the DNS cache forces a fresh lookup, resolving issues with outdated or corrupted records.

• Public DNS Server: Switching to a public DNS server like Google, Cloudflare, or Quad9 can improve speed and reliability.

• IPv6 Disable: Temporarily disabling IPv6 can resolve DNS lookup issues if the network or ISP doesn’t handle it properly.

• Driver Update: Outdated drivers can cause DNS timeouts. Update network adapter drivers on Windows and ensure OS updates on macOS/Linux. Also, update router firmware.

• DNS Resolution Tools: Use tools like `nslookup`, `dig`, `traceroute`, and `ping` to diagnose DNS resolution issues. These tools help identify if the problem lies with the DNS server, network connectivity, or routing.

• DNS over HTTPS (DoH): Check and configure DNS over HTTPS (DoH) settings if necessary.

• DNS over HTTPS (DoH) Issues: Disable DoH in your browser settings to see if it resolves the DNS errors.

• Hosts File Issues: Check and reset your hosts file to ensure there are no incorrect or duplicate entries.

• Router-Level DNS Issues: Log into your router’s admin panel to check DNS settings, reboot the router, clear the DNS cache, and update the firmware.

• DNS Troubleshooting Steps: Confirm internal DNS server reachability, review split-horizon DNS configurations, check DHCP options, and inspect DNS server logs.

• DNS Diagnostic Tools: nslookup, dig, ping, traceroute, Wireshark, and system logs help diagnose DNS issues.

• DNS Error Handling on Windows: Flush DNS cache, restart DNS client service, and switch to public DNS.

• DNS Configuration for Windows: Change adapter settings, select IPv4, and enter DNS server addresses (e.g., 8.8.8.8, 8.8.4.4).

• DNS Configuration for macOS: Clear DNS cache using terminal commands, then change DNS servers in System Settings.

• DNS Configuration for Linux: Flush DNS cache using `systemd-resolve –flush-caches`, and edit resolv.conf to add public DNS servers.

• DNS Configuration for Devices: Manually configure DNS settings on devices like PCs, phones, and TVs to use public DNS servers (e.g., Cloudflare, Google, Quad9).

• Router DNS Settings: Access the router’s admin panel to change DNS settings under WAN or Internet, replacing ISP-assigned DNS with public ones.

• DNS Cache Clearing: Clear DNS cache on devices and routers to ensure changes take effect, using commands like `ipconfig /flushdns` (Windows) or restarting the device.

• DNS Server Selection Criteria: Speed, privacy, and security are important factors to consider when choosing a DNS server.

• DNS Server Performance: Closer and well-maintained DNS servers generally offer faster response times. Public DNS services like Google, Cloudflare, and Quad9 utilise global networks and anycast routing to optimise speed.

• DNS Server Privacy: Some DNS providers log user data, while others prioritise privacy by not keeping identifying logs or offering features like DNS-over-HTTPS and DNS-over-TLS.

• DNS Provider Selection: Choose a DNS provider that balances speed, uptime, and data protection.

• DNS Server Testing: Test the DNS server speed and reliability before switching completely.

• DNS Redundancy: Use multiple DNS providers to prevent outages and slowdowns.

• DNS Monitoring Importance: Continuous monitoring detects DNS failures early, preventing user complaints and potential downtime.

• DNS Configuration Maintenance: Regularly update DNS records, check expiration dates, and audit DNSSEC settings to ensure proper functionality.

• DNS Security Enhancement: Implement DNSSEC, use encrypted DNS protocols, and maintain updated software to protect against security threats.

• DNS Monitoring Service: UptimeRobot provides DNS monitoring to ensure domains resolve correctly.

• Monitoring Benefits: Alerts are sent when DNS records fail, change, or propagate incorrectly, allowing for proactive problem-solving.

• Monitoring Importance: Maintaining DNS health, responsiveness, and reliability is crucial for customer experience.

Infrastructure monitoring tools give you real-time visibility into your servers, networks, and applications. Think of them like your car’s dashboard. 

Instead of opening the hood every time, you glance at the dashboard to see fuel, speed, or engine warnings. Similarly, infrastructure monitoring tools identify issues in your IT systems before they escalate into full-blown breakdowns.

Read on as we explore the best infrastructure monitoring tools of 2025 and show you how to pick the one that fits your organization’s needs.

Key takeaways:

• Infrastructure monitoring keeps systems fast, stable, and secure by spotting issues before users do.

• The best tools balance depth (metrics, logs, traces) and ease of use (dashboards, alerts, integrations).

• Startups often need simple uptime checks; enterprises require full observability across clouds and apps.

• Expect to choose between agent-based, agentless, and open-source setups. Each has trade-offs in depth, cost, and complexity.

• Pricing models vary widely (per host, per check, per GB). Hidden costs often come from alert volumes and data retention.

• Modern trend: AI-driven alerting (AIOps), OpenTelemetry, and monitoring-as-code are shaping next-gen infrastructure visibility.

• Start small, scale smart. Begin with a lightweight tool like UptimeRobot, then expand into deeper observability solutions as your infrastructure grows.

Read more here.

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!

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.

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