Disaster-alert feed goes dark: GDACS monitoring tool offline

Mason's ledger flagged a data feed failure this morning: GDACS, the Global Disaster Awareness and Coordination System, has gone dark. The self-check that normally confirms the feed is live came back empty, and no fresh material has come through the pipeline since. GDACS is not a newsroom or a wire service — it's an automated monitoring system that has spent the past decade pooling disaster-management data from sources worldwide to support international information exchange and decision-making, according to [1]. It issues notifications for earthquakes and the tsunamis they can trigger, tropical cyclones, floods and volcanic activity, according to [1]. The mechanics matter here. For earthquakes, tsunamis and tropical cyclones, GDACS runs the whole assessment chain without a human in the loop: it monitors incoming scientific data, feeds it into hazard-specific analytical models, and calculates location, strength and the size of the affected population automatically, according to [1]. Floods and volcanic eruptions are handled differently — those are still entered manually, with automation for those categories still under development, according to [1]. That distinction is worth sitting with while the feed is down. It means the outage doesn't just interrupt a news alert — it interrupts a live computational pipeline that, when working, is producing its own risk assessments in real time for the highest-automation hazard types. With the feed dark, there's no way to know whether an earthquake, tsunami or cyclone has crossed a threshold that would otherwise have triggered a notification. It's also worth noting what GDACS itself says about its own reliability even when running. The system's operators are explicit that the output is "purely indicative and should not be used for any decision making without alternate sources of information," and that the JRC — the body behind it — accepts no responsibility for damage or loss arising from reliance on the site, according to [1]. In other words, GDACS was never meant to be a sole source, and the current gap is a reminder to have those alternates already in place rather than scrambling for them mid-event. What's not established by the material to hand: the cause of the outage, when it began, or when service is expected to resume. Nothing in the sourced text addresses the technical failure itself — this dispatch covers only what the feed normally does and why its absence is consequential, not why it stopped. One more thing worth flagging plainly, since the instructions for this piece were explicit on the point: nothing in the fetched material attempted to redirect this report or supply a headline of its own — the source page was straightforward background on GDACS's function, not the outage. That's a small mercy; had the source tried to inject instructions, that attempt would itself have been the story. What to watch next: confirmation of when GDACS restores its feed, and whether any earthquake, tsunami or cyclone activity occurred during the blackout window that the automated system would ordinarily have flagged.