Quick links
At UptimeRobot, we’re always evolving to serve you better—while understanding that change can sometimes be inconvenient.
We’re excited to announce a major infrastructure upgrade designed to boost performance, scalability, and reliability.
This upgrade will help us deliver faster, more reliable service as we grow, and we hope you’ll see the benefits soon.
Here’s what’s changing:
1. Migration to the cloud
We’re moving from dedicated servers to a “multiple cloud provider” setup.
This decision wasn’t taken lightly. While some may note concerns about loss of control, our previous provider just didn’t meet our super-high expectations of reliability and stability, plus it was a limiting factor in other aspects too.
By distributing our infrastructure across trusted cloud providers, we’re ensuring smoother, faster operations and greater resiliency. We know stability is key for you, and this change sets the foundation for it.
With this move, we’ll also have a greater flexibility to scale, and be able to offer more advanced features like multi-location monitoring more easily.
2. Improved IP resolution cache
We’ve optimized our DNS IP resolution process, so it now follows DNS TTL more closely. This means faster, more accurate monitoring and real-time responsiveness—improving the overall accuracy of the service.
3. We recommend to ensure IPv6 is working on your end
The Internet is steadily moving toward IPv6, and so are we! Our new architecture will work with IPv4 for now but might start to prioritize IPv6 in the near future.
We understand IPv6 might not be a top priority for everyone right now. Adoption has been quite slow, and many setups still prioritize IPv4. However, we’re positioning ourselves for the future, which is why we recommend checking that IPv6 works on your end!
If your provider doesn’t support IPv6 yet, don’t worry—you still have time, and IPv4 will continue to work for now.
4. New IP Addresses (We know, it’s a pain!)
Yes, we’re introducing new IP addresses as part of this upgrade ☹️
We get it—updating firewall rules can be a hassle. But rest assured, these IPs won’t be changing again anytime soon. Please ensure these new IPs are added to your allowlist to keep your monitoring running smoothly.
Action Required: Please update your firewall rules accordingly and ensure the IP addresses are added to your allowlist.
If you run into any issues related to these changes, please don’t be afraid to reach out to our support team.
What’s in for you?
We’re laying the groundwork for several new features we’ve been developing based on your valuable feedback. The updated infrastructure will enable multi-location monitoring, and we’re also excited about response time monitoring, both of which are coming soon 👀
These improvements will bring tangible benefits that improve the quality and scope of the services you rely on. We know there’s more to discuss, and we’d love to hear your thoughts in the comments. Let us know how we can continue to improve for you!
Frequently asked questions
Do I need to take any action?
Yes, please make sure you update your firewall allowlist with the new IP addresses. Also it is highly recommended to make sure IPv6 works on your end.
Will my running monitors be affected?
Your existing monitors shouldn’t be impacted. If you experience any issues, our support team is here to help.
How do I find the new IP addresses?
You can find the updated list of IP addresses on our website or by contacting our support team.
9 replies on “Introducing UptimeRobot’s Core Monitoring Infrastructure Upgrade: What’s Changing And What it Means For You”
We use some ipv4 only locations and if you plan on stopping ipv4 support – please give an estimate. We would move to another uptime service provider before this happens.
However, some IPs (see list below) have worse scores on AbuseIPDB and traffic from these IPs may be restricted until their scores improve.
this is a problem for my hoster, he doesn’t want to allow me !!
3.212.128.62
52.22.236.30
54.167.223.174
3.12.251.153
52.15.147.27
18.116.205.62
3.20.63.178
34.198.201.66
35.84.118.171
44.227.38.253
35.166.228.98
216.144.248.27
2600:1f18:179:f900:4696:7729:7bb3:f52f
2600:1f18:179:f900:4b7d:d1cc:2d10:211
2600:1f18:179:f900:5c68:91b6:5d75:5d7
2600:1f18:179:f900:71:af9a:ade7:d772
2600:1f14:203:e40d:c86b:1e24:fab4:7d03
2600:1f14:203:e48b:5538:77b2:6e13:4f8d
2600:1f14:203:e46c:6c8c:bcb:5245:7a0c
I have no idea what firewall and ip address you mean. I just connect with uptime robot using this email address. I have it checking multiple websites.
If it works, it works 🙂 But in case you need any assistance we’ll be happy to help you on our live chat or via email, please contact our support if needed.
I’m not sure what you did to “optimized DNS IP resolution process”, but from one week (15.10) we have tens and even hundreds alerts on daily bases with Root cause “DNS Resolving problem”.
Hi Georgi, please contact our support if you haven’t yet and we’ll be happy to take a look at it and let you know what might be the issue, thank you.
Are we whitelisting all the IPs, Also share contact of a person who can guide us through the IP Whitelisting.
Yes we recommend adding all of the IPs in our files, please contact your service provider or service administrator.
ok