Status pages and incident communication
Tell your users what is happening, before they ask
Publish a status page for your service, post incident updates as you work, and announce maintenance ahead of time. Subscribers get the email; everyone else sees the page.
- WebsiteOperational
- Public APIPartial outage
- Sign-inOperational
- Email deliveryOperational
Identified
Elevated error rates on the Public API. A fix is rolling out.
90 days ago · Today
Everything a status page needs, and no monitoring agent to install
- 01
Branded status pages
A public page per product or service, with your name, accent color, logo and links.
- 02
Components and status
List the parts of your service and show each one’s status at a glance.
- 03
Incidents and updates
Post an incident, mark the affected components and add updates until it is resolved.
- 04
Scheduled maintenance
Announce planned work in your time zone; it starts and ends on schedule.
- 05
Email subscribers
Visitors subscribe on your page and get incident and maintenance emails.
- 06
90-day history and RSS
Show a day-by-day record for every component and an RSS feed of updates.
- 07
Stays up when you are down
A published snapshot keeps your page readable even if uptimeloom’s API is not.
- 08
Team roles and audit log
Admins change things, viewers watch, and every change is recorded.
From first incident to resolved
- Step 1
Add your components
List what your users depend on, such as the website, the API and sign-in, each with a baseline status.
- Step 2
Post an incident
Mark the affected components and their impact. Their status on the page changes at once.
- Step 3
Update until resolved
Move the incident through investigating, identified and monitoring. Choose which updates email your subscribers.
- Step 4
Schedule maintenance
Announce planned work in your time zone with an optional reminder. It starts and ends on schedule.
Your status page, ready before your next incident
Ask for access, set up your components, and publish. Your users need nothing but the link.