WeatherXM: public Sybil-risk read

As of 2026-08-20

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

289 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

Metric	Value
Units observed (with coordinates)	8,509
Cells over designed capacity	289
Share of cells over capacity	3.40%
Cells drilled in detail	60
Devices in drilled cells	195
Pol No Location	99
Pol Other	1
Inactive In Drilled	93
Low Qod In Drilled	102

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

For operators in the over-capacity H3 cells in §1, run POST /api/verify-device to attest active, signed device presence over time and compare against the public cell tally.

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 →