Prompt
How do I make a status page for a digital service?
Latest observation
A good status page is simple, trustworthy, and easy to update. Its job is to tell users:
- whether the service is working,
- what’s broken,
- what you’re doing about it,
- and when to expect the next update.
Core pieces of a status page
1. Overall service health
Show a clear high-level state, such as:
- Operational
- Partial outage
- Major outage
- Maintenance
Use color sparingly:
- Green = normal
- Yellow/orange = degraded
- Red = outage
- Blue/gray = maintenance or informational
2. Component list
Break the service into parts users care about, for example:
- API
- Web app
- Mobile app
- Payments
- Authentication
- Notifications
For each component, show its status separately so users can see what’s affected.
3. Incident banner
If something is wrong, show:
- what happened,
- when it started,
- current impact,
- workaround if any,
- next update time.
Keep it plain and factual.
4. Maintenance notices
For planned work, show:
- start/end time,
- affected components,
- expected impact,
- timezone,
- whether downtime is expected.
5. Incident history
Include recent incidents and maintenance events so users can see reliability over time.
6. Subscription/notifications
Let users subscribe to:
- email updates,
- SMS,
- RSS/Atom,
- webhook, if relevant.
This reduces support requests.
What to include in the content
Use short, direct language:
- “We are investigating elevated error rates on the API.”
- “Users may be unable to log in.”
- “Our team is working on a fix.”
- “Next update in 30 minutes.”
Avoid vague wording like:
- “Experiencing issues”
- “Some users may be affected” unless you can be more specific
- jargon or internal system names
Recommended structure
A typical status page layout:
-
Header
- Service name/logo
- Current overall status
-
Current incident/maintenance section
- Active incidents
- Scheduled maintenance
-
Component status table
- Component name
- Current status
- Short note
-
Incident history
- Past incidents with timestamps
-
Subscription options
- Get updates
-
Footer
- Contact/support links
- Last updated time
- Status page source or trust info
Technical options
Option 1: Use a hosted status page service
Good if you want speed and reliability:
- Statuspage
- Better Stack
- Atlassian Statuspage
- Cachet-hosted providers
- Instatus
Pros:
- fast setup
- incident workflow built in
- subscriptions and notifications included
Cons:
- recurring cost
- less customization
Option 2: Build your own
Good if you want full control.
Typical stack:
- Frontend: static site or simple web app
- Backend: admin dashboard for posting incidents
- Data source: database or config files
- Uptime checks: monitor your endpoints automatically
- Notifications: email/SMS via provider
- Hosting: CDN or static hosting for availability
Best practice: keep the public page separate from your main app so it stays accessible even during outages.
Good practices
- Make the page accessible even if the main service is down.
- Use a separate domain if possible, like
status.example.com. - Update quickly and regularly during incidents.
- Keep timestamps in UTC or clearly labeled local time.
- Be honest; don’t minimize outages.
- Don’t post sensitive internal details.
- Make the page mobile-friendly and accessible.
- Keep the wording consistent across incidents.
A simple example
Overall status: Partial outage
Affected components:
- API — Degraded performance
- Web app — Operational
- Payments — Investigating
Incident update:
We are investigating elevated error rates affecting the API. Some users may experience slow responses or failed requests. We identified the issue in our database layer and are applying a fix. Next update in 30 minutes.
If you want to build one quickly
Start with:
- a simple public page,
- a component list,
- a manual incident editor,
- automated uptime checks,
- email subscriptions.
If you want, I can also help you with:
- a design mockup,
- a database schema,
- a React/HTML template,
- or a step-by-step build plan for your stack.