The map follows changes as they happen

The resource map no longer waits for its next scheduled read. Most connections now tell Firefight when something changes, or keep a log of changes Firefight reads every few minutes, and the map reads that resource again straight away.

Live updates. Vercel, Render, Railway, Northflank, Netlify, GitHub, GitLab, Bitbucket, PlanetScale and Supabase send changes by webhook, which reach the map within about a minute. AWS, Google Cloud, Azure, Cloudflare, Fly.io, Neon and Kubernetes are checked every few minutes. Each connection under Integrations, and the Live updates section beside the map, says whether live updates are on and when the last change arrived, or why they are off.

What changed. The panel beside the map lists what changed in the last 24 hours, such as a deploy, a status that moved, a setting that changed, or something new or gone.

Key checks. Open a resource in Focus to see the first readings worth taking on it, such as a service's error rate and p95 latency, each with what is normal for it over the last week. Run takes the reading now and says how it compares, such as "Now 412 ms, 3.1x the usual high of 133 ms".

Usual log lines. Firefight learns the kinds of line each important resource usually logs, so a line seen during an incident can be told apart from one that was there all week. Only the patterns are kept, never the lines.