Unofficial Status Page
Your status page repainted by customers; count the red days you never declared.
The job
Shows support and incident leaders a 90-day status page rebuilt from customers' public posts, beside the official one. Counts bad days the company never declared, flags the next live, and holds the team to a rule, set in advance, for how fast to declare.
The moment
The official status page shows 90 green days and 99.98% uptime. Beside it, a version rebuilt from what customers post publicly shows 6 red days and 11 amber.
A support lead taps one Thursday and replays it. From 19:40, 212 merchant posts pile up saying the store has stopped and checkout is down, while the official banner still says "All systems operational".
The first official reply comes at 22:10, two and a half hours later. Every rival was fine that night, so it wasn't the card network.
The VP of Support marks three days as not declared, opens the drafted apology and asks who owns the status page.
What it does
- Tick a red day declared or undeclared
- Pre-register the declare rule and the undeclared tally
- Draft a retroactive incident note
- Send the incident manager the timeline and verbatims
- Hand the night's posts to support
- Log a red day to a shared history
- Save a dated copy of the official status page
What you see
A faithful status page (component rows, 90 daily bars, uptime) painted by public posts, with rival rows, a Time Machine replay of any red night, and a live Street Now wall.
What it moves
Bad days customers saw that were never declared, per quarter, and the median minutes from customers' posts turning red to the first official word, against the rule set in advance.
Built for
- CX leaders & VoC
