Prompt
How do I publish uptime history on a status page?
Latest observation
Oct 27, 2026
OpenAI APIWeb search: off
To publish uptime history on a status page, you usually need to do 3 things:
- Track availability events
- Store historical uptime/downtime data
- Display that data publicly on the status page
Typical approach
1) Monitor your service
Use a monitoring tool or your own checks to record:
- when an incident starts
- when it ends
- how long it lasted
- which service/component was affected
Examples:
- UptimeRobot
- Pingdom
- Better Stack
- Datadog
- Grafana + Prometheus
- custom cron/health checks
2) Keep incident history
Store records like:
- date/time
- incident title
- status: investigating / identified / monitoring / resolved
- root cause
- resolution notes
- duration
- affected components
Also calculate metrics such as:
- uptime percentage over 7/30/90 days
- total downtime
- number of incidents
- mean time to recovery (MTTR)
3) Publish on the status page
Add a public section showing:
- Current status of each service
- Incident history / past incidents
- Uptime chart or percentage history
- Maintenance history if relevant
Common layouts:
- “Incident History” timeline
- “Uptime last 90 days” graph
- per-service availability badges
- monthly uptime summaries
If you’re using a status page platform
Most status page tools support this automatically if you connect monitoring or incidents:
- Statuspage by Atlassian
- Better Stack Status Pages
- Instatus
- Cachet
- Blinkenlights-like self-hosted options
Usually you:
- create a service/component
- connect monitoring
- post incidents or sync from alerts
- enable the public history feed
If you’re building your own
You’ll need:
- a database table for incidents
- a service uptime aggregator
- a frontend component for history
Example fields:
incident_id
service_name
started_at
ended_at
status
summary
details
severity
Best practices
- Be transparent and consistent
- Use clear timestamps and time zones
- Don’t hide incidents once resolved
- Separate planned maintenance from unplanned outages
- Keep historical records searchable
If you want, I can also show you:
- a sample database schema
- a status page HTML layout
- or how to do this with a specific tool like Statuspage, Better Stack, or Cachet