uptimepage.dev valid

Uptimepage

Uptime monitoring, public status pages and on-call in one.

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-27T10:03:59.775Z. Cached copy · Source on uptimepage.dev

# Uptimepage

> Uptime monitoring, public status pages and on-call in one.

Uptimepage is a hosted service for uptime monitoring, public status pages and on-call, in one product for teams. Checks run from up to thirteen regions (San Jose, Dallas, Bogotá, New York, Santiago, São Paulo, London, Frankfurt, Helsinki, Johannesburg, Singapore, Tokyo and Sydney); a failing check opens an incident automatically, pages the monitor's channels or its escalation policy, and can be posted to a branded status page on your own subdomain. Escalation policies page channels and on-call schedules level by level until someone acknowledges, and schedules rotate people daily, weekly or on a custom length, with calendar overrides. Alerts carry dedupe and flap-suppression so brief blips never page anyone. Organizations have role-based members and an audit log, and monitors, status pages and incidents are managed by REST API, Terraform or MCP. The production source is published under AGPL, so a team can audit what it runs and self-host if its requirements change. Public data is available as JSON, an RSS feed and an embeddable SVG badge. On Team, a status page can be private instead: it opens for the email addresses and domains on its list, after a code sent by email, or for anyone with a page password the owner shares. Uptimepage operates the hosted service at uptimepage.dev: the Standard plan is free with no card, the first 1,000 accounts get a more generous founding plan kept for life, and Pro and Team are the paid plans.

## Facts
- Check types: HTTP/HTTPS, TCP, DNS, TLS certificate, domain expiry, ICMP ping, cron-job heartbeat, scripted browser login flow, manual (state set by an operator)
- Check interval: Standard every 3 minutes, Founding and Pro every 60 seconds, Team every 30 seconds. Self-hosted installs start on the Team plan, and the operator can lower it to 10 seconds for HTTP, TCP, DNS and ping. Browser flows, TLS and domain checks have higher floors
- Check regions: 13 hosted regions: San Jose, Dallas, Bogotá, New York, Santiago, São Paulo, London, Frankfurt, Helsinki, Johannesburg, Singapore, Tokyo, Sydney; self-hosted can add any region by running a probe agent
- Alert channels: Slack, Discord, Telegram, Microsoft Teams, Google Chat, Mattermost, email, SMS, webhook, PagerDuty, ntfy, Pushover, Gotify, WhatsApp
- Status page: branded (logo + colour) on your own subdomain, or your own domain on Founding (one), Pro and Team
- WordPress: monitored from outside with no plugin: an HTTP check on the homepage plus one on an uncached page such as /wp-json/, a heartbeat for WP-Cron run from a system cron, a browser flow through a WooCommerce cart and checkout, TLS and domain-expiry checks
- Public history: 90 days
- Incidents: auto-opened on down, auto-closed on recovery, acknowledged by a responder, with public notes
- On-call schedules: layered rotations (daily, weekly or a custom length) in the schedule's timezone, optional weekly hours per layer, calendar overr
…

Related sites

Explore similar publishers →

Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.

Machine-readable: GET /v1/resolve?q=uptimepage.dev · GET /v1/domain/uptimepage.dev · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for uptimepage.dev:
1. POST https://agentwebmap.com/v1/sites/uptimepage.dev/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://uptimepage.dev/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/uptimepage.dev/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/uptimepage.dev).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.