downtimeHow much are your window overruns costing you?
Enter your numbers. The industry average is 18 minutes of overrun per window — your finance team already knows what that costs.
// Input Parameters
Enter your parameters and click
Calculate to see your revenue at risk
Every tool your on-call rotation needs
Hover any card to see it in action. These aren't mockups — they're pixel-accurate screenshots from the live product.
Window Scheduling
Cron-syntax or one-click scheduling for every service. Set duration, grace period, and escalation threshold once.
Escalation Chains
Multi-tier alert routing: on-call SRE → team lead → VP Engineering. Integrates with PagerDuty, Opsgenie, and Slack.
Compliance Audit Logs
Immutable, timestamped records for every window open, close, overrun, and acknowledgment. SOC2 and ISO 27001 ready.
Dependency Mapping
Visualize upstream and downstream service dependencies. Know before you schedule which services will cascade.
Multi-Cloud Support
AWS, GCP, Azure, and on-prem in one view. No per-cloud agents — a single API token covers your entire estate.
SLO Burn Rate Tracking
Correlate window overruns directly to SLO budget burn. See which maintenance events are eating your error budget.
From engineers who ship at 2 a.m.
“We were learning about billing-worker overruns from Stripe support tickets — 40 minutes after the fact. Downtime fires within 4 seconds. That's the difference between a postmortem and a non-event.”
“Our compliance team wanted audit logs for every maintenance window — who opened it, who closed it, did it run over. Downtime just hands us a CSV. SOC2 audit prep went from three days to 45 minutes.”
“I manage 34 services across AWS and GCP. Before Downtime, I had a Notion doc tracking windows manually. Now I have one dashboard, and my 2 a.m. on-call rotations are actually survivable.”
Monitor 5 Services Free
Two fields. Zero sales cycle. You're monitoring in under 3 minutes.