Incidents reported on status page for d.cx administration team https://status.dg.cx/ en https://status.dg.cx/incident/775689 Fri, 28 Nov 2025 22:30:16 -0000 https://status.dg.cx/incident/775689#f25512087879d35b9a652972354428d42fff740cc1edb922c81f9012909781a6 Prometheus (hm) recovered. https://status.dg.cx/incident/775689 Fri, 28 Nov 2025 07:12:47 -0000 https://status.dg.cx/incident/775689#ab8269a3b6c56d4d329878eaaf56b9246572d5dae6f6b34c258434a1f6f9c3fd Prometheus (hm) went down. https://status.dg.cx/incident/775564 Fri, 28 Nov 2025 02:27:32 -0000 https://status.dg.cx/incident/775564#7b462a1d7ffa944bcc07fe2852c90ab9e6b14e3a0034365f7b2f80dfd737bebf dg.cx recovered. https://status.dg.cx/incident/775564 Fri, 28 Nov 2025 00:52:00 -0000 https://status.dg.cx/incident/775564#1cdac6f22f34dace619ef69b62cb9fca782db584188d03b3027b3ee4a95eb482 I migrated the VM to a different (newly built) proxmox host. Previously the cluster was purely 12th gen Intel, added a new 10th gen intel node. Because of different CPU feature support, I think a critical Go process crashed, but need to add more logging to know for sure. https://status.dg.cx/incident/772765 Sun, 23 Nov 2025 11:39:00 -0000 https://status.dg.cx/incident/772765#df18b8609922f1accb196b64ecd4417d976f6d49fb128091e55edefcfa734484 Resolved https://status.dg.cx/incident/772765 Sun, 23 Nov 2025 05:35:00 -0000 https://status.dg.cx/incident/772765#c280c968efc5d8d3c8eb760bea07056015a268e397792754fc5c11a32fa8e174 ip.wtf was partially down due to an app bug.