Pacific event watch
Track strong earthquakes, tsunami activity, and related follow-on signals without leaving the same watch surface.
Show new M6+ earthquakes around Japan and any matching tsunami events.
Ops
Watch one place.
Watch one place.
See what changed.
Fresh evidence for live watch: focus on a country, region, or event, see what changed, and keep the source trail visible.
Starter watches
Start with one live watch, either as a watch idea or a direct feed entry point. Keep the scope narrow and let the watch deepen from there.
Regional hazard watch
Keep one region in view and watch for multiple live hazard types as conditions change.
Watch the Gulf Coast for new hurricanes and active wildfires.
Signal overlap watch
Monitor different feed families together when the operational picture spans markets, events, and geography.
Watch Indonesia for volcanic activity and large moves in the rupiah.
Live
Hazard feed
Earthquakes now
Start with a live seismic watch and keep the question focused on what is active now, not broad history.
Open in Ops › Alert AlertsUS severe alert watch
Open the weather-alert posture directly when the operational question is where warnings are active right now.
Open in Ops › Track StormsAtlantic hurricane watch
Use a live storm track as the entry point when you want one region, one season, and one changing situation.
Open in Ops ›
Soon
Climate
Heat and climate watch
Upcoming watch posture for heat anomalies, drought stress, and larger climate signals treated as live conditions instead of a static map.
How Ops works
Ops chat is snapshot-first. It starts from what is active now, then reads the recent watch history behind that state. This is the lane for "what changed?", "what is new?", and "which source says what?"
See the current state first
Each watch begins from the live feed snapshot: active alerts, current storms, current seismic activity, or the latest market move that matters operationally.
What is active right now in this watch?
Ask against the last ~72 hours
Ops can look back through the recent retained window to explain what changed, what escalated, what faded, and how the current state developed over the last few days.
How did this situation change over the last 72 hours?
Use Explore for older history
If the question is broader or older than the live window, move to Explore. Explore is the better lane for deeper historical context, larger comparisons, playback, and canonical pack history.
How does this compare to the last 5 years?
More feeds, same watch model
Ops is not limited to the starter watches. Earthquakes, currency, tsunamis, volcanoes, wildfires, and hurricanes all use the same watch posture: one region or event, live snapshots first, recent history as support, and a clean handoff to Explore when the question becomes more historical.
Before you start a watch
How fresh is the data?
Live collectors write into the same packs the rest of DaedalMap reads, so a watch shows the latest collected state rather than a separate real-time copy. Each feed page lists its own collection cadence.
Will it tell me where an alert actually applies?
Alert and event geometry is compared against maintained places by measured overlap. A storm track or alert polygon reports the places it intersects instead of guessing from a name or a center point.
How far back can I ask?
Ops answers from the live snapshot and the recent retained window, roughly the last 72 hours. Older comparisons belong in Explore, which reads the full pack history.
What does a watch cost?
Opening Ops and browsing feeds is free. Paid feeds and larger agent or bulk workloads are priced separately, and the engine is open source if you would rather run it yourself. See pricing.