--- title: Status Pages for Incidents & Uptime description: Hosted status pages at yourname.watchfor.io, driven by your monitors: confirmed incidents post themselves, plus uptime heatmap, maintenance, RSS and a badge. canonical: https://watchfor.io/status-pages --- # Status Pages That Update From Your Monitors Answer “is it down?” before the support inbox fills. A WatchFor status page posts each confirmed incident within about a minute and resolves it with the incident. [Get started for free](/auth/sign-up)[View pricing](/pricing) ## What a WatchFor Status Page Does The page updates itself from confirmed incidents. The wording stays under your control ### Incidents Post Themselves With auto-publish on (the default), a confirmed incident on a monitor or host attached to the page becomes a public incident within about a minute. It resolves when the internal incident resolves. A single failed check never reaches the page, only confirmed problems do. ### Components Backed by Monitors, Tags or Hosts Name components the way customers do: API, Dashboard, EU region. Back each one with specific monitors, with a tag so monitors you tag later join automatically, or with servers running watchfor-agent. Show it as one line, a collapsible group or every monitor listed. ### Uptime Heatmap per Component Every component shows an uptime percentage and a daily heatmap. The default view covers 30 days, and visitors can page back through earlier three-month windows. Maintenance shows as maintenance, not downtime. Incidents you mark as false positives disappear from the history. ### Updates in Your Words Post incidents by hand with Investigating, Identified, Monitoring and Resolved updates. The severity you pick (minor, major or critical) sets the component state. Edits you make to an auto-published incident are never overwritten by the automation. ### Maintenance From Your Windows Planned work is announced from a maintenance window, never typed directly on the page. The notice goes up ahead of time and moves from Scheduled to In progress to Completed, and affected components turn blue instead of red. Nobody can relabel an outage as maintenance after the fact. ### Third-Party Status Next to Yours Mirror the public status of 30 providers, including GitHub, Cloudflare, Stripe, OpenAI and Anthropic, polled every 3 minutes. Visitors can tell whether the problem is you or your provider. A provider's outage never changes your own banner. ### Public, Password-Protected or Private Public for customers. Password-protected for partners or beta users: one shared password, and visitors stay signed in for 7 days. Private returns 404 to visitors and shows the page only to signed-in members of your organization. ### Badge, JSON and RSS Public pages serve an SVG status badge for your site or README, a CORS-enabled status.json that needs no API key, and an RSS feed of incidents and maintenance. The page is cached for about a minute and refreshed on every change, so it stays fast when everyone checks it at once. ## Your page, and how you build it A confirmed incident appears on the public page without anyone posting it. Pick who can see the page, auto-publish incidents and group components. Each component sets its display mode, incident detail and monitors. Maintenance windows mute alerts, stay out of the SLA and post a notice. ## Why Run Your Status Page on WatchFor A status page updated by hand goes stale exactly when it matters, because the person who should update it is busy fixing the outage. A WatchFor page reads the same confirmed incidents your team is paged for. It turns red without anyone remembering to flip a switch, and it stays green through one-location blips that never become incidents. You keep control of the public story: the incident wording and severity, how much each component reveals, and whether a post-mortem is published. [Start monitoring now](/auth/sign-up) Live at yourname.watchfor.io as soon as you save Only confirmed incidents reach the page; one failed check never does Per component: status only (default), the cause in plain words, or full detail Maintenance announced from maintenance windows and shown as neutral time Incidents marked as false positives removed from the page and its history 30 third-party providers mirrored without touching your own banner Your logo, header position and a light, dark or auto theme Every page and announcement change recorded in the activity log ## How Status Pages Work Set it up once, then confirmed incidents keep it current 1 ### Start a Page Pick a name and a URL name; the slug becomes yourname.watchfor.io. Run separate pages for different products, regions or audiences. The pricing page lists how many your plan includes. 2 ### Add Components Attach monitors, tags or hosts to each component, or add a third-party provider. Choose the display mode and how much an auto-published incident explains. 3 ### Choose Visibility and Branding Make it public, password-protected or private. Upload a logo and set the default theme. You can change any of it later; the URL stays the same. 4 ### Publish and Share Save and the page is live. Link it from your app or help center and embed the badge. Confirmed incidents post themselves; you add updates when there is something to say. ## Status Page Use Cases One product, several audiences ### Public Incident Communication Support pastes one link during an outage. Customers see which component is affected, the latest update and the timeline. You write each update once instead of answering every ticket separately. ### Internal Team Overview A private page shows signed-in members every service on one screen. Set its components to Full detail and incidents show exact values, disk paths and process names you would never publish. ### Multi-Product & Multi-Region Separate pages per product, brand or region, each with its own components and visibility. A public customer page and a private internal page can be built from the same monitors. ### Is It Us or Our Provider? When Stripe or Cloudflare has an outage, your customers feel it too. Third-party components put the provider's live status next to yours, with a link to its own status page, so support can answer in one sentence. ## Frequently asked questions How WatchFor status pages behave [All questions→](/faq)[Ask us directly](/contact) What is a status page? A status page is the public side of your monitoring: one URL that answers “is it just me, or is it down?” without a support ticket. A WatchFor page shows an overall banner (All systems operational, Some systems degraded, Major outage or Scheduled maintenance), each component's state and uptime heatmap, active incidents with their updates, scheduled maintenance and the incident history. Do components update automatically? Can I run more than one status page? Can I control what customers see? Can I make a status page private? Is there an RSS feed? Will the page stay up during a big outage? How do I announce scheduled maintenance? Can I show the status of services I depend on? Can I use my own domain? ## From our blog Guides, deep-dives, and best practices from the WatchFor team [Monitoring ### The complete status page guide: from bare green dots to a page customers actually trust Aug 23, 2026·7 min readRead article](/blog/status-page-complete-guide)[Reliability ### Incident status update templates: copy-paste wording for every stage Oct 03, 2026·13 min readRead article](/blog/incident-status-update-templates)[Monitoring ### Status Page Best Practices: turning your worst day into trust Jun 24, 2026·4 min readRead article](/blog/status-page-best-practices) ## Give Customers One Link to Check Create a page, attach the monitors you already run and share yourname.watchfor.io. The next confirmed incident posts itself, and you add the updates. Status pages are included on the Free plan, no credit card required. [Get started for free](/auth/sign-up)[View documentation](/docs/status-pages) --- Canonical page: https://watchfor.io/status-pages · Site guide: https://watchfor.io/llms.txt