At UptimeRobot, keeping your monitoring reliable and your data secure is a top priority. As part of our ongoing efforts to support modern security standards, we will be updating our minimum supported TLS version for certain connections.
Starting September 1st, 2025, UptimeRobot will no longer support TLS 1.0 and TLS 1.1 for API and cron monitor connections. All such connections will need to use TLS 1.2 or higher.
Why we’re making this change:
TLS (Transport Layer Security) is the encryption protocol that protects the data exchanged between your systems and UptimeRobot. Older TLS versions (1.0 and 1.1) are now considered insecure by industry standards and have been deprecated by major browsers, APIs, and cloud providers.
By requiring TLS 1.2 or higher, we:
- Align with modern security best practices
- Reduce the risk of vulnerabilities and potential exploits
- Ensure compatibility with the majority of up-to-date systems and libraries
This is part of a broader set of improvements to keep UptimeRobot safe, stable, and reliable for all users.
Who this affects:
This change only impacts:
- Users connecting to the UptimeRobot API using TLS 1.0 or 1.1
- Users running cron monitors that connect over TLS 1.0 or 1.1
If you are already using TLS 1.2 or higher, no action is needed.
How to prepare?
Before September 1st, check your client libraries, server configurations, or scripts to ensure they use TLS 1.2 or higher when connecting to UptimeRobot.
Here are some quick checks and tips:
- Update your HTTP/HTTPS client libraries to the latest version
- Confirm your programming language runtime supports TLS 1.2+ (most modern versions do)
- If you use a custom server or proxy, ensure its TLS settings allow TLS 1.2+ and disable older versions
Need help?
If you’re not sure whether this affects you, our support team can help you verify your current TLS version and guide you through any necessary updates.
We appreciate your understanding as we continue improving the security and reliability of UptimeRobot.
