{
  "id": 20317424,
  "title": "My server didn't go down. Chasing the false alarm hardened everything else.",
  "url": "https://urgent.news/2026/11/16/my-server-didnt-go-down-chasing-the-false-alarm-hardened-everything",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-11-16T19:32:13.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/lfariaus/my-server-didnt-go-down-chasing-the-false-alarm-hardened-everything-else-feo"
  },
  "original_language": "en",
  "account": "On November 7, Discord informed the reporter that one of the containers was down: backend_api. The reporter opened the site on their phone, and it didn't load. However, upon SSHing into the server and checking the logs, they discovered that every container had been running the whole time. The issue turned out to be a false alarm caused by the reporter's 4G connection dropping out. What initially seemed like a five-minute investigation expanded into two days and 13 pull requests, as each fix exposed the next issue that had gone unnoticed. This post chronicles the problem, how each fix was verified on the live server, and the surprising insights gained along the way.",
  "summary": "On November 7, Discord pinged me: 🔴 Container(s) Down: backend_api. I opened my site on my phone and it didn't load. That looked like proof. It wasn't. I SSHed into the droplet and read the logs. Every container had been up the whole time. My phone's 4G had dropped out, and the alert was false. That should have been a five-minute investigation, but it turned into two days and 13 pull requests,…",
  "key_points": [],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}