Elektrine lite

← Feed

@AkaSci@fosstodon.org

2026-11-13 20:42 UTC

Based on the chart below posted by @dougmadory@infosec.exchange and other hints on the net, here is likely what happened with Microsoft servers - 1. The servers are designed to handle a certain number client conn attempts per second. 2. Normally, the rate of conn attempts is small since once established, most conns hang around for hours or days. 3. But after a server restart, for any reason, all connected clients will time out and retry, creating a surge of conn attempts. (contd) 18/n

Replies (1)

  • @AkaSci@fosstodon.org 2026-11-13 20:49

    4. If the server falls behind in processing, it will queue up incoming conn requests (either at the TCP layer or in the app sw) 5. If the queue allows a large number of conns (bigger is better, right?), the response time will increase 6. Clients will time out and retry conns 7. Soon, the server is processing timed out conns only, doing some SSL layer processing, wasting CPU cycles, dropping the conn.. 8. While the queue contains new conns near the tail 9. Most conns fail. (contd) 19/n

    Open ##5531429