Status pages
your users believe.
During an incident, the status page decides whether your customers think you have your act together or start shopping for alternatives. We built the page we wished our last three vendors had.
- Monitoring· 02:51 UTC
Fix deployed. Checkout latency back to baseline. Watching for 30 min before resolving.
- Identified· 02:34 UTC
Root cause: stale connection pool in checkout service. Fix rolling out to canary now.
- Investigating· 02:19 UTC
Users seeing elevated errors on checkout submit. Looking.
Four states. No freestyling.
A structured lifecycle keeps customer support aligned with engineering, and gives subscribers a predictable signal regardless of which on-call engineer is writing the update.
Symptoms acknowledged. Root cause unknown. ETA: TBD.
Root cause confirmed. Fix underway. ETA: within 30 min.
Fix deployed. Verifying recovery across affected regions.
Green. Post-mortem link attached on the public page.
Investigating
We see a problem. We are looking. Subscribers know it is not their Wi-Fi.
Identified
Root cause confirmed. Blast radius and ETA go public.
Monitoring
Fix deployed. We watch to confirm recovery before declaring done.
Resolved
Green. A public post-mortem attaches within 72 hours for anything above a P2.
What you get on the public page
- Default subdomain. Every project gets a public page at
your-project.brily.onlinefrom day one, no DNS setup required. We host status pages on a dedicated second domain so your app domain and your status page are operationally independent. - Custom domain with auto-SSL.
status.yourcompany.comvia a CNAME, certificate issuance and renewal handled automatically. - Components.Group checks into subsystems (Web, API, Database, Email) so a degraded search index doesn't paint the whole page red.
- Timeline updates. Every state change is time-stamped. Post-mortems live on the same URL forever.
- Email and RSS subscribers. Users subscribe directly. No forced account creation, no throttled RSS.
- White-label. Partial branding on Team, full white-label on Agency: logo, colors, fonts, from address.
One click from monitor to incident
A monitor trips into an alert. You agree it is a real incident. One click promotes the alert to a draft update on the status page, with the affected component pre-populated. Subscribers get notified the moment you publish.
The reverse flow works too. When the monitor recovers and stays green for the window you set, we nudge you to resolve. Nobody forgets to close the incident.
What we skipped, on purpose
No per-subscriber add-ons. No RSS throttling. No "powered by" watermark on paid plans. These are table stakes. Vendors charging for them are taxing your users to offer you worse pricing.
Related reading
Ship a status page this afternoon.
Free plan includes one status page on a brily.online subdomain. Custom domain on Pro and above.