whatsmyip.fyi
Tools

Quarterly datasets

Four aggregate measurements taken from the traffic this site already handles, published every quarter as CSV under a Creative Commons Attribution licence. No dataset contains an IP address, a session identifier, or anything that can be traced to one visitor.

Status: first release planned. Nothing is published yet. The collection code and the aggregation thresholds are being built alongside the tools that feed them. The first release is planned for Q1 2027, covering the quarter that ends 31 December 2026. Each dataset below states what it will measure and how, so the method is on the record before the numbers are.

What will be published

  1. IPv6 share by country and ASN

    Planned

    How many real connections can actually carry IPv6, rather than how many networks advertise it?

    Measures
    The share of homepage requests where the dual-stack probe completed over IPv6, split by country and by autonomous system.
    Method
    The homepage loads one image from an IPv4-only hostname and one from an IPv6-only hostname. Each result is counted once per session as a triple of country, ASN and outcome. No address is stored.
    Columns
    quarter, country, asn, as_name, sessions, v6_capable, v6_preferred

  2. Carrier-grade NAT share by ASN

    Planned

    Which access networks put their subscribers behind shared address space, and how consistently?

    Measures
    The share of sessions whose public address falls in 100.64.0.0/10, or whose reported client port range and RTT profile match a CGNAT gateway, per autonomous system.
    Method
    Derived from the address family and prefix of the request as seen at the edge, aggregated per ASN. RFC 6598 space is counted directly; other signals are reported separately and never merged into the headline number.
    Columns
    quarter, asn, as_name, country, sessions, rfc6598_share, inferred_share

  3. Leak rates by browser and leak type

    Planned

    When a visitor is behind a tunnel, which browser leaks, and which check catches it?

    Measures
    For sessions that ran the full VPN check, the rate at which WebRTC, DNS or IPv6 exposed a path outside the tunnel, split by browser engine and major version.
    Method
    Counted only from sessions that ran every check to completion. A leak is recorded when a check returns an address or resolver outside the network the HTTP request came from. The rubric is published with the data.
    Columns
    quarter, engine, engine_major, sessions, webrtc_leak, dns_leak, ipv6_leak, any_leak

  4. Resolver market share

    Planned

    Which recursive resolvers actually answer for people, as opposed to which ones people say they use?

    Measures
    The share of DNS leak tests answered by each resolver operator, split by country, with ISP resolvers grouped by ASN.
    Method
    Each leak test issues a unique subdomain under our own authoritative zone. The resolver that queries us is attributed by address to an operator using RDAP. Query names are single-use and expire in ten minutes.
    Columns
    quarter, country, resolver_operator, resolver_asn, queries, share

How the numbers are made

Every figure is a count of sessions, never of people and never of addresses. A session contributes at most one row to at most one bucket. A full address is never written down: the country, the network number and the check outcome are resolved while the request is being answered, a counter is incremented, and the rest is discarded inside that same request.

Buckets with fewer than 500 sessions in a quarter are suppressed rather than published, because a small bucket in a small country is not anonymous. Suppressed buckets are reported as a count of suppressed rows so the totals still reconcile.

Each release carries the rubric that produced it. When a rubric changes, the old series is not rewritten; a new column is added and the change is described in the release note. Comparisons across a rubric change are marked in the CSV itself.

Everything is licensed CC BY 4.0. Cite it as "whatsmyip.fyi quarterly network datasets" with the quarter and a link. If you find an error, tell us and the correction goes in the next release with a note, not a silent edit.

Where the measurements come from