Who's at the edge, and what we stopped
Reported edge traffic and sampled firewall events — sources, countries, rules and request paths. Collected from Cloudflare's analytics; coverage may be partial. Account-wide, so the cluster picker doesn't steer it.
Reading the last 24 hours from Cloudflare — firewall events, edge traffic and the rules in place…
Cloudflare isn't configured on this instance.
Set OBS_CF_API_TOKEN (a read-only Cloudflare token) — or let it fall back to the
CF_TOKEN the deploy tooling already uses — and this page reads the WAF, DDoS and edge-traffic
analytics for every zone on the account.
Couldn't read Cloudflare just now.
Firewall-event source map
Reported event sources. Node size = sampled event count; arcs indicate geography, not traffic delivered to origin. Click a country to pin the feed.
Our origin (GCP us-central1)
Reported source
Source geography (illustrative)
Traffic & firewall events over 24 hours
Reported edge requests (area, left) and sampled firewall events (bars, right) — different scales. Events include actions other than blocking.
Edge requests / hour
Firewall events / hour
Reported firewall sources
Event counts by the source Cloudflare reported in this window.
Protections in place
The firewall rules guarding these hostnames. Click any rule that fired to see what it is and what it caught.
Top firewall-event sources
Source IPs with the most sampled firewall events. Click one to pin the feed below.
Reported request paths
Hostnames and paths recorded in the returned firewall events; paths alone do not establish intent.
Event source countries
Source countries in sampled firewall events.
Response mix
Status codes served at the edge — the errors are their own signal.
Busiest DNS names
Most-queried hostnames on the account.
Recent firewall events
Returned sample, newest first; check each event's action and the snapshot timestamp.