Scope
Confirm entity, absolute UTC dates, timezone, filters, metric, and unit match the intended question.
Independent prompt planner · Source checked August 8, 2026
Define the entity, absolute time window, metric, comparison, and strongest allowed conclusion before opening Radar Researcher. The output is a planning aid, not a Radar result.
Prompt outline
For Internet disruption in country, region, ASN, or domain, analyze HTTP traffic and recorded outage events from 2026-08-01 00:00 UTC through 2026-08-08 23:59 UTC. State metric definitions, endpoint parameters, missing data, and retrieval time. Describe the observed pattern; do not infer cause.
Evidence to preserve
This tool does not access Radar, validate data, establish causality, check licensing, or create a permanent archive.
Understand scope, history, traces, charts, sharing, and licensing boundaries.
Separate observations, comparisons, attribution evidence, and unknowns.
Trace the Worker, Durable Object, model, MCP, API, and chart path.
Review imperative and declarative tools, compatibility, and authority.
Evidence gates
Confirm entity, absolute UTC dates, timezone, filters, metric, and unit match the intended question.
Inspect the Radar endpoint, parameters, returned data, chart reference, and retrieval time in the trace.
Use a matched comparison period and identify seasonality, missing observations, or measurement changes.
Keep observed patterns separate from cause; corroborate with routing, operator, official, local, and expert evidence.
Preserve permitted evidence outside a shared Researcher link when retention beyond its 30-day expiry is required.
Check current Radar API terms, CC BY-NC 4.0 attribution, privacy policy, and the intended commercial context.
Official references: Radar Researcher launch and Radar API documentation. Verify current beta access, datasets, definitions, licensing, links, and limits before use.