CROSS CONNECT PROVEDOR

Data as of 2026-10-25
BGP inherited
This organisation
Netblocks6 · 1,025 IPv4 addresses
IPv6 2 prefixes (largest 2804:7388::/32)
Also registered under this name 10 netblocks across 3 separate records
Record ID256083034
RegistryBGP
Customerssee who runs inside this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 6 shared RIR contact/maintainer handles
Registry names 3 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works · report an issue

IP Ranges (6)

⬇ export CSV
CIDR Org name Registry Status Confidence
187.16.217.224/32 CROSS CONNECT PROVEDOR PEERINGDB ASSIGNED ● high
187.121.152.0/22 CROSS CONNECT PROVEDOR BGP ANNOUNCED ● high
187.121.152.0/23 CROSS CONNECT PROVEDOR BGP ANNOUNCED ● high
187.121.154.0/23 CROSS CONNECT PROVEDOR BGP ANNOUNCED ● high
2001:12f8::217:224/128 CROSS CONNECT PROVEDOR PEERINGDB ASSIGNED ● high
2804:7388::/32 CROSS CONNECT PROVEDOR BGP ANNOUNCED ● high

IPv6 ranges (2)

CIDR
2804:7388::/32
2001:12f8::217:224/128

Footprint over time

10 weekly snapshots · JSON
7 +1 netblocks since 2026-07-05
2026-07-05 peak 9 2026-10-25

Network trust

what's this?
RPKI hygiene: D how networks compare →
28.6% of checked blocks have valid RPKI ROA coverage (2 of 7)
No discrepancies found among checked blocks.

NIC Handles

34752285000139 AS270921 AS270921 VAFNA7 VAFNA7 VAFNA7