[status] Investigating: The newly reset database cluster (from last night) decided to blow itself up again. I think the extra query load and data from the new monitoring system is making the setup fragile.
Investigating. https://t.co/RXH9yTJSbH
[status] Completed: The monitoring system was paused for about an hour, otherwise the upgrade was uneventful.
https://t.co/GDJEQP9j1u https://t.co/EfVCEnl4xT
[status] Scheduled (Aug 3, 2025, 00:45 UTC): The system will be upgraded to support the new monitoring agent.
https://t.co/e6txcDsp93
https://t.co/MLlr9ORgDS https://t.co/YX3l5ye4YZ
[status] Investigating: A couple days ago I upgraded the older MySQL cluster to a newer one. It worked fine and then ... DIdn't.
The DNS and NTP services continue to operate, but the management website and monitoring is having a comp⦠https://t.co/RO4fKZcPZb
[status] Identified: A fiber cut is affecting the management system kubernetes cluster. The NTP Pool DNS service is unaffected.
https://t.co/jVT66m1Ojd https://t.co/8LrGYNSDyB
[status] Monitoring: The immediate problem was fixed a couple hours ago. A complete fix will be implemented, likely with a brief outage, later today.
A few server operators got erroneously notified by the monitoring system when the s⦠https://t.co/reOcOCyHz5
[status] Investigating: One of the database servers for the central system is malfunctioning.
Serving DNS queries is unaffected. https://t.co/gK8nRUkwj1