A public status page is a read-only page at /status/your-handle/your-slug that shows the current health of your service to anyone — no login required. Use it to keep users informed during incidents without them flooding your support inbox.
Creating a status page
- Open a monitor's settings in the dashboard
- Scroll to the Status Page section
- Enter a short, memorable slug (e.g. my-app or acme-api)
- Click Save
Your status page is immediately live at /status/your-handle/your-slug. No additional setup is required.
Choosing a good slug
Your slug becomes part of the public URL, so make it short and recognizable — especially important when users are frustrated during an incident and trying to find the page quickly.
- Use 1–2 words: your product or company name
- Lowercase letters and hyphens only
- Avoid numbers, version strings, and underscores
- Match it to your main domain or product name
Good examples: acme, my-app, build-status. Bad examples: production-v2-monitoring, 1234abcd.
What users see on the status page
- Current monitor status (UP or DOWN) with a color indicator
- Response time for the most recent check
- uptime history
- Recent incidents with start time, end time, and whether they're resolved
Automatic updates
The status page updates automatically as your monitor state changes. When UptimeWiz confirms a service is down, the status page reflects that immediately. When it recovers, the page updates to show UP. You don't need to manually update anything.
Sharing your status page
Add the URL to your documentation, support auto-responder, application error pages, and any places customers might look for service health information. The goal is to make it impossible not to find during an incident.
Every customer-facing service should have a public status page. It reduces support load during incidents and shows customers you take reliability seriously.