THE QUESTION
Why does the same outage keep recurring?
Say what you meant. Two cards merge only if both authors agree.
closed · back to Actions
Viewing as guest. Enter a handle to join and take part.
Merge duplicates
Only for two cards making the same claim.
why
A merge happens only when both authors consent. Argue meaning in the card's side chat before folding anything.
merged "Action items from incident rev…" → "Post-mortem actions are writte…"
Customers report outages before monitoring does
I mean the pattern over the last two quarters, not a single incident.
cluster 5
Nothing said yet.
Tests that fail intermittently are retried until green
Customers report outages before monitoring does
I mean the pattern over the last two quarters, not a single incident.
cluster 5in focus ↑ · close ✕
The on-call rota has the same two people on it most weeks
cluster 1discuss
Leadership asks for a root cause within the hour, so the first plausible one wins
I mean the pattern over the last two quarters, not a single incident.
Reliability has no budget line of its own
To be precise: this is about the process, not the person on call that night.
cluster 4discuss
Every team has its own logging format
cluster 4discuss
Success is measured in features shipped per quarter
Dependencies are upgraded only when something breaks
Meaning the repeat outages, not the one-off hardware failure in March.
The service map in the wiki is two years old
cluster 6discuss
Deploys go out on Friday afternoons because that is when the sprint ends
Post-mortem actions are written up and then never scheduled
cluster 2discussing (1)
Rollbacks take longer than the outage they are meant to end
To be precise: this is about the process, not the person on call that night.
Runbooks are out of date within a month of being written
To be precise: this is about the process, not the person on call that night.
cluster 6discussing (1)
Migrations are run by hand from a laptop
cluster 3discuss
Post-mortems assign actions to people who were not in the room
Scope: the services this team runs, not the whole platform.
Feature work always outranks reliability work in planning
Scope: the services this team runs, not the whole platform.
There is no time set aside after an incident, so the write-up is done at midnight
Feature flags are never cleaned up, so nobody knows which paths are live
Meaning the repeat outages, not the one-off hardware failure in March.
cluster 2discuss
Config lives in five places and drifts between them
I mean the pattern over the last two quarters, not a single incident.
cluster 3discuss
Incidents are declared late because declaring one feels like blame
Load tests were last run before the customer base doubled
The same three services cause most of the pages
cluster 1discuss
One engineer knows how the payment path actually works
Scope: the services this team runs, not the whole platform.
Error budgets exist on a slide and nowhere else
The staging environment does not resemble production
The incident channel fills with people asking for status instead of giving it
Nobody owns the shared database schema
To be precise: this is about the process, not the person on call that night.
Retries are unbounded, so a slow dependency becomes a flood
Alerts fire so often that on-call mutes them
I mean the pattern over the last two quarters, not a single incident.
cluster 5discuss
Capacity is added after the outage, never before