A little clarity.
Then back to building.

You can monitor websites and APIs with HTTP checks, network services with TCP checks, reachable hosts with ICMP, and certificate validity with SSL monitoring.

Most monitors only require a target, check type, interval, and one or more probe regions. You can begin on the Free plan without adding a payment method.

Use HTTP for websites and API endpoints, TCP for services listening on a port, ICMP when the host explicitly supports ping, and SSL when certificate expiration is the primary concern.

Independent regions help distinguish a local network problem from a service-wide outage. Regional confirmation can prevent one unreliable route from creating an unnecessary incident.

Many websites and edge networks intentionally block ICMP ping traffic. A failed ping does not always mean the website is unavailable. Use an HTTP check when your goal is to verify that a webpage or API responds correctly.

A failed observation starts an investigation. Repeated-failure thresholds and agreement between independent regions determine when an outage is confirmed and incident notifications are sent.

Yes. Monitor details include a paginated, filterable check log with timestamps, regions, status, latency, and the evidence captured for each observation.

Monitor charts support short operational windows and longer historical ranges, with average, median, and p95 latency views, regional comparison, incidents, failures, and maintenance context.

A failed observation opens an investigation. When the configured failure thresholds and regional confirmation rules are met, the outage is confirmed and notifications are sent to configured destinations. The incident retains evidence and updates through recovery.

Notifications can be routed through email and configured integrations such as Slack or webhooks. Delivery history records outcomes and retry information for operational review.

The incident timeline keeps relevant observations, affected regions, lifecycle changes, team updates, and notification activity together so responders can understand what happened without reconstructing it later.

Scheduled maintenance provides operational context for the affected monitors and keeps planned work visually distinct from unexpected downtime in telemetry and customer communication.

No. Public responses use component names and status-page content without exposing private monitor targets or organization data.

Create named sections, assign components to each section, choose customer-facing display names, and arrange them in the order that makes sense to your audience.

Published status pages can surface current incidents, incident-update timelines, component health, uptime history, and scheduled maintenance using the monitoring data connected to each component.

Yes. Status pages include a subscriber interface with verification and notification preferences so customers can choose the updates relevant to them.

The Free plan includes 10 monitors, checks every five minutes, up to three regions per monitor, one status page, and up to five team members.

Yes. Annual Pro and Business plans provide twelve months of service for the price of ten.

Yes. Workspace owners can invite members, review invitation delivery, assign roles, and manage each member’s alert-email preferences from Team management.

Anyone can contact the platform team from the public Contact page. Signed-in users can also create a workspace support ticket to retain technical context and the full conversation history.