Git Beginner About 20 min +120 XP

Status Page Timeout Fix Is Not on Main

main still carries upstream_timeout_seconds: 2 in its committed deploy/status.yaml.

Take this incident no signup All incidents

Briefing

The status API's upstream health checks give up after two seconds, and the status page has been showing three regions as degraded.

So is everything else from the investigation: a louder log level and a notes file.

The release train leaves at 15:00 and Ravi will only take a commit he can read in one glance.

Someone in the channel suggests committing everything now and cleaning up later.

The fix is yours to find: hints, the recovery checks and the debrief unlock inside the incident.

01
Get paged
The alert fires and the clock starts. Read the page and the briefing.
02
Investigate
Work in a simulated shell with realistic output: logs, configs, services.
03
Fix it
Change the system the way you would in production. Hints are there if you get stuck.
04
Prove it
Automated checks verify the recovery, then the debrief explains what happened.

Free, instant, and it works on your phone. No signup: start as a guest and save your progress later.