DS Uptime
Uptime monitoring, incidents and status pages in one place.
DS Uptime checks every endpoint you depend on as often as every 15 seconds — with the method, headers, body and status codes that define healthy for it. Every failure is re-checked from two more regions before it counts, slow responses are flagged before they turn into downtime, and branded status pages keep customers informed on your own domain.
- 142 msUpPublic APIapi.acme.com/health99.98%
- 88 msUpWeb appapp.acme.com100%
- 1.8 sDegradedPayments webhookpay.acme.com/hook99.91%
- —MaintenanceSearch servicesearch.acme.com99.95%
- Monitoring · 10:21Queue drained, latency back under 400 ms.
- Identified · 10:09Upstream provider rate limiting.
- Investigating · 10:02Slow responses on payment webhooks.
Monitoring, incidents and status pages — connected
From the first failed check to the final all-clear on your status page, one tool covers the whole outage lifecycle.
- 01
Check
Every endpoint on its own schedule, as often as every 15 seconds.
GET /health → 200 - 02
Confirm
A failure is retried, then re-checked from two more regions before it counts.
confirmed · 3/3 regions - 03
Open
A confirmed outage or a slow streak opens an incident on its own.
incident · HTTP 503 - 04
Alert
Your team hears about it once, not on every failed check.
→ Slack #ops - 05
Update
Share progress as you work, straight on the status page.
identified · 10:09 - 06
Recover
The next healthy check closes the incident and sends the all-clear.
resolved · 7 m 12 s
Monitor anything that speaks HTTP
Public websites, private APIs behind a token, webhooks that expect a POST body — each monitor sends exactly the request you define and judges the answer by your rules.
- GET or POST with custom headers, query parameters and JSON bodies
- Healthy means what you decide: specific status codes, or any 2xx
- Intervals from 15 seconds, with a timeout and slow-response threshold per monitor
- Uptime over 24 hours, 7, 30 and 365 days, with min, average and max response times
- 24 hours100%
- 7 days99.98%
- 30 days99.95%
- 365 days99.91%
A status page on your own domain
Group monitors into public pages your customers can bookmark — live status, uptime history and every incident update, so they get answers without opening a ticket.
- Your logo and your own domain, like status.yourcompany.com
- An overall status that always reflects the most serious issue
- Incident updates appear the moment you post them
- Notices, warnings and scheduled maintenance windows
- Website100%
- Public API99.97%
- Payments99.93%
- Dashboard100%
- Resolved · 10:28 — Payments are processing normally.
- Monitoring · 10:21 — A fix is live, we're watching error rates.
- Identified · 10:09 — An upstream provider is rate limiting us.
Alerts in the tools your team already uses
Each monitor posts to its own destination. Down, degraded and recovered events arrive formatted for it — and a test message confirms the wiring before you need it.
- Service
- Payments API
- Status
- DEGRADED
- Cause
- Slow response: 1840ms (> 800ms threshold)
- When
- 2026-09-25T09:55:41Z
{"event": "alert","status": "down","severity": "critical","monitor": "Payments API","cause": "HTTP 503","startedAt": 1790071334000,"resolvedAt": null}
Who it's for
- SaaS & platform teams
- DevOps & SRE
- Digital agencies
- IT operations
Why DS Uptime
One tool, not three
Monitoring, incident management and the public status page share the same data, so nothing has to be copied or kept in sync by hand.
Uptime you can quote
Uptime is calculated from real outage time, only from when a monitor was created — slow periods never count as downtime and new monitors never inflate the numbers.
Private by default
Only the status pages you publish are public. Configuration and every internal view sit behind authentication, and customer domains can never reach them.
“Know about every outage before your customers do — and keep them informed while you fix it.”
Get started with DS Uptime
See DS Uptime in action
Request a walkthrough and we'll show you exactly how DS Uptime fits your team.