Uptime Kuma has quietly become the default self-hosted monitor. The project now has about 90,000 GitHub stars, supports 90+ notification services and checks your sites as often as every 20 seconds. So choosing among the best Uptime Kuma hosting providers matters more than most people think.
Here is the catch nobody talks about: your monitor is only useful if it stays up when your sites go down. If you host it on the same server as your websites, one outage silences both the site and the alarm. If you are new to the idea, our guide on what uptime is and how to monitor website availability explains why that matters.
This guide ranks the 10 best Uptime Kuma hosting providers by real price, what is actually managed, Uptime Kuma 2.x readiness and setup time. You will also find a sizing table, a true cost breakdown and the mistakes that break most self-hosted monitors.
Quick Summary: Which Uptime Kuma Host Should You Pick?
Short on time? Use this table to pick the best Uptime Kuma hosting provider for your situation:
| If you want to… | Use this | Best for | Setup time |
|---|---|---|---|
| Run Uptime Kuma free on your own cheap server with a control panel | xCloud (free plan) | Agencies and developers with several sites | About 10 minutes |
| Pay the least for a managed instance | PikaPods | Solo founders, side projects | About 2 minutes |
| Hand off updates and backups completely | Elestio | Teams with no time for server work | About 5 minutes |
| Get automatic app updates on your own server | Cloudron | Self-hosters running many apps | About 30 minutes |
| Get a big VPS with a one-click template | Hostinger VPS | Beginners on a budget | About 15 minutes |
| Deploy from a template with usage-based billing | Railway | Developers who live in PaaS tools | About 5 minutes |
- Best overall value: xCloud’s free plan on a $4 to $6 VPS from any cloud provider.
- Cheapest managed option: PikaPods from $3.30 a month.
- Most hands-off: Elestio, which handles updates, backups and SSL for you.
Why Uptime Kuma Needs the Right Hosting
Uptime Kuma is light. Still, it has a few hard requirements. If you get one wrong, you either lose data or get alerts you cannot trust.
| Requirement | Why it matters |
|---|---|
| Local disk or a Docker volume for /app/data | The official README warns that network file systems such as NFS are not supported. SQLite needs proper file locking. |
| A separate failure domain | Your monitor must survive when your sites fail. Use a different server and ideally a different provider or region. |
| WebSocket support on the reverse proxy | The dashboard runs over WebSockets. Your proxy must pass the Upgrade and Connection headers. |
| Its own domain or subdomain | Uptime Kuma cannot run from a subdirectory such as /status. |
| Exactly one instance | It is a single-node app. Running two replicas against one database causes conflicts. |
| Backups of /app/data | Version 2 removed JSON backup and restore. Copying the data folder (or dumping MariaDB) is now the only backup method. |
The reverse proxy wiki covers the WebSocket and subdomain rules in detail.
What Changed in Uptime Kuma 2.x (and Why Your Host Must Keep Up)
Uptime Kuma 2.0 shipped on October 20, 2025, as Linuxiac reported. The current stable release is 2.5.7, published on October 23, 2026. Here is what changed for hosting:
- MariaDB support joined the default SQLite database. MariaDB suits setups with hundreds of monitors.
- Alpine images were dropped. Instead, version 2 offers standard, slim and rootless Docker images under the
louislam/uptime-kuma:2tag. - Node.js 20.4 or newer is required for installs without Docker.
- The upgrade from 1.x rewrites heartbeat data. The v1 to v2 migration guide shows about 7 minutes for 20 monitors with 90 days of history. On slow disks, it takes much longer.
That last point matters. Several one-click templates still ship version 1.23. So check the version before you deploy.
The 4 Types of Uptime Kuma Hosting
You are really choosing between four models. Each one trades money for time differently:
| Type | Examples | You manage | Typical monthly cost |
|---|---|---|---|
| Managed app hosting | PikaPods, Elestio | Almost nothing | $3.30 to $11+ |
| Control panel on your own server | xCloud, Cloudron, Coolify | The server bill, some updates | $0 panel + $4 to $6 VPS |
| VPS with a one-click template | Hostinger, Akamai (Linode), Vultr, DigitalOcean | OS, Docker, updates, backups | $4 to $12 |
| Platform as a service (PaaS) | Railway | Volumes and config | About $5 to $8, usage based |
How We Ranked the Best Uptime Kuma Hosting Providers
We scored each provider on six criteria:
- Real monthly cost, including renewal prices and the server you still need to rent.
- What is actually managed: updates, backups, SSL and support.
- Uptime Kuma 2.x readiness: which version the template ships today.
- Setup time from sign-up to the first monitor.
- Failure isolation: how easily you can keep the monitor away from the sites it watches.
- Exit path: how easily you can take your /app/data folder elsewhere.
We checked every price and template on official pages in October 2026. Prices exclude VAT and can change. Therefore, confirm them before you buy.
Disclosure: xCloud is our own product. We list its cons the same way we list everyone else’s. That way, you can judge the ranking yourself.
Master Comparison Table
| Rank | Provider | Type | Starting price | Setup time | Best for |
|---|---|---|---|---|---|
| 🥇 1 | xCloud | Panel on your server or managed VPS | $0 plan + your VPS; managed VPS $24.99/mo | ~10 min | Agencies managing many sites |
| 🥈 2 | PikaPods | Managed app hosting | $3.30/mo | ~2 min | Cheapest managed instance |
| 🥉 3 | Elestio | Fully managed | $11/mo | ~5 min | Zero maintenance |
| 4 | Cloudron | App platform on your server | Free for 2 apps + your VPS | ~30 min | Auto-updated self-hosting |
| 5 | Hostinger VPS | VPS + template | $6.49/mo intro, renews $11.99 | ~15 min | Big VPS for the price |
| 6 | Akamai (Linode) | VPS + Quick Deploy App | $5/mo | ~10 min | Simple cloud VPS |
| 7 | Vultr | VPS + Marketplace app | $5/mo (1 GB) | ~10 min | Many regions |
| 8 | Railway | PaaS template | $5/mo Hobby (includes $5 usage) | ~5 min | PaaS fans |
| 9 | Coolify | Self-hosted PaaS | Free self-hosted; Cloud $5/mo | ~30 min | Docker-savvy teams |
| 10 | DigitalOcean | VPS + Docker | $4/mo (512 MiB) | ~15 min | Teams already on DO |
🥇 1. xCloud: Best Overall Uptime Kuma Hosting for Agencies and Developers
xCloud’s Uptime Kuma hosting deploys the app in one click on a server you connect or one xCloud provisions. xCloud sets up the container, a persistent data volume at /app/data and HTTPS on your domain. In addition, you manage it from the same panel you use for WordPress, Laravel or Node.js sites.
The pricing, however, is the interesting part. The free plan covers 1 server and 10 sites with your own VPS. As a result, a $4 to $6 server from DigitalOcean, Vultr, Akamai or Hetzner is your only bill. If you prefer xCloud to provision the server, managed Cloud VPS plans start at $24.99 a month for 6 GB of RAM and 4 vCPUs.
Key Features:
- One-click deploy with free SSL and a custom domain for the dashboard and status pages.
- HTTP, TCP, DNS, ping and WebSocket monitors, plus certificate expiry alerts.
- Persistent volume that keeps your database, history and status pages across restarts.
- Server backups, snapshots and security updates at the server level.
- Bring any server: DigitalOcean, Vultr, Akamai (Linode), AWS, Hetzner or bare metal.
- Room for other apps on the same panel, from monitoring stacks to production sites.
How to Deploy Uptime Kuma on xCloud:
- Create a free xCloud account and connect a small VPS (keep it separate from your production servers).
- Click New Site, choose your server, open One Click Apps and select Uptime Kuma.
- Add a site title, then choose Go Live with your domain or Demo Site for a temporary subdomain.
- Keep the default port and database settings, then click Next.
- Open the site, create your admin account and turn on 2FA.
👉 Follow the full step-by-step guide to deploy Uptime Kuma with xCloud.
| Pros | Cons |
|---|---|
| ✅ Free plan on your own server | ❌ App upgrades are manual: back up, change the tag, recreate |
| ✅ HTTPS, domain and volume set up for you | ❌ Pins a tested release (2.5.0 at the time of writing) |
| ✅ One panel for monitoring and your other sites | ❌ Docker container monitoring is not available |
| ✅ Works with any major cloud provider | ❌ Managed Cloud VPS ($24.99) is more than Kuma alone needs |
Best for: agencies and developers who want Uptime Kuma next to their other sites in one panel, on a cheap separate server.
🥈 2. PikaPods: Cheapest Managed Uptime Kuma Hosting
PikaPods runs open-source apps as small managed “pods”. Its Uptime Kuma pod starts at $3.30 a month and uses a MariaDB backend. New accounts also get a $5 welcome credit, which covers more than a month.
In addition, PikaPods handles updates and stores daily encrypted backups in your own S3-compatible storage. That design is smart because your backups live outside PikaPods.
Key Features:
- Managed app hosting with updates handled for you.
- MariaDB backend by default.
- Daily encrypted backups to S3-compatible storage you own.
- Custom domains for your instance.
- Pay-as-you-go pricing with adjustable resources.
- $5 welcome credit for new accounts.
How to Deploy: Sign up, pick Uptime Kuma from the app list, choose resources and a region, then add your domain.
| Pros | Cons |
|---|---|
| ✅ Lowest managed price we found | ❌ Less control over the container and image tag |
| ✅ Backups go to storage you own | ❌ You need your own S3 bucket for backups |
| ✅ Live in about 2 minutes | ❌ Small pods may need upgrading as monitors grow |
Best for: solo founders and side projects that want a managed monitor for the price of a coffee.
🥉 3. Elestio: Best Fully Managed Uptime Kuma Hosting
Elestio is the most hands-off option on this list. Its managed Uptime Kuma starts at $11 a month, billed per hour with no long-term commitment. Elestio handles automated backups, SSL, updates and service monitoring.
You also choose the underlying cloud: Hetzner, DigitalOcean, Vultr, Akamai, AWS Lightsail, OVH, Scaleway, Azure and others. As a result, it is easy to keep the monitor on a different provider from your sites.
Key Features:
- Automatic updates for Uptime Kuma.
- Automated backups with restore options.
- Auto SSL and custom domains.
- Choice of cloud provider and region.
- Hourly billing with no lock-in.
- Bring your own VM if you prefer your own cloud account.
How to Deploy: Create an account, pick Uptime Kuma, choose a provider, region and size, then deploy.
| Pros | Cons |
|---|---|
| ✅ Truly managed, including updates | ❌ Over 3 times the price of PikaPods |
| ✅ Pick a different cloud from your sites | ❌ The trial requires a card |
| ✅ Hourly billing | ❌ Pricier than running your own small VPS |
Best for: teams that never want to SSH into a monitoring server.
4. Cloudron: Best for Auto-Updated Self-Hosting
Cloudron is an app platform you install on your own server. Its Uptime Kuma package already runs 2.5.7 (the latest release) and needs at least 256 MB of RAM. On top of that, Cloudron handles app updates and backups for you.
The free plan allows 2 apps, which is enough for Uptime Kuma plus one more tool. After that, paid plans unlock unlimited apps.
Key Features:
- Automatic app updates. For example, Cloudron packaged 2.5.7 two days after its release.
- Built-in backups for every app.
- One dashboard for every installed app.
- Free plan for up to 2 apps.
- Runs on any VPS you rent.
- Let’s Encrypt SSL set up automatically.
How to Deploy: Rent a VPS, run the Cloudron installer, then install Uptime Kuma from the app store.
| Pros | Cons |
|---|---|
| ✅ Ships the current Uptime Kuma release | ❌ Cloudron wants a dedicated server |
| ✅ Updates and backups handled | ❌ Free plan stops at 2 apps |
| ✅ You keep full ownership | ❌ Longer first setup |
Best for: self-hosters who want app-store convenience on their own hardware.
5. Hostinger VPS: Best Budget VPS With a One-Click Template
Hostinger’s Uptime Kuma VPS template installs Uptime Kuma with Docker on its KVM plans. The entry KVM 1 plan costs $6.49 a month at the intro rate and renews at $11.99. You get 1 vCPU, 4 GB of RAM and 50 GB of NVMe storage, far more than Uptime Kuma needs.
Weekly backups are free. Plus, a 30-day money-back guarantee lowers the risk. However, this is a self-managed VPS. That means OS updates and Uptime Kuma upgrades are your job.
Key Features:
- One-click Docker template for Uptime Kuma.
- 4 GB RAM on the cheapest plan.
- Free weekly backups.
- 30-day money-back guarantee.
- Full root access for custom setups.
- Several data center locations.
How to Deploy: Buy a KVM plan, pick the Uptime Kuma template during setup, then point a subdomain at the server.
| Pros | Cons |
|---|---|
| ✅ Lots of RAM for the price | ❌ Renewal nearly doubles the price |
| ✅ Free weekly backups | ❌ Intro price requires prepaying |
| ✅ Template saves Docker setup | ❌ Self-managed updates |
Best for: beginners who want a roomy VPS and do not mind basic server upkeep.
6. Akamai (Linode): Best Simple Cloud VPS for Uptime Kuma
Akamai Cloud, formerly Linode, lists Uptime Kuma as a Quick Deploy App on Ubuntu 24.04. During setup, the installer configures Let’s Encrypt and an optional custom domain. The cheapest Nanode plan costs $5 a month for 1 CPU and 1 GB of RAM.
Key Features:
- Quick Deploy App with SSL set up during install.
- $5 Nanode with 1 GB RAM and 25 GB storage.
- Pay by the hour for short tests.
- Global regions across North America, Europe and Asia.
- Works with any plan size.
- Optional backups for an extra fee.
| Pros | Cons |
|---|---|
| ✅ Predictable $5 price | ❌ Self-managed after install |
| ✅ SSL configured at deploy | ❌ Template version is not shown |
| ✅ Hourly billing | ❌ Backups cost extra |
Best for: developers who want a plain, reliable VPS with a head start on setup.
7. Vultr: Best for Region Choice
Vultr’s Uptime Kuma Marketplace app deploys a ready instance in a few clicks. Plans with 1 GB of RAM start at $5 a month. Vultr also offers even smaller 0.5 GB plans for lighter setups.
Vultr’s wide region list makes it a strong choice for a second monitor. For example, you can run one Kuma near your users and another on a different continent.
| Pros | Cons |
|---|---|
| ✅ Many regions worldwide | ❌ Self-managed |
| ✅ Cheap small plans | ❌ The docs deploy on pricier Optimized Cloud plans |
| ✅ Marketplace app saves time | ❌ Backups cost extra |
Best for: teams that want monitors in specific regions.
8. Railway: Best PaaS Template
Railway has an official Uptime Kuma guide and a one-click template. The Hobby plan costs $5 a month and includes $5 of usage. Railway estimates about 512 MB of RAM for Kuma. Because of that, most small setups land between $5 and $8 a month.
Two rules matter here. First, mount a volume at /app/data before you create the admin account. Second, run exactly one replica.
| Pros | Cons |
|---|---|
| ✅ Deploys in minutes from a template | ❌ Usage billing makes costs less predictable |
| ✅ Git and CLI workflow | ❌ The guide still pins version 1 (change the tag to 2) |
| ✅ Easy logs and metrics | ❌ Forgetting the volume wipes your data on redeploy |
Best for: developers who already run their apps on Railway.
9. Coolify: Best Self-Hosted PaaS Option
Coolify offers Uptime Kuma as a one-click service with SQLite, MariaDB or MySQL variants. Self-hosted Coolify is free. Alternatively, Coolify Cloud manages the control plane for $5 a month for 2 servers.
Either way, you bring your own servers. That keeps costs low. In return, you own the upkeep.
| Pros | Cons |
|---|---|
| ✅ Free and open source | ❌ Steeper learning curve |
| ✅ Database choice at deploy time | ❌ You maintain servers and Coolify itself |
| ✅ Great for many Docker apps | ❌ Overkill for one monitor |
Best for: Docker-savvy teams running many self-hosted services.
10. DigitalOcean: Best for Teams Already on DigitalOcean
DigitalOcean’s cheapest Droplet costs $4 a month (512 MiB). Meanwhile, the 1 GiB Droplet costs $6. A third-party Marketplace 1-Click for Uptime Kuma exists. However, it still ships version 1.23.13.
So, skip the 1-Click and run the official Docker command on a fresh Droplet instead. Alternatively, connect the Droplet to a control panel that deploys version 2 for you.
| Pros | Cons |
|---|---|
| ✅ Reliable, well-documented platform | ❌ The Marketplace image is outdated |
| ✅ $4 entry price | ❌ 512 MiB is tight for v2 |
| ✅ Easy snapshots | ❌ Backups add 20% to 30% to the bill |
Best for: teams that already run infrastructure on DigitalOcean.
Also Worth Knowing
- Hetzner remains popular for DIY Docker hosting. However, it raised cloud prices on April 1, 2026 and again for new orders on June 15, 2026, per its price adjustment statement. Check current prices and availability first.
- Sliplane runs Docker containers on managed servers from €9 a month, with daily volume backups.
- Zeabur has an Uptime Kuma marketplace template. However, it currently uses version 2.0.2.
How Much Server Does Uptime Kuma Need?
Uptime Kuma publishes no official minimum. Cloudron’s package requires 256 MB of RAM, xCloud’s template requires 512 MB and Railway estimates about 512 MB. Based on those figures, here is a practical starting point:
| Setup | Monitors | Database | Recommended server |
|---|---|---|---|
| Personal or side project | Up to 25 | SQLite | 1 vCPU, 512 MB to 1 GB RAM |
| Small business or agency | 25 to 150 | SQLite | 1 vCPU, 1 to 2 GB RAM |
| Large agency or SaaS | 150+ | MariaDB | 2 vCPU, 2 to 4 GB RAM |
Treat this as a starting point rather than a strict rule. Also, short check intervals and long history retention both raise disk and memory use.
Cost Breakdown: What You Will Actually Pay
Even among the best Uptime Kuma hosting providers, real cost has three parts: hosting, backups and your time. The third is the line item people forget.
| Option | Monthly hosting | Backups | Your time per month (estimate) |
|---|---|---|---|
| xCloud free plan + $5 VPS | ~$5 | Server snapshots from your provider | ~30 minutes (manual app upgrades) |
| PikaPods | From $3.30 | Included (your S3 storage) | Near zero |
| Elestio | From $11 | Included | Near zero |
| Cloudron free + $5 VPS | ~$5 | Included | ~15 minutes |
| Hostinger KVM 1 | $6.49, then $11.99 | Weekly, included | 1 to 2 hours |
| Railway Hobby | ~$5 to $8 | Volume backups to configure | ~30 minutes |
| DIY VPS (Docker) | $4 to $6 | +20% to 30% on most clouds | 1 to 2 hours |
If an hour of your time is worth $30, a “cheap” $5 VPS that needs two hours a month really costs $65. That is exactly why managed and panel-based options win for busy teams.
Set Up Uptime Kuma the Right Way (Whichever Host You Choose)
1. Keep the Monitor Away From What It Monitors
Use a different server from your production sites. Preferably, pick a different provider or region too. Otherwise, a single provider outage hides itself.
2. Monitor the Monitor
Of course, Uptime Kuma cannot alert you about its own crash. So, add an external check on the Kuma URL from a free SaaS monitor. Alternatively, run a heartbeat check with a tool like Healthchecks on another server.
3. Lock Down the Dashboard
Turn on the built-in 2FA right after you create the admin account. Also, put the dashboard on its own subdomain behind HTTPS. Then keep public access limited to status pages. Our guide to maximizing VPS security covers firewall basics.
4. Back Up /app/data on a Schedule
Version 2 removed JSON export. Instead, back up the whole data folder or your MariaDB database. Next, store copies off the server. Then test a restore before you need it.
5. Plan Around Single-Location Checks
Each Uptime Kuma instance checks from one place. Therefore, a network blip near your server can trigger false alerts. So, set retries to 1 or 2 (version 2 defaults to 0). You can also run a second instance in another region. The Globalping integration is another way to add locations.
6. Put Status Pages on Your Own Domain
Uptime Kuma can map each status page to its own domain, such as status.yourbrand.com. Point a DNS record at the server, add SSL and set the domain in the status page settings.
Common Mistakes to Avoid
- Hosting Kuma on the same server as your sites. One crash takes down the site and the alert together.
- Deploying an outdated template. Several one-click images still ship 1.23. Start on version 2 to avoid a slow migration later.
- Storing /app/data on NFS. The project does not support network file systems. As a result, SQLite can corrupt.
- Skipping the volume on PaaS platforms. Without a persistent volume, every redeploy wipes your monitors.
- Leaving 2FA off. Your dashboard holds credentials for notification channels and internal URLs.
Which Uptime Kuma Host Fits You?
| If you are… | Best choice | Why |
|---|---|---|
| An agency managing client sites | xCloud | Free panel, one server for monitoring, one dashboard for all sites |
| A solo founder | PikaPods | Managed for $3.30 a month |
| A team with no ops time | Elestio | Updates and backups fully handled |
| A homelab or self-hosting fan | Cloudron or Coolify | Many apps on your own hardware |
| New to servers but on a budget | Hostinger VPS | Big VPS, template and weekly backups |
| Already deep in one cloud | Akamai, Vultr or DigitalOcean | Keep billing and tooling in one place |
Run Uptime Kuma on xCloud in Minutes
If you manage more than a couple of sites, a control panel saves the most time. With xCloud’s self-managed hosting, you connect your own server and deploy Uptime Kuma next to your other apps. Would you rather have xCloud handle the server too? xCloud managed hosting provisions and secures it for you.
Here is a simple setup that works well for agencies:
- Rent a small VPS from a different provider than your production servers.
- Connect it to xCloud on the free plan.
- Deploy Uptime Kuma as a one-click app and add your status page domain.
- Watch the monitoring server’s own CPU, RAM and disk with xCloud server monitoring.
Want a different tool? xCloud’s catalog includes more than 50 one-click monitoring apps, such as Gatus, OneUptime and Grafana.
Ready to set up your monitor? Compare xCloud plans and deploy Uptime Kuma today.
Your 2026 Roadmap: Pick a Host and Ship Your Monitor This Week
In the end, the best Uptime Kuma hosting providers all run the same open-source app. The real differences are price, version freshness, backups and how much of your time they save.
| Goal | Expert pick |
|---|---|
| Best overall value | xCloud free plan + $5 VPS |
| Cheapest managed | PikaPods |
| Zero maintenance | Elestio |
| Auto-updated self-hosting | Cloudron |
| Biggest VPS for the money | Hostinger KVM 1 |
What to do this week: pick a host on a different provider from your sites, deploy Uptime Kuma 2.x and turn on 2FA. Then add HTTP monitors for your key pages, connect one alert channel and point an outside check at Kuma itself. For more ways to keep sites online, read our tips to prevent downtime.
If you have found this blog helpful, feel free to subscribe to our blogs for valuable tutorials, guides, knowledge and tips on web hosting and server management. You can also join our Facebook community to share insights and engage in discussions.
Frequently asked questions
What are the best Uptime Kuma hosting providers in 2026?
For most people, the best Uptime Kuma hosting providers are xCloud, PikaPods and Elestio. xCloud is best for running Kuma free on your own server with a control panel. PikaPods is the cheapest managed option. Meanwhile, Elestio is the most hands-off.
Is Uptime Kuma free?
Yes. Uptime Kuma is open source under the MIT license. That means you can use it commercially at no cost. You only pay for the server or managed service that runs it.
Can I host Uptime Kuma for free?
Partly. xCloud’s free plan and Cloudron’s free plan cost nothing. Even so, you still need a server, which usually starts at $4 to $6 a month. Truly free cloud tiers often sleep or lose data, which defeats the purpose of a monitor.
How much RAM does Uptime Kuma need?
There is no official minimum. Cloudron requires 256 MB. Most other hosts recommend about 512 MB. For version 2 with up to 150 monitors, 1 to 2 GB of RAM gives comfortable headroom.
Should I use SQLite or MariaDB with Uptime Kuma 2?
SQLite is fine for most setups and stays the default. Choose MariaDB if you plan on hundreds of monitors. Decide early because the project does not officially support moving from SQLite to MariaDB later.
Does Uptime Kuma support monitoring from multiple locations?
Not on its own. Each instance checks from where it is hosted. To add locations, run a second instance in another region or use the Globalping integration.
Can I use my own domain for the Uptime Kuma status page?
Yes. Uptime Kuma lets you map each status page to a custom domain. You need a DNS record, an SSL certificate and a reverse proxy that supports WebSockets.
Uptime Kuma vs UptimeRobot: which is better?
Uptime Kuma gives you unlimited monitors and 20-second checks for the cost of a server. UptimeRobot is easier to start and checks from several locations. Many teams use both: Kuma for detail and a SaaS check on Kuma itself.
How do I upgrade Uptime Kuma from 1.x to 2.x?
Back up the /app/data folder first, then switch the image tag to 2 and start the container. Let the migration finish without interruption. Stopping it means restoring from backup. On large databases, the upgrade can take hours.
My Uptime Kuma keeps sending false down alerts. What should I check first?
First, check whether the alerts line up with network blips near your server. Then raise retries to 1 or 2 because version 2 defaults new monitors to 0. If false alarms continue, move Kuma to a more stable host or add a second instance in another region.