Observe one browser-to-Cloudflare network measurement

A bounded signal timeline

BROWSER → NETWORK PATH → CLOUDFLARE

• HEAD timing samples
• download transfer
• upload transfer
• Result = one moment on this route

The measurement chain is explicit

The editor does not test a subscription plan or a named city server. It asks the current browser to make a small set of requests to Cloudflare, then displays the timing and transfer figures observed in that run.

1. 1. Sample HTTP response timing

   The browser sends 10 HEAD requests to the Cloudflare trace endpoint. Successful samples are trimmed when enough are available, then shown as ping and jitter figures.

2. 2. Plan the transfer size

   A 1 MB Cloudflare download probe estimates a transfer size for the next stage. The plan remains bounded rather than expanding with the connection.

3. 3. Transfer and record the run

   The browser measures a Cloudflare download and upload, displays the resulting Mbps figures, and can keep up to 10 recent records in this browser’s local storage.

Published transfer boundaries

These limits describe the current editor behavior. They help put the visible figures in context and keep one run from becoming an open-ended transfer.

• 10 — HTTP HEAD timing samples
• 1 MB — initial download planning probe
• 50 MB — maximum download transfer
• 20 MB — maximum upload transfer

Browser and endpoint context belongs with the number

A browser measurement includes more than the access connection. Device activity, browser behavior, Wi-Fi or cable conditions, the route taken at that time, and the selected Cloudflare endpoint all contribute to what is observed.

• Cloudflare uses the network endpoint selected by the current routing; the editor does not offer a fixed city choice.
• Connection details may be requested from ipapi.co; when that request does not return data, the Cloudflare trace can provide an IP-only fallback.
• The history chart reads records stored by this browser, not a cross-device history.

Read the result as a moment, not a promise

Download, upload, ping, and jitter are observations from one browser session to Cloudflare. A later run can differ because the route and conditions can differ. Compare runs made in similar circumstances and note the endpoint context shown by the editor.

• Use ping and jitter as HTTP response-timing observations for this endpoint, not an ICMP diagnostic.
• Use download and upload figures as transfer observations from this browser to Cloudflare.
• Repeat after changing a relevant condition, then compare the recorded time, figures, and endpoint context.

Continue with the network context

Use the adjacent tools when you need a different view of the current browser connection or a specific public hostname.

• Ping Test

  Observe HTTP response timing for a submitted public URL.

• What Is My IP

  View the IP information the browser-facing lookup returns.

• DNS Lookup

  Inspect returned DNS records for a domain name.

Questions about this browser measurement