TBD
Cluster stats
Netblocks12
All fragments 23 blocks across 9 clusters
Cluster ID192700131
RegistryAPNIC
Customersfind customers using this network →
Evidence & provenance ?
Attribution unresolved
Shared handles clustered on 15 shared RIR contact/maintainer handles
Registry names 4 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

IP Ranges (12)

⬇ export CSV
CIDR Org name Registry Status Confidence
31.13.171.0/27 TBD RIPE ASSIGNED PA ● low
80.178.174.96/29 TBD RIPE ASSIGNED PA ● low
85.8.180.0/24 TBD RIPE ASSIGNED PA ● low
85.8.181.0/24 TBD RIPE ASSIGNED PA ● low
91.249.165.40/29 TBD-NET RIPE ASSIGNED PA ● low
93.117.208.209/32 TBD RIPE ASSIGNED PA ● low
95.167.140.0/23 TBD-NET RIPE SUB-ALLOCATED PA ● low
95.167.141.0/24 TBD-NET RIPE SUB-ALLOCATED PA ● low
212.29.211.20/30 tbd RIPE ASSIGNED PA ● low
212.144.103.160/28 TBD-NET RIPE ASSIGNED PA ● low
217.21.193.160/27 TBD RIPE ASSIGNED PA ● low
221.7.16.64/26 TBD-Group APNIC ASSIGNED NON-PORTABLE ● low

Network trust

what's this?
RPKI hygiene: B how networks compare →
91.7% of checked blocks have valid RPKI ROA coverage (11 of 12)
Possible discrepancies (2)

These blocks are registered to TBD but cryptographically authorized for a different, unrelated network (1 distinct holder) — often M&A history, multi-homing, or outsourced/managed hosting, occasionally worth a closer look.

95.167.140.0/23 /23 authorized for AS12389 — PJSC Rostelecom
95.167.141.0/24 /24 authorized for AS12389 — PJSC Rostelecom

NIC Handles

ARCOR-MNT AS9116-MNT DUMY-RIPE DUMY-RIPE EWETEL-MNT INETUM-ES-MNT MAINT-CNCGROUP-XJ MNT-OSSOBV MNT-TWK-LIR NV-MNT-RIPE ROSTELECOM-MNT TNF-MNT +3 more