Sensitive settings encrypted
Stored monitor credentials and notification configuration are encrypted. Private configuration stays out of public status pages.
Website & infrastructure monitoring
Know what’s up.
Act when it matters.
Website, API, network, SSL, DNS and scheduled-job monitoring in one clear workspace. Confirm failures, route useful alerts and follow recovery.
Free diagnostics are available now. Public account registration is currently closed.
Monitors12
Uptime99.97%
Response284 ms
Response timeIllustrative · 24 hours
WebsiteHTTP
UP
Account APIAPI
UP
GatewayPing
UP
DocumentationPage speed
DEGRADED
11 up · 1 degraded · no open outage in this example
Coverage that fits your stack
One place for the signals you depend on
Choose the check that answers the question. Keep availability, performance and expiry signals distinct.
Website
Status, content and response checks for public URLs.
Explore monitoring →Ping
Track host reachability and packet loss.
Explore monitoring →Port / TCP
Confirm a public service accepts connections.
Explore monitoring →SSL certificates
Catch expiry and certificate validation failures.
Explore monitoring →DNS
Follow important records without losing history.
Explore monitoring →API
Assert responses and run bounded multi-step scenarios.
Explore monitoring →Cron / heartbeat
Detect a job that stops reporting its success signal.
Explore monitoring →Domain expiry
See available registry expiry dates before renewal.
Explore monitoring →Email domain health
Check MX, SPF, DMARC and configured DKIM records.
Explore monitoring →From signal to resolution
A clear path through every disruption
- 1
Monitor
Run the right check.
- 2
Detect
Record the result.
- 3
Confirm
Confirm failure before a downtime alert.
- 4
Alert
Reach your configured destinations.
- 5
Recover
Close the incident when healthy.
- 6
Report
Review duration and trends.
Confirmation behavior depends on monitor type and configuration. Standard availability checks use failure confirmation to reduce noise.
Incidents with context
See what happened.
Know when it recovered.
Automatic incidents retain failure reasons, alert history and recovery duration. Dependencies and bounded escalation help keep genuine outages actionable.
Explore SLA / SLO tracking →Example incident timeline
- 10:02 · Detected
Website checks confirmed a failure.
- 10:04 · Investigating
The team posted a manual communication update.
- 10:09 · Recovered
Successful checks closed the incident. Duration: 7 minutes.
Service status
Example preview✓ All systems operational
Website✓ Operational
API✓ Operational
Dashboard✓ Operational
Email✓ Operational
Uptime history · incident updates · planned maintenance
Communication that builds trust
Keep everyone informed
Publish service components, maintenance and incident updates. Double opt-in email subscriptions let visitors choose to receive updates.
Explore status pages →Illustrative report
Service review
SLO target99.9%
Error budgetDuration-based
Uptime, downtime, MTTR, meaningful percentiles and period comparisons in private HTML / PDF reports.
Useful before you create an account
Find the next thing to fix
Practical safeguards
Built to keep monitoring data private
Public destinations only
Network checks enforce protections against private and reserved destinations.
Workspaces stay separate
Organization access controls protect monitors, incidents and reports. Email and signed webhooks route configured alerts.
Checks currently run from one production location. Independent external monitoring is not yet available. Read our privacy policy.
Built for practical operations
Your stack. Your workflow.
Developers
Assert API behavior and investigate response history.
IT teams
Bring public host, certificate and DNS checks together.
Agencies
Organize client workspaces and share clear reports.
Small businesses
Watch your website and renewal dates with useful alerts.
SaaS teams
Combine service checks, dependencies and public communication.
Start with a useful answer
Run a free check today. Explore plans for ongoing monitoring.