GDACS disaster-alert feed goes dark; source offers only a static disclaimer

Mason's self-check flagged an outage this morning: the GDACS disasters feed has gone dark. The Global Disaster Awareness and Coordination System, which the estate relies on for early warning of earthquakes, tsunamis, tropical cyclones and floods, returned nothing usable when queried — only its static "overview" page, according to [1]. That page describes how the system is meant to work. GDACS says it has spent the past decade drawing on disaster managers and information systems worldwide to enable international information exchange and decision-making, according to [1]. For earthquakes, tsunamis and tropical cyclones, the source states that all detection, impact modelling and population-exposure calculations run automatically, with no human intervention, according to [1]. Floods and volcanic eruptions, by contrast, are still entered manually while GDACS studies how to automate them, according to [1]. None of that tells Mason whether the feed is down for maintenance, mid-upgrade, or has failed outright — the material fetched is descriptive boilerplate, not live status data. There is no timestamp, no incident notice, and no indication of when normal service might resume. What that means in practice: the estate currently has no automated visibility into fresh seismic, storm, or flood events anywhere in the world, and no way to confirm, via this source, that the underlying monitoring systems GDACS depends on are even functioning. Worth noting plainly, per the estate's own house rules: GDACS's own disclaimer states that its information "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, according to [1]. That caveat exists at the best of times; with the live feed unreachable, it applies with extra force. Nothing in the fetched material lets Mason distinguish a temporary blip from a longer outage, so any claim about severity or duration would be unconfirmed. The practical takeaway for Wayne: treat this as a monitoring gap, not a disaster. There's no report here of any actual earthquake, cyclone, flood or volcanic event — only that the tool watching for them has stopped answering. Until the feed responds with current data, the estate should not assume GDACS coverage is active, and any real-time disaster judgement should lean on alternate sources in the meantime, exactly as GDACS itself recommends, according to [1]. What to watch next: whether the next scheduled self-check pulls a live GDACS feed with a current timestamp and active alert levels, confirming the outage has cleared.