NO-T7D-10030

BGP inherited
Cluster stats
Netblocks6
All fragments 50 blocks across 34 clusters
Cluster ID210514247
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

4 weekly snapshots · JSON
6 0 netblocks since 2026-07-05
2026-07-05 peak 6 2026-07-19

IP Ranges (6)

⬇ export CSV
CIDR Org name Registry Status Confidence
188.94.222.16/30 NO-T7D-10030 RIPE ASSIGNED PA ● low
188.94.222.144/28 NO-T7D-10030 RIPE ASSIGNED PA ● low
188.94.222.160/28 NO-T7D-10030 RIPE ASSIGNED PA ● low
188.94.222.176/29 NO-T7D-10030 RIPE ASSIGNED PA ● low
188.94.222.184/30 NO-T7D-10030 RIPE ASSIGNED PA ● low
188.94.222.188/30 NO-T7D-10030 RIPE ASSIGNED PA ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “NO T7D” — 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.
Combined view of all 34 name-family clusters →

Network trust

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

NIC Handles

DUMY-RIPE DUMY-RIPE UPHEADS-MNT