--- title: "Status page examples worth copying | Logdash" description: "GitHub, Vercel, Stripe, Linear and Cloudflare status pages, checked in October 2026: what each does well, what a small SaaS should copy and what to skip." url: https://logdash.io/status-page/examples --- # Status page examples The status pages worth copying are GitHub for incident updates, Vercel for per-region components, Stripe for a short component list, Linear for showing an unflattering number and Cloudflare for maintenance notices. Every page below was checked on 2 October 2026\. All five run on a hosted tool: GitHub, Vercel, Stripe and Cloudflare on Atlassian Statuspage, Linear on incident.io. Even Stripe retired its custom-built status.stripe.com, which now redirects to Statuspage. The tool matters less than three decisions: what counts as a component, how often someone posts during an incident, and how honest the numbers are. ## Best status page examples - GitHub, githubstatus.com. 11 components named after what users touch: Git Operations, Webhooks, API Requests, Actions, Copilot. On 1 October 2026 an Actions incident got 10 timestamped updates in 3 hours 9 minutes, closing with a promise of a root cause analysis. Fixes that happened before anyone posted are logged as retroactive incidents rather than left out. - Vercel, vercel-status.com. 67 components, 20 of them CDN regions named by code and city, from ARN1 Stockholm to YUL1 Montréal, so a customer can check their own region. Its 28 September incident states the exact window, 13:01 to 13:11 UTC, and who was hit: functions on the Edge runtime. - Stripe, stripestatus.com. Short for a company its size: 6 components named after product areas, from Stripe API to Acquirers and payment methods, each with 90 days of bars. Maintenance is announced per payment method, such as TWINT or BLIK, and there is an Atom feed for anyone who wants updates without an account. - Linear, linearstatus.com. 6 components: application, API and integrations, each split into US and EU. It shows the EU application at 99.54% next to 100% for the API, which is why the 100% is believable. - Cloudflare, cloudflarestatus.com. 479 components, mostly data centres grouped into 7 regions. On 2 October it listed 25 upcoming maintenance windows by city, such as NRT Tokyo. ## SaaS status page examples for a small team Copy Linear and Stripe, not Cloudflare. A small SaaS has 3 to 6 things a customer can tell apart: the app, the API, webhooks, maybe sign-in. Name them that way. 479 components is right for a global network and noise for a product with one database. Steal GitHub and Vercel habits instead: post fast, timestamp everything, name the UTC window when it is over. ## Status page design examples Nearly every page above shares one layout: an overall status line, a row per component, a strip of daily bars and an uptime percentage. Linear and Statuspage pages show 90 days of history, and the Logdash component draws the same layout from your monitors, styled with your Tailwind theme. Every Statuspage page also serves its state as JSON, and so does every published Logdash page: ```bash # GitHub, on Atlassian Statuspage curl -s https://www.githubstatus.com/api/v2/summary.json | jq -r '.status.description' # Logdash's own status page, by its custom domain curl -s https://api.logdash.io/v1/status_pages/status.logdash.io | jq -r '.status' ``` 1. **Monitor what you will list** Create one Logdash service per component you plan to show, and point its HTTP monitor at a health URL. 2. **Publish the page** Add the monitors to a status page and publish it, or render it in your own design with the shadcn component or the Next.js starter. 3. **Test the alert** Stop one service. On the next check the row turns red, and before a customer opens the page a Telegram alert reaches you with the monitor name and status code. ### Logdash vs Atlassian Statuspage | Feature | Logdash | Statuspage | | ------------------------------ | ------------------------------------------ | ---------------------------------------------------- | | Incident posts and subscribers | Not built in | Email, SMS, Slack, webhook and RSS | | Status from real checks | Built in, every 5 minutes on the free plan | Needs a monitoring tool, the API or email automation | | Public JSON | Yes, no key | Yes, no key | | Custom domain | Pro, or any plan with your own build | Paid plans, from $29 a month | ### When Statuspage is the better pick - You want the GitHub setup: written incident updates and subscribers by email, SMS or Slack. - You want the Stripe setup: maintenance windows announced ahead of time, per component. - Your checks already run in another tool and only the page and the subscriber list are missing. ### What are the best status page examples? GitHub for incident updates, Vercel for regional components, Stripe for a short component list, Linear for honest numbers. All four were live on 2 October 2026. ### What are good SaaS status page examples for a small team? Linear and Stripe. Both list 6 components or fewer, named the way customers think about the product. Cloudflare is a good page for a global network and a poor template for a product with one database. ### Where can I find status page design examples? Open any of the five pages above. Most share one layout: overall status, a row per component, daily history bars and an uptime figure. The Logdash component gives you that layout in your own theme. ### Do status page examples like GitHub use a hosted tool? Yes. GitHub, Vercel, Stripe and Cloudflare run on Atlassian Statuspage and Linear on incident.io. Hosted tools win on incident posts and subscribers, building your own wins on design. ## Keep reading [All status page guides](https://logdash.io/status-page): One page per question, from the status page API to a free page on your own domain. [Status page best practices](https://logdash.io/status-page/best-practices): Host the status page apart from your app, drive it from real checks, list only what customers can tell apart, show uptime over a stated window rounded down, and post a timestamped update at least every hour during an incident. [Status page API](https://logdash.io/status-page/api): Every status page you publish in Logdash is also public JSON at api.logdash.io/v1/status\_pages/:id, with no API key and CORS open to any origin, so you can render it on your own site in your own design. [Open source status page](https://logdash.io/status-page/open-source): Logdash is AGPL-3.0 and its status page client, components and Next.js starter are MIT, but the checks and the data run on hosted Logdash, so if the whole stack must run on your own hardware, Uptime Kuma, Gatus or Upptime are the honest picks. [Uptime monitoring](https://logdash.io/features/monitoring): HTTP checks as often as every 15 seconds. When one fails, Telegram tells you before your users do.