Uptime Kuma 2.1 Adds Globalping Support, Expanded Notification Integrations

After months of development, Uptime Kuma, the widely used self-hosted uptime monitoring tool with more than 80,000 stars on GitHub, has officially released version 2.1.

This release introduces two major notification integrations: Jira Service Management and Google Sheets, giving teams additional ways to receive alerts — especially useful for those relying on ticketing workflows or spreadsheet-based tracking.

Notification handling is also more flexible. Discord and ntfy messages now support templates, formatting presets, and richer alert details, while Slack alerts can include monitor group names for clearer context.

Another highlight is Globalping integration, which allows checks to run from distributed probes around the world instead of only from your own server. Automation support improves as well, with HaloPSA notifications now exposing monitor_id and heartbeat_id fields.

New Domain Expiry Monitoring

Version 2.1 also introduces a dedicated Domain Expiry monitor that lets you:

• Track domain expiration dates automatically
• Receive alerts before domains expire
• Reduce noisy expiry logs and improve validation behavior
• Benefit from more reliable RDAP lookups, including better handling of multi-level public suffixes and static RDAP DNS data

Fixes and Improvements

This update resolves several monitoring issues and brings broader reliability enhancements. Certificate expiry checks now respect proper settings, while parsing improvements were made for MongoDB JSON data, RSS time zones, RADIUS client handling, and monitor selection logic. Nested group expand/collapse behavior has also been refined across dashboards.

Localization continues to expand, with Bavarian German added and numerous translation updates contributed via Weblate.

As with previous releases, Uptime Kuma 2.1 also includes dependency updates, workflow refinements, maintenance changes, and minor security improvements.

To view them all in detail, check the changelog.

If you haven’t tried it yet, now’s a good time — especially if you run self-hosted infrastructure. I’ve also published a step-by-step guide showing how to deploy Uptime Kuma quickly using Docker.