Status page subscribers
Let visitors subscribe to your Servor status page by email or webhook to get incident and maintenance updates, and learn how to manage your subscribers.
Subscribers are people (and systems) who want to be told when your status changes. Instead of checking the page, they get an update the moment you post an incident or schedule maintenance. This page covers how visitors subscribe, the channels available, and how you manage the list.
How visitors subscribe
On a public status page, visitors see a Subscribe option. They choose how they want to be notified:
The visitor enters their email address and confirms it. They'll receive a message whenever you publish or update an incident, or schedule maintenance.
A developer subscribes a URL. Servor sends an HTTP request to it on each update — handy for piping status changes into Slack, a bot, or your own systems.
Once subscribed, people are notified automatically for every incident and maintenance update you post — you don't do anything extra when you publish.
Subscribers need to reach the page
Subscribing happens on the status page itself. On a password-protected page, only visitors who have the password can reach the page to subscribe.
What subscribers receive
Subscribers are notified when you:
- Publish a new incident
- Post an update to an existing incident
- Resolve an incident
- Schedule or start maintenance
Notifications carry the incident's title, status and message, so a subscriber gets the context without opening the page. Keep your incident messages clear and jargon-free — they land directly in someone's inbox.
Manage subscribers
From your status page settings — open the page from Status pages in Servor — you can review and manage the subscriber list:
- See who's subscribed and by which channel (email or webhook).
- Remove a subscriber who no longer needs updates or asked to be taken off.
- Visitors can also unsubscribe themselves from a link in any notification email.
Don't confuse subscribers with team notifications
Subscribers are your external audience following your public status. To get your own team alerted when a monitor changes state, use notification channels and alerts instead — those are separate systems.
See also
Every incident and maintenance update reaches your subscribers.
Make it privateUnderstand how password protection affects who can subscribe.
Notification channelsAlert your own team by Email, Slack, Discord or Webhook.
Status badgeShow live status inline for people who'd rather not subscribe.