WaVe ConnecT

BGP inherited
Cluster stats
Netblocks4
Cluster ID207728340
RegistryPEERINGDB
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 1 shared RIR contact/maintainer handle
Registry names 1 distinct registrant name across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

3 weekly snapshots · JSON
19 +1 netblocks since 2026-07-05
2026-07-05 peak 19 2026-07-12

IP Ranges (4)

⬇ export CSV
CIDR Org name Registry Status Confidence
187.16.212.49/32 WaVe ConnecT PEERINGDB ASSIGNED ● high
187.16.213.30/32 WaVe ConnecT PEERINGDB ASSIGNED ● high
2001:12f8::212:49/128 WaVe ConnecT PEERINGDB ASSIGNED ● high
2001:12f8::213:30/128 WaVe ConnecT PEERINGDB ASSIGNED ● high

Possibly related to this organisation

what's this?
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 (4 of 4)
No discrepancies found among checked blocks.

NIC Handles

AS270425