RESERVER

BGP inherited
Cluster stats
Netblocks8
All fragments 18 blocks across 5 clusters
Cluster ID211731988
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 3 shared RIR contact/maintainer handles
Registry names 1 distinct registrant name across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

5 weekly snapshots · JSON
9 0 netblocks since 2026-07-05
2026-07-05 peak 9 2026-07-19

IP Ranges (8)

⬇ export CSV
CIDR Org name Registry Status Confidence
2a01:4f8:10b:19d::/64 RESERVER RIPE ASSIGNED ● low
2a01:4f8:13a:2066::/64 RESERVER RIPE ASSIGNED ● low
2a01:4f8:172:1885::/64 RESERVER RIPE ASSIGNED ● low
2a01:4f8:200:5099::/64 RESERVER RIPE ASSIGNED ● low
2a01:4f8:231:1bda::/64 RESERVER RIPE ASSIGNED ● low
2a01:4f8:271:3f50::/64 RESERVER RIPE ASSIGNED ● low
2a01:4f8:2191:31d2::/64 RESERVER RIPE ASSIGNED ● low
2a01:4f8:2201:41a2::/64 RESERVER RIPE ASSIGNED ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “RESERVER” — often per-country or per-system registrations of the same brand, occasionally a different organisation sharing the name. Not counted in this organisation's own footprint.
Sub-allocations under carriers
IP blocks an ISP reassigned to a similarly-named customer — decoded from the ISP's own naming convention, not a direct registration.

Network trust

what's this?
RPKI hygiene: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (8 of 8)
No discrepancies found among checked blocks.

NIC Handles

DUMY-RIPE DUMY-RIPE HOS-GUN