Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
Uptime Kuma 2.3 is now available as the latest stable release of the self-hosted monitoring tool. A standout addition in this version is the new OracleDB monitor, which expands its database monitoring capabilities. The update also enhances WebSocket functionality, including added support for authentication.
On the status page front, version 2.3 introduces collapsible groups, making it easier to manage larger and more complex status pages. At the same time, the previously added sorting feature has been removed due to performance concerns, so users who relied on it should take note before upgrading.
There’s also an important update for Raspberry Pi users. A new option, UPTIME_KUMA_SQLITE_SINGLE_CONNECTION, has been added and may need to be set to true to prevent SQLite locking issues—particularly on Raspberry Pi and similar low-powered devices. Most other users won’t need to worry about this setting.
Notification capabilities have been expanded as well. This release adds support for Telnyx messaging, VK notifications, MAX Messenger, and custom message templates for the Evolution provider. Additionally, the Home Assistant notification documentation has been updated to reflect its 2024 terminology change from “Services” to “Actions.”
In terms of bug fixes, the update resolves issues with missing time buckets in uptime calculations, domain expiry checks not refreshing correctly, and SSL handling in the temporary setup database server. It also fixes a Prometheus-related issue where a single monitor could generate duplicate metric series when tags were applied.
Further fixes address gaps in monitor graphs for very fast TCP pings, Stackfield notification handling, database storage for applyExisting, and improved error handling during monitor creation.
For the full list of changes, refer to the official changelog. And if you’re new to Uptime Kuma, consider trying it out—there are plenty of guides available to help you get started quickly with Docker.
For more details, see the changelog.
