Learn
What is a status page?
A status page is a web page, usually public, that shows the current health of a company's services, their recent uptime history and any incidents or scheduled maintenance in progress. It is the single place customers and colleagues look when something seems wrong, replacing a flood of support tickets with one timely, honest answer.
What does a status page show?
Most status pages follow a similar layout. At the top is an overall summary such as “All systems operational” or a banner for the current incident. Below it is a list of components, the customer-facing names for the parts of the product, each with a current state and often a bar showing uptime for the last 7, 30 or 90 days. Further down sits the incident history: timestamped updates for past outages and any maintenance that has been announced.
Components deliberately use customer language rather than internal names. A customer does not need to know that a Kubernetes node pool is unhealthy; they need to know whether “Website”, “API” or “Checkout” is working. Grouping components, for example Customer facing versus Infrastructure, keeps a longer list readable.
Why publish a status page?
The first reason is support load. During an outage, every minute that customers cannot find an answer turns into tickets, chat messages and social posts, all asking the same question. A status page that already says “We are aware and investigating” answers them before they ask, and email subscribers are told directly when things change.
The second reason is trust. A public uptime history is a commitment: it shows that you measure availability, that you are willing to be judged on it, and that incidents are explained rather than hidden. Prospective customers and procurement teams increasingly look for one before signing a contract. A status page also gives your own team a shared view of what customers currently see, which reduces confusion during an incident.
Automatic status versus written updates
Component status can come from two sources. Automatic status is driven by uptime monitors: when a monitor behind a component is confirmed down, the component turns red and an incident appears without anyone touching the page. This is fast and never forgets, but it cannot explain what happened or what you are doing about it.
Written updates are posted by a person and usually move through a standard lifecycle: Investigating, Identified, Monitoring and Resolved. Each step is timestamped and sent to subscribers. The best pages combine both. Monitors keep the page truthful even at three in the morning, and humans add context when there is something worth saying. Scheduled maintenance is announced ahead of time so planned work is not mistaken for an outage.
Public, private and branded pages
Not every status page is for the open internet. Internal tools and B2B platforms often publish a page protected by a password, or hidden from search engines, so that only customers and staff can see it. Branding matters either way: a page carrying your logo, colours and a custom domain such as status.yourcompany.com is recognisably yours and is easier to find in a hurry.
A status page should be hosted independently from the services it describes. If it lives on the same servers, it goes down with them, which is exactly the moment it is needed.
How MoniterMySite handles this
Every MoniterMySite plan includes at least one status page; the free Starter plan has one, Launch has three, Growth has twenty and Summit is unlimited. Components map to monitors and can be grouped, with 7, 30 or 90-day uptime bars, uptime percentage, response times and incident reasons shown as you choose. Visitors can subscribe by email and receive every announcement. Custom domains are available on Launch and above, password protection on Growth and above, and any page can be hidden from search engines. Incidents move through Investigating, Identified, Monitoring and Resolved, and maintenance announcements change to In progress and Completed automatically.
Frequently asked questions
Should a small company have a status page?
Yes, if anyone outside the team depends on the service. A status page costs little to set up, and the first incident where customers find the answer themselves instead of emailing you pays for the effort.
What should the components on a status page be?
The things a customer would name when describing a problem: Website, API, Dashboard, Checkout, Email delivery. Keep the list short and group it if it grows. Internal infrastructure can live in its own group or stay off the page entirely.
Is it bad to show a low uptime number publicly?
A visible dip with an honest incident write-up builds more trust than a page that is always green. Customers already know when you were down; the page shows whether you noticed and how you responded.
How do subscribers get notified?
Visitors enter an email address, confirm with one click and then receive each incident update and maintenance announcement. Every email includes an unsubscribe link.
Keep reading
See it in practice.
Add your first monitor on the free plan in under a minute. Multi-region confirmation is included from the Launch plan.