Using the demo

1. Pick a point. Click anywhere on the US map, or search a city, ZIP, or lat, lon in the search bar. The red pin marks it.
2. Pick who is asking with I am in on the right: your real connection, or a US state (the user is placed at the state's center). Cloudflare answers from the store nearest to that user. The strip shows the header that carries it (X-Tempest-Caller: TX), and curl copies the exact call, header included.
3. Read the strip at the top: lines 1 and 2 are the exact API calls, the same two an AccuWeather client makes (location search for a key, then current conditions for that key; copy or curl); the last line is what on Cloudflare answered it: Worker location, Durable Object, data version, time inside Cloudflare, origin bytes (always 0).
4. Right panel: the current conditions (switch units and language), Served by (the Durable Object, its data center, which tile was read, timings), Compare callers (same point, called as users in eight states plus Europe and Asia), and Origin traffic (traditional GET vs Tempest, with an editable scale calculator).
5. Bottom drawer: the full JSON we built at the edge: AccuWeather's 32 current-conditions fields in AccuWeather's order with nothing added (where the call came from and which Durable Object answered travel in X-Tempest-* headers), the location search result, and Field check against AccuWeather's field list.
6. Share a view: the address bar updates with ?q=…&from=…; the link reopens on the same point and user.

Icon legend

Your location · where the call comes from: your connection, or the center of the state you selected

Durable Object · the Cloudflare data center whose store answered the call

Request path · your location → Durable Object

Conditions location · the point whose weather you asked for

Data tiles · the 247 tiles (128 × 128 grid points) the US dataset is cut into

Tile read · the tile that contained your point

Data