NOC-RIPE

Data as of 2026-09-06
BGP inherited
This organisation
Netblocks6
IPv6 6 prefixes (largest 2003:8:0:10::/64)
Record ID237878726
RegistryRIPE
Customerssee who runs inside 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 · report an issue

IP Ranges (6)

⬇ export CSV
CIDR Org name Registry Status Confidence
2003:8:0:1::/64 NOC-RIPE RIPE ASSIGNED ● low
2003:8:0:7::/64 NOC-RIPE RIPE ASSIGNED ● low
2003:8:0:b::/64 NOC-RIPE RIPE ASSIGNED ● low
2003:8:0:e::/64 NOC-RIPE RIPE ASSIGNED ● low
2003:8:0:10::/64 NOC-RIPE RIPE ASSIGNED ● low
2003:8:0:15::/64 NOC-RIPE RIPE ASSIGNED ● low

IPv6 ranges (6)

CIDR
2003:8:0:10::/64
2003:8:0:15::/64
2003:8:0:1::/64
2003:8:0:7::/64
2003:8:0:b::/64
2003:8:0:e::/64

Footprint over time

8 weekly snapshots · JSON
6 0 netblocks since 2026-07-05
2026-07-05 peak 6 2026-09-06

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

DTAG-NIC DUMY-RIPE DUMY-RIPE