StoryFirst seen
A single database node failure went unnoticed because the three-region setup lacked zonal resilience.
Everything it touches
1 names 1 voices 1 source posts
The story’s neighborhood
Explore the graph, or choose a connection below.
Follow the evidence
This brief comes from Tech Twitter’s edited headlines. The posts below are the sources grouped with the story; statements in them belong to their authors.
Revolut shared the postmortem of their global cards outage of 5 hours. Some interesting (alarming?) notes: 1. They had no monitoring on database nodes going down (!!) 2. Across 3 regions, they ran 5 nodes, with #1. So a single node going down meant no zonal resillience (cont'd)Read original on X
Revolut's five-hour cards outage traced to missing database monitoring
Revolut's five-hour cards outage traced to missing database monitoring
Revolut's five-hour cards outage traced to missing database monitoring
Revolut's five-hour cards outage traced to missing database monitoring
Revolut's five-hour cards outage blamed on missing database monitoring
Revolut's five-hour cards outage traced to missing database monitoring
Shared connections
The outage suggests Revolut lacked failover to another zone, and Revolut has promised a postmortem.