Skip to content
Practice

SEV-1 simulationDatabases · Real outage · Reconstructed data · 15–20 minutes

Incident #016 — 2,147,483,647

Customer impact

The app is effectively read-only. Nearly every action fails because one very busy table can no longer accept writes.

SignalCurrent value
Appread-only in effect
Writes to the tracking tablefailing
Highest ID in that table2,147,483,647
Database healthok
Readsworking

Your task

You were paged at 07:21. Work out why writes are failing, using the service map, metrics, logs, traces and recent changes. Choose how to get writes back safely, then name the cause and the permanent fix.

07:25Impact continuing · +0 minabout 0 thousand blocked actions lost since you joined

Investigate · each first look costs 1 simulated minutes

What do you want to look at?

Nothing open yet. Pick a view above. You do not have to open them all before you act.

Step 1 · mitigate · you can act at any time

Customers can read but not write. What do you do?