Radar data is partially unavailable
This dashboard never substitutes missing values with estimates — unavailable metrics are shown as “no data” until the Cloudflare Radar API returns them.
● Loading… --/100
Netnux Stability Index — a weighted score computed from live Cloudflare Radar inputs (latency, bandwidth, DNS response time, traffic volatility). See methodology.
until the next minute-aligned refresh
Confirmed network events
Cloudflare outage annotations affecting Iran · last 3 days
Traffic anomalies & BGP routing
Radar anomaly detection and routing-table statistics for Iran
A zero anomaly count means Cloudflare Radar reported no anomalies for Iran in the window — not an absence of measurement.
L7 attack mitigation mix
Share of mitigated L7 DDoS traffic by Cloudflare product · Iran
Latency & DNS response time
Median (p50) round-trip latency and DNS resolution, milliseconds
Bandwidth
Median (p50) throughput per internet user, Mbps
Internet traffic change
Cloudflare netflows vs. the equivalent previous period, weekday-aligned (%)
DDoS activity — L3/4 & L7
Attack traffic targeting, originating from and carried within Iran
Requests served over encrypted TLS
Requests using the HTTP/3 transport
Requests arriving over IPv6
Requests classified as bot-generated
DNS responses validating DNSSEC
Most popular domains
Top domains by requests from Iran · Cloudflare Radar ranking
Major autonomous systems in Iran
Top 10 ASNs ranked by estimated internet user population · Radar Entities API
| ASN | Operator | Country | Est. users | Website |
|---|---|---|---|---|
| loading… | ||||
Data & methodology
Every number on this page is fetched live from the official Cloudflare Radar API and cached on Cloudflare’s edge for 60 seconds. Nothing is mocked, modeled or filled in: when a dataset is temporarily unavailable the dashboard shows “no data”.
Internet quality (IQI)
Median (p25/p50/p75) latency, bandwidth and DNS response time from /radar/quality/iqi/summary and their timelines from /radar/quality/iqi/timeseries_groups, filtered to location=IR.
Traffic
Internet traffic change from /radar/netflows/timeseries with normalization=PERCENTAGE_CHANGE, which Cloudflare only accepts alongside a comparison series. Two positional series are therefore requested for location=IR: the selected window (1d/7d/30d) and its control (<range>control) — the equivalent previous period, shifted back by whole weeks so weekdays stay aligned. The plotted values are the percentage change returned by Cloudflare; if the API returns both windows unnormalized instead, the change is computed pointwise from those two live series (both share one response-wide scale, so the ratio is exact). Points with a zero or missing control value have no defined percentage change and are shown as gaps, never estimated.
Attacks
L3/4 DDoS attack-byte series (/radar/attacks/layer3/timeseries, directions TARGET and ORIGIN) and L7 HTTP attack traffic (/radar/attacks/layer7/timeseries), plus attack vectors and mitigation-product breakdowns.
Events & routing
Confirmed outages from /radar/annotations/outages?location=IR, anomaly counts from /radar/traffic_anomalies/locations and routing-table statistics from /radar/bgp/routes/stats?location=IR.
Netnux Stability Index
Computed on the server from the live inputs above — latency score (100 at ≤40 ms median RTT, linear to 0 at 400 ms), bandwidth score (logarithmic, 0 at 1 Mbps to 100 at ≥100 Mbps), DNS score (100 at ≤10 ms, linear to 0 at 300 ms) and volatility score (100 at 0% mean absolute traffic change, linear to 0 at 25%), weighted 0.35 / 0.25 / 0.15 / 0.25. Unavailable inputs are dropped and the remaining weights re-normalized. This index is a Netnux derivation, not a Cloudflare metric.