Captura de la cabecera del artículo. Entrad en el link para leerlo.

Notices where this attachment appears

1. Embed this notice
   Ulises 🌼 ⁂ /I\ (rataunderground@neopaquita.es)'s status on Saturday, 18-Apr-2026 18:24:57 JST Ulises 🌼 ⁂ /I\

   Postmortem del apagón de bluesky.

   "This particular RPC (GetPostRecord) takes a batch of post URIs, and looks them all up in memcached, then scylla upon cache miss. What I had missed is that we deployed a new internal service last week that sent less than three GetPostRecord requests per second, but it did sometimes send batches of 15-20 thousand URIs at a time. Typically, we'd probably be doing between 1-50 post lookups per request.

   Every RPC handler in the data plane does bounded concurrency (i.e. errgroup.SetLimit). However, this endpoint did not! It was the only endpoint in the entire system that was missing it.

   That means that we'd launch 15-20 thousand goroutines for the request, slam the daylights out of memcached by dialing a ton of connections, then close and return them to the OS since our max idle conn pool size was 1000. They would build up in the TCP TIME_WAIT state, and exhaust all available ports."

   TL;DR , se han hecho DDoS a si mismos. Vibecoding too much? : p

   fuente: https://pckt.blog/b/jcalabro/april-2026-outage-post-mortem-219ebg2