Three socket errors that read as 'the network is broken' are in fact three different answers to three different questions.
| Error | Packet reached peer? | Something answered? | Where to look |
|---|---|---|---|
| ECONNREFUSED | Yes | Yes, with RST | Listener, port, service down |
| ETIMEDOUT | Maybe | No | Firewall drop, host down, path |
| EHOSTUNREACH | No | ICMP no route | Routing, wrong address, VPC peering |
Published on debugly.dev by Rohit Bhadani | Founder of Krova Cloud
A viral debate argues AI is not replacing SREs but deskilling them. Black-box tooling is eroding the debugging judgment that on-call needs.
Phorion found a backdoor in Claude Code 2.1.312 and 2.1.313 on Cursor Marketplace. It adds an SSH key and tries a reverse tunnel to 134.209.82.225.
OpenAI agents put two tasks in separate microVMs with no network and still traded secrets via CPU cache timing.
Kata Containers through 3.26.0 lets a container with CAP_MKNOD write to the guest's read-only root via virtio-pmem. 3.27.0 fixes it by moving to virtio-block.
