# 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 (`.statoss.com` and `statoss.com/s/`), 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, imported from a CSV or a list of addresses; a logo, colours, a time zone, a password or a list of allowed people per page. - On-call on Hobby and Pro: a page's sources take alerts from anything that sends to PagerDuty's Events API, Opsgenie's Alert API or Sentry's webhooks, at https://api.statoss.com with the URL changed. Alerts repeat until someone acknowledges them, from the dashboard, the email, Pushover, Slack buttons, the API or MCP. Pro adds escalation policies, schedules, each person's own ways to be reached (email, Pushover, ntfy, Telegram) and an import from PagerDuty or Opsgenie. Docs at /docs/on-call. - Errors on every plan: any Sentry SDK, @statoss/sdk or the Python statoss package sends to an app's DSN at https://ingest.statoss.com. Events are grouped into issues, with releases, source maps uploaded by sentry-cli or the StatOSS CLI, and an app's own levels, categories and fields. On Hobby and Pro an app's alert rules open on-call alerts; on Free new and regressed high-priority issues are emailed to the owner. Docs at /docs/errors and /docs/send-errors. - Logs, an add-on to Hobby and Pro at $5 a month with 15 GB, then $0.25 a GB (lines kept 30 days count twice): lines from the StatOSS and Sentry SDKs, OpenTelemetry, the Vercel, Fly, Cloudflare and Heroku drains and plain JSON, with an app's key, kept beside its errors. One search box, live tail, patterns, saved views and log alerts through on-call. Docs at /docs/logs and /docs/send-logs. - A REST API at https://statoss.com/api/v1 (OpenAPI at /api/v1/openapi.json, docs at /docs/api) with keys that read or write and reach every page or one. An MCP endpoint at /api/v1/mcp with the same key, and a read-only one at /mcp next to every page. An MCP client without a key signs its person in with OAuth 2.1, for read or read and write, every app or one; Account, Connected apps lists and revokes them (docs at /docs/agents). An agent without an account registers as https://statoss.com/auth.md describes (auth.md v0.6), builds a draft of status pages, monitors and apps, and its person claims it into a team. The front page, https://statoss.com/docs/agents#setup-prompt and the dashboard's Help carry a prompt to paste into a coding agent, which does that for the project it is in. Deploy markers posted from CI show on the response-time chart. ## Plans - Free, hosted: 1 status page, 1 monitor, checks every 5 minutes, 7 days of history, down and recovery emails, 5,000 errors a month kept 30 days. No card. - Free, self-hosted: run statoss-standalone yourself. Unlimited pages and monitors, your own SMTP server. - Hobby, $4 a month: 1 status page, 10 monitors, checks every minute from every region in turn, 90 days of history, an address of your choice, email plus Slack, Discord, Microsoft Teams, Telegram, PagerDuty, Opsgenie, Pushover, ntfy and webhook alerts, on-call for one person (3 alert sources, repeats until acknowledged), 50,000 errors a month kept 30 days, and check locations to add. - Pro, $15 a month: 10 status pages, 100 monitors across them (50 per page), an address of your choice, and your own domain with the certificate handled. Pro also has email, Slack, Discord, Teams and webhook subscribers (1,000 per page, more in blocks of 1,000 at $5 a month), a monthly uptime report, a password on the page, a year of history, incident updates and post-mortems drafted from the check data, and components that follow a vendor's status page. Pro also has private pages, open only to the people and email domains you allow, includes $4 a month of added check locations, and includes 3 people on the team, $5 a month for each one after, up to 25. Pro's on-call is for the whole team: 50 alert sources, escalation policies, schedules and the PagerDuty and Opsgenie import. Pro takes 500,000 errors a month, kept 90 days. Billing runs through Polar. Cancel from the billing page at any time. ## Pages - [Home](https://statoss.com/): the example page, how the strip is read, setup, alerts, pricing. - [Pricing](https://statoss.com/pricing): the three plans side by side, and questions about billing. - [Docs](https://statoss.com/docs): the status page, incidents, subscribers, feeds, addresses and domains, checks, alerts, on-call, errors, logs, deploy markers, importing, teams, plans and your data, the API and MCP, self-hosting. - [Monitoring](https://statoss.com/monitoring): one page per check type: website, API, SSL certificate, domain expiry, cron job heartbeat, TCP port, DNS, ping. - [Integrations](https://statoss.com/integrations): Slack, Discord, Microsoft Teams, Telegram, PagerDuty, Opsgenie, Pushover, ntfy, the signed webhook, and the badge and widget. - [Compare](https://statoss.com/compare): StatOSS next to UptimeRobot, Better Stack, Atlassian Statuspage, Instatus, Uptime Kuma, Pingdom, Hyperping, openstatus, Checkly, Cronitor, Gatus and StatusCake, hosted Uptime Kuma (on a VPS or PikaPods), Sentry, PagerDuty, and leaving Opsgenie before it shuts off on 5 April 2027. - [Guides](https://statoss.com/guides): what a status page is, uptime monitoring explained, how to write a post-mortem, status page best practices. - [Open source status page](https://statoss.com/open-source-status-page), [Free status page](https://statoss.com/free-status-page), [Self-hosted status page](https://statoss.com/self-hosted-status-page). - [Private status page](https://statoss.com/private-status-page), [Status page API and MCP server](https://statoss.com/status-page-api). - [On-call](https://statoss.com/on-call), [Error tracking](https://statoss.com/error-tracking), [Logs](https://statoss.com/log-management). - [Uptime calculator](https://statoss.com/tools/uptime-calculator): an uptime percentage as downtime per day, week, month and year. - [Changelog](https://statoss.com/changelog): what changed, newest first, also as RSS and Atom. - [Support](https://statoss.com/support): search the docs, write to support, or chat when someone is available. - [Sign up](https://statoss.com/signup) - [Security](https://statoss.com/security), [Subprocessors](https://statoss.com/subprocessors), [Data processing agreement](https://statoss.com/dpa) - [Privacy](https://statoss.com/privacy) - [Terms](https://statoss.com/terms) - [statoss-standalone on GitHub](https://github.com/kroqdotdev/statoss-standalone): the self-hosted version. ## Optional - [Full description](https://statoss.com/llms-full.txt): everything above in more detail, including how checks, alerts, plans and accounts behave. Contact: support@statoss.com ## Uptime reports - [Uptime reports](https://statoss.com/uptime): measured uptime of 20 services developers depend on (GitHub, GitLab, npm, PyPI, Docker Hub, Cloudflare, Vercel, Netlify, Fly.io, Render, AWS, Google Cloud, Stripe, Twilio, Slack, Discord, OpenAI, Anthropic, Sentry, Supabase), from StatOSS's own checks every 5 minutes. Each report at https://statoss.com/uptime/ has the state now, availability over 24 hours, 7, 30 and 90 days (and a year, once there is one), response time by location, every outage dated in UTC, and what exactly is checked. - [A month of the reports as JSON](https://statoss.com/uptime/data.json?month=2026-10): per service, location and UTC day, the checks, failed checks, uptime, median and 95th percentile response time, and the month's outages. Any month from the reports' first, as ?month=YYYY-MM.