Terasys Virtual

BGP inherited
Cluster stats
Netblocks9
Cluster ID208803556
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

5 weekly snapshots · JSON
9 +2 netblocks since 2026-07-05
2026-07-05 peak 9 2026-07-19

IP Ranges (9)

⬇ export CSV
CIDR Org name Registry Status Confidence
43.254.82.17/32 Terasys Virtual PEERINGDB ASSIGNED ● high
103.30.172.176/32 Terasys Virtual PEERINGDB ASSIGNED ● high
119.11.184.245/32 Terasys Virtual PEERINGDB ASSIGNED ● high
123.108.9.159/32 Terasys Virtual PEERINGDB ASSIGNED ● high
157.10.16.94/32 Terasys Virtual PEERINGDB ASSIGNED ● high
218.100.27.83/32 Terasys Virtual PEERINGDB ASSIGNED ● high
2001:7fa:2:5::19f/128 Terasys Virtual PEERINGDB ASSIGNED ● high
2401:91e0:31::136:868:1/128 Terasys Virtual PEERINGDB ASSIGNED ● high
2404:2f80:206::94/128 Terasys Virtual PEERINGDB ASSIGNED ● high

Network trust

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

NIC Handles

AS136868