Cloudflare Radar: investigate a regional traffic drop
Use the redesigned Radar map as context, then compare it with site logs before changing a campaign. Includes two illustrative decisions and a review template.
Cloudflare redesigned Radar’s homepage on October 23, adding an interactive view of worldwide Internet traffic and outages. Checked October 27; our review date is not the launch date.
Why publishers should care
When visits from one country fall, outside context can help. An Internet-wide signal does not prove that your landing page failed or explain rejected conversions. The following is our editorial diagnostic method, not a tested campaign case.
Check before changing the budget
- Record country, source, page and the start and end of the drop, including time zone. Compare equivalent hours and weekdays; rule out changes to tags and report filters.
- Open Radar and examine available country data for a comparable period. Save the link and observation time. Mark missing time ranges or detail as unknown.
- Check your own site logs: incoming requests, HTTP errors, redirects and form loading. Check hosting status separately. Do not create a payable test conversion.
- Compare visits, enquiries and accepted results separately. Do not apply a regional traffic percentage directly to revenue.
Two illustrative decisions
A regional coincidence. In a hypothetical project, visits from Turkey decline and an independent landing-page availability check also reports errors in the same interval. Preserve both observations and contact the page owner. Temporarily stop the affected placement if unavailability is confirmed; resume after checking the route. The cause still needs investigation.
A site-specific failure. In another hypothetical project, the broader picture is quiet but a form returns an error after a release. Give the developer the URL, time and response code. No Radar signal does not prove the network is healthy; the form error is more direct evidence. Do not scale traffic until it is fixed.
Review template
Copy these fields: country; source/sub-ID; URL; interval and time zone; Radar observation; HTTP errors; last site change; confirmed observation; unknowns; owner; restart condition. Exclude visitor personal information. In AffiliateCore, compare your campaign results using available source labels and statuses; keep external observations separate. This does not announce a Radar integration with our platform.
Primary source: Cloudflare, 23.10.2026.