statoss.com valid

StatOSS

Hosted status pages and uptime monitoring. StatOSS requests your URLs once a minute (every 5 minutes on Free), keeps every result for 14 days and hourly totals for up to a year, and draws a public page that shows each failed check with its time and reason. Email, Slack, Discord, Microsoft Teams, Telegram, PagerDuty, Opsgenie, Pushover, ntfy or a webhook when a monitor goes down, turns slow, and when it is back.

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-26T17:27:22.523Z. Cached copy · Source on statoss.com

# StatOSS

> Hosted status pages and uptime monitoring. StatOSS requests your URLs once a minute (every 5 minutes on Free), keeps every result for 14 days and hourly totals for up to a year, and draws a public page that shows each failed check with its time and reason. Email, Slack, Discord, Microsoft Teams, Telegram, PagerDuty, Opsgenie, Pushover, ntfy or a webhook when a monitor goes down, turns slow, and when it is back.

StatOSS is the hosted, multi-user version of statoss-standalone, an MIT licensed single-tenant checker you can run yourself with Docker. Both share the same checks and the same page layout.

## What it does

- Every account owns status pages. A page has a name, an address (`<slug>.statoss.com` and `statoss.com/s/<slug>`), and a list of monitors (URLs). On Free the address is assigned as the page name plus a short random tail, such as northwind-k3f9; Hobby and Pro choose their own.
- One scheduler checks every monitor every minute (every 5 minutes on Free; certificates hourly and domain expiry every 6 hours) with a ten-second timeout. The checks come from four regions: Europe (Aarhus and Copenhagen in Denmark, Falkenstein in Germany), North America (Ashburn, USA), Asia (Singapore) and Oceania (Sydney, Australia). On Hobby and Pro the regions take turns, and an account can add London, Paris, San Jose, Toronto or São Paulo at $4 a month, Johannesburg or Tokyo at $8, and a fixed IP on an added location at $4. Targets on private or internal addresses are refused.
- A second look in the same region (another location, or the same one again when it is the only one) confirms every failure before it counts, and a failed check is checked again from every region at once. A monitor counts as down after two failed checks in a row and as back after one success; a monitor down from some regions only says which, on the page, in the alert and in the incident. Each change sends one alert; a slow threshold adds a slow state with its own alert.
- A page picks the regions that count toward its response times and its uptime. A monitor can have a slow threshold of its own in some regions, and one behind an allowlist can be checked from one region alone.
- The page draws a strip per monitor: bar height is the median response time, amber marks a timeout, red marks any other failure. Consecutive failures are grouped into one entry with the time and the reason. The checks behind a bar show where their time went: the lookup, the connection, the TLS handshake and the first byte.
- Sign in with email and password (confirmed by email), Google, or GitHub, with two-factor sign-in by an authenticator app.
- Monitors can be HTTP, TCP, DNS, ping, certificate, domain expiry, heartbeat or a component set by hand, and can be imported from UptimeRobot, Better Stack, Statuspage or any CSV with a URL column. Incidents, templates, maintenance windows (once, or every week or month, with a calendar feed); email, Slack, Discord, Microsoft Teams and webhook subscribers, im
…

Machine-readable: GET /v1/resolve?q=statoss.com · GET /v1/domain/statoss.com · 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 statoss.com:
1. POST https://agentwebmap.com/v1/sites/statoss.com/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://statoss.com/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/statoss.com/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/statoss.com).
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.