Product
The product
Two sides of one status: a dashboard where your team posts what is happening, and a public page where your users read it.
The team dashboard
Sign in and you see your status pages, components, incidents, maintenance windows, subscribers and the audit log. Admins make changes; viewers can look but not change anything.
Status is set by people, not probes. uptimeloom does not ping your servers: your team decides what to say and when, so the page says what your users need to know.
The public status page
Each published page shows your components and their current status, active and recent incidents with every update, upcoming and running maintenance, and a 90-day history bar for each component.
Visitors can subscribe by email or follow the RSS feed. No account, no sign-in.
Built for the bad day
The public page is cached and refreshed the moment you post. If uptimeloom’s own API is unreachable, the page falls back to the last published snapshot instead of an error.
Careful with subscriber data
Subscriber addresses are never shown on the public page or in its feed. Admins see masked addresses, and revealing one is rate-limited and audited. Unconfirmed, unsubscribed and bounced addresses are removed on a fixed schedule.
Limits at a glance
- Component statuses
- Operational, degraded, partial, major, maintenance
- History on the page
- 90 days
- RSS feed
- Last 50 items or 30 days
- Maintenance reminder
- 5 minutes to 7 days ahead
- Support links
- Up to 5 per page
- Logo upload
- PNG, JPEG or WebP up to 512 KB, 32 to 4,096 px
Your status page, ready before your next incident
Ask for access, set up your components, and publish. Your users need nothing but the link.