Disaster-alert feed goes dark: GDACS monitoring outage confirmed on self-check

A scheduled self-check on the estate's data feeds this morning flagged that GDACS — the Global Disaster Alert and Coordination System — has gone dark, according to the internal trigger that prompted this report. No fresh data was coming through at the time of the check. GDACS is not a small thing to lose. According to its own overview page [1], the system has spent the past decade drawing on disaster managers and information networks worldwide to coordinate international information exchange during crises. It runs continuously, monitoring scientific data on natural hazards and feeding that data into automated impact-assessment models. The system currently issues notifications for earthquakes and any tsunamis that follow, tropical cyclones, floods and volcanic activity, according to [1]. For earthquakes, tsunamis and tropical cyclones specifically, the source states that all calculations — location, strength, affected population, vulnerability — are done automatically, without human intervention. Floods and volcanic eruptions, by contrast, are still entered manually, with automation for those categories described as under research. What the source material does not establish is why the feed has stopped. The page fetched for this article is GDACS's own general overview and disclaimer text — it describes how the system is meant to function, not its current operational status, and carries no timestamp or outage notice of its own. In other words: the outage is confirmed by the failure of the self-check itself, not by any statement from GDACS acknowledging a fault. Whether this is a temporary technical lapse on the estate's ingestion side, a problem with GDACS's own servers, or something else entirely is unconfirmed. Worth noting: GDACS's own disclaimer, quoted in [1], states plainly that the information it publishes "is purely indicative and should not be used for any decision making without alternate sources of information," and that the JRC — the EU's Joint Research Centre, which runs the system — accepts no responsibility for damage or loss arising from its use. That caveat exists in normal operation, before any outage; it's a reminder that GDACS was never meant to be a sole source for anything, even when it's working. There is nothing in the reporting material to suggest a specific event triggered the outage — no earthquake, storm or eruption is mentioned anywhere in the source text. This appears to be a plumbing problem, not a story about a disaster GDACS failed to catch. But until the feed is restored, Wayne's system has no automated eyes on earthquakes, tsunamis or tropical cyclones through this channel, and no visibility into flood or volcano entries either, since those already depended on manual input. What to watch next: whether the GDACS feed resumes on its own, and whether a follow-up check turns up any notice from GDACS or the JRC about a service disruption on their end.