GETKINETIK BUREAU

Public-data read · neutral bureau

Over-capacity read

WeatherXM: public Sybil-risk read

As of 2026-06-21

Public source: WeatherXM public cells API · no auth, no internal data

286 cells exceed designed capacity — §1 lists H3 indices + map centers for your ops queue.

This is an independent read of WeatherXM's own public data by the GETKINETIK bureau. We publish what the public endpoint returns — covering map cells reporting more devices than they can physically hold — so anyone can reproduce it. We hold no token in any network we read and take no equity in graded networks.

The numbers

MetricValue
Units observed (with coordinates)8,501
Cells over designed capacity287
Share of cells over capacity3.38%
Cells drilled in detail60
Devices in drilled cells187
Pol No Location88
Pol Other4
Inactive In Drilled105
Low Qod In Drilled101

What this means — and what it doesn't

Worth a look

Map cells that list more devices than the area can physically contain. The bureau surfaces the count and the cell index so the question can be asked from public data alone.

Not an accusation

This is not proof of fake devices. Over-capacity can come from registry double-counting or expected reward-zone behavior. Only the operator can settle the cause — the bureau just makes the count checkable.

How to confirm it

Reproduce the read from the public source above and cross-check the flagged entries against the registry.

For an authoritative per-device grade — hardware-rooted signature, chain age, tamper flags — a network or operator can POST a Proof of Origin to the verify-device API.

Go deeper

Full methodology & row-level table → Verify a device → Request the full table →

Other networks the bureau reads

GeodnetHivemapperHelium IoTHelium Mobile