DigitalOcean uptime monitoring with 30-second checks and SMS alerts
Short answer: DigitalOcean Uptime is a good, cheap start at $1 a month per check, with email and Slack alerts and up to four regions. It stops at 100 checks per team, IPv4 only, and no SMS or webhook alert channel. If a missed outage costs more than a pager, add AlertPing for 30-second checks, and SMS alerts on the same Droplets and App Platform apps.
DigitalOcean Uptime behavior checked against docs.digitalocean.com
alertping ▸ check preview
simulated
▸ type a domain to watch a check and an alert play out
▸ simulation of 3 regions · US East · EU Central · EU East
▸ waiting…▌
queued
probing▌
If ever goes down, you get:
Alert fired ▸ 2 channels · 6.2 s after first failure
AlertPing app
● DOWN : HTTP timeout confirmed from 3/3 regions (US East, EU Central, EU East). Incident opened.
sms · on-call
AlertPing: DOWN. Confirmed 3/3 regions . First fail: EU Central.
Simulation, not a measurement of your site: this preview runs entirely in your browser and the latencies are generated from the domain you typed. Real checks on your monitors run from our US East, EU Central and EU East regions.
read this first
DigitalOcean Uptime is real monitoring, with a narrow alert path
DigitalOcean does ship an uptime product, which is more than several hosts can say. A check runs against any HTTP or HTTPS endpoint or any IPv4 address by ICMP ping, reports from up to four regions, and can alert on downtime, a latency threshold or an approaching SSL expiry. It costs $1.00 per check a month, billed hourly, with no extra charge for alerts, and every invoice carries one check free.
The gaps show up when the site earns money. Notifications go out by email and Slack only, so an outage at 3 a.m. depends on someone reading a channel. Each check allows five alerts, each alert nine email addresses, and a team tops out at 100 checks. Checks run over IPv4 only. The docs do not list plain TCP port checks or a response string assertion, so a Droplet that answers 200 with a broken page can look healthy.
Droplet and App Platform alerts are a separate matter. Those watch resource use such as CPU and memory inside your account. They tell you a machine is busy, not whether a customer can load your checkout from outside.
the honest table
DigitalOcean Uptime next to AlertPing
| What you need | DigitalOcean Uptime | AlertPing |
|---|---|---|
| Alert channels | Email and Slack | SMS, email, Slack and webhook on every plan |
| Check types | HTTP, HTTPS and ICMP ping to IPv4 addresses | HTTP, HTTPS, ports, keyword and response string, API and SSL expiry |
| Checks included | $1.00 per check a month, up to 100 per team | Flat plans from $49 a month, no per-check meter |
| Regions | Up to four: Asia East, Europe, USA East, USA West | Multi-region, every failure confirmed from a second region |
| Alert limits | 5 alerts per check, 9 email addresses per alert | Alerts to every contact you choose, with acknowledgement |
| IPv6 and plain TCP | IPv4 only, TCP port checks not listed | Port checks for databases, SMTP and custom services |
| Best for | Hobby projects and a handful of cheap internal checks | Customer-facing apps where someone must be woken up |
DigitalOcean wins on price for a few checks and on staying inside the control panel you already use. The figures come from DigitalOcean's Uptime pricing page and its limits page. Running both is fine, the checks do not interfere.
the mechanics
Setting up outside monitoring for a Droplet or App Platform app
Point the check at your public domain, not the Droplet IP, so DNS, the load balancer and the certificate are all in scope. Add one check for each route that earns money, such as login, checkout and the API your front end calls, and assert on a string you know appears when the page is healthy. Use 30-second checks for anything customer-facing and require a second region to confirm before an alert fires.
Send the alert to SMS and Slack, and add a second contact. SMS, email, Slack and webhook alerts are included on every AlertPing plan with no credit packs. Nothing is installed on your Droplets, no firewall rule is needed beyond allowing public traffic, and you can keep the DigitalOcean checks running in parallel.
who needs this
Which DigitalOcean teams need this
Agencies hosting client sites on Droplets, where an outage becomes a phone call before anyone looks at a dashboard. SaaS founders running a paying product on App Platform or a managed database stack with no on-call tooling. Small teams whose sales funnel lives on one Droplet: a founder sending outbound email through a tool like Coldreach to a landing page loses every click while it is down and may not find out until replies dry up. If one missed outage costs more than a monitoring plan, you are the reader this page is for.
scope
What AlertPing does not replace on DigitalOcean
AlertPing does not read Droplet CPU, memory or disk, and it does not replace DigitalOcean's own resource alerts. It watches the public side: the URLs customers call, how fast they answer and whether the certificate is healthy. The same split between platform signals and outside checks appears on Fly.io, on Render and in our guide to website down alerts.
questions people ask
DigitalOcean uptime monitoring questions
Does DigitalOcean have uptime monitoring?
Yes. DigitalOcean Uptime checks HTTP and HTTPS endpoints and IPv4 addresses by ping from up to four regions, at $1.00 per check a month. Alerts go out by email and Slack only, with a cap of 100 checks per team.
How do I get SMS alerts when my DigitalOcean Droplet goes down?
DigitalOcean Uptime does not list SMS as an alert channel. Point an external monitor such as AlertPing at your public domain, add the routes that matter and send alerts to SMS and Slack. Checks run every 30 seconds without changes to your Droplet.
How much does DigitalOcean Uptime cost?
Each check costs $1.00 per month, billed in hourly increments, with no additional cost for alerts, and one free check credit on every invoice. A team can create up to 100 checks.
Can DigitalOcean Uptime monitor a site hosted somewhere else?
Yes. The docs say it can monitor any publicly accessible URL or IPv4 address, not only DigitalOcean resources. It checks over IPv4 only.
Is DigitalOcean Uptime enough for a customer-facing app?
For a hobby project, often yes. For a paid product you usually want SMS or phone alerts, response string checks and port checks, which are the parts it does not list.
Watch your DigitalOcean apps and page a human
AlertPing checks your domains and API routes as often as every 30 seconds, confirms every failure from a second region, warns before your SSL certificate expires, and sends SMS, email, Slack and webhook alerts on every plan. Flat pricing from $49 a month, with 30-second checks from $59.
keep reading