Uptime monitoring
Get notified when scheduled checks detect downtime on public websites and API endpoints, with recent result history and alerts that stay actionable.
Downtime is expensive (and usually messy)
A 12-minute outage can turn into a two-hour incident: clients start emailing, dashboards show partial failures, and you’re trying to answer “is it fixed?” without reliable check results.
- • Lost revenue (orders, signups, leads).
- • Support load: tickets, calls, Slack pings.
- • Reputation damage: “it was down again” sticks.
What we do
We run repeated checks against your endpoints, detect failures, and keep their alert events and recent observations available for review.
- • HTTP(S) monitoring for websites and APIs.
- • Review measured response times in recent results.
- • Track open and resolved availability alert events in the alert inbox.
How it works
Paste a URL (website or API). Optionally add a name like “Client portal API” to keep your list readable.
Choose interval and target details for HTTP or SSL checks so the monitor stays readable and actionable.
When the check fails, we create an alert event and notify the configured routes. A successful recovery resolves that event and can send a recovery notification.
Features
Run checks at the interval allowed by your plan and keep the capture time for each recent observation.
Review average, p50, p95, and individual response-time observations; response-time threshold alerts are not part of the launch offer.
See active and resolved availability events in the alert inbox alongside each monitor’s recent check results.
Track status code, latency, SSL expiry state, and recent check history from the monitor detail page.
Route notifications through email, webhooks, Slack, Teams, Discord, or SMS according to your plan limits.
Keep a clean list of monitored endpoints and share status updates without endless back-and-forth.
Common use cases
Monitor the public app and critical API endpoints on a scheduled cadence after deployments.
Detect failed public storefront or checkout endpoint checks and notify the configured alert routes.
Monitor client sites and portals, review alert events and recent results, and send one status link when something breaks.
FAQ
What exactly counts as “down”?
A check is considered failing when the endpoint does not respond, times out, or returns an unhealthy status for the configured monitor.
Can I monitor APIs, not just websites?
Yes. You can monitor internet-reachable public HTTP(S) endpoints that pass the platform's target-safety checks. A common pattern is using /health, /status, or a lightweight API endpoint.
How often do checks run?
You choose an interval allowed by the plan. Shorter intervals detect issues earlier, while longer intervals reduce check volume.
How do alerts work?
Owners can configure email, webhook, Slack, Teams, Discord, or SMS channels, then route monitor alerts with cooldown and recovery settings.
Do you keep an incident history?
The alert inbox keeps active and resolved alert events, and each monitor shows recent observations. A dedicated per-monitor incident timeline with calculated durations is not part of the launch UI.
Can I share uptime status with clients?
Yes — pair uptime monitoring with Status Pages. Share one public link during incidents so clients stop asking for updates in every channel.
Create your account, add your first endpoint, and start collecting recent uptime observations.