Uptime Kuma | 2.3.2

Uptime Kuma 2.3.2 released on 03-05-2026


Uptime Kuma 2.3.2 is out now. Administrators using the bundled SQLite will see the default database access mode revert to a single connection, restoring the prior stability and addressing concurrency issues.

Visit the Uptime Kuma GitHub release notes for full details and the linked issue (#7346) if you need background on the fix.

What’s in this release

  • Revert back to a single SQLite connection by default (fix for issue #7346).
  • Fixes a database-related regression that affected stability and concurrency when multiple SQLite connections were used.
  • No other user-facing changes are included; the release is a targeted bugfix.

Upgrade notes

  • No breaking changes or migrations are documented — upgrade as you normally would to apply the fix.
  • If you run non-standard SQLite setups, test the update in a staging environment before rolling it out to production.

If you upgrade to 2.3.2, share how it behaves for you — report regressions or confirmations in the issue tracker or community channels so maintainers can follow up.

Related posts

Uptime Kuma | 2.3.2

Uptime Kuma 2 3 2, reverts to single SQLite connection to fix stability issues, minimal impact, back up your database and verify monitors after upgrade

Uptime Kuma | 2.3.2

Uptime Kuma 2:3:2: Revert to single SQLite connection, bugfix for DB regression and stability issues, admins using bundled SQLite should upgrade

Uptime Kuma | 2.3.0

Uptime Kuma 2 3 0: status page sort reverted, SQLite single connection for Raspberry Pi, WebSocket auth, new providers, bug fixes and UX updates