TURBO CAIRES NET

Data as of 2026-08-30
BGP inherited
Cluster stats
Netblocks5 · 514 IPv4 addresses
IPv6 2 prefixes (largest 2001:12f8::211:122/128)
Cluster ID232899342
RegistryPEERINGDB
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 5 shared RIR contact/maintainer handles
Registry names 2 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works · report an issue

Footprint over time

3 weekly snapshots · JSON
11 0 netblocks since 2026-07-05
2026-07-05 peak 11 2026-07-12

IP Ranges (5)

⬇ export CSV
CIDR Org name Registry Status Confidence
187.16.211.122/32 TURBO CAIRES NET PEERINGDB ASSIGNED ● high
187.16.211.143/32 TURBO CAIRES NET PEERINGDB ASSIGNED ● high
2001:12f8::211:122/128 TURBO CAIRES NET PEERINGDB ASSIGNED ● high
2001:12f8::211:143/128 TURBO CAIRES NET PEERINGDB ASSIGNED ● high
45.162.202.0/23 TURBO CAIRES NET ARIN ALLOCATED ● low

IPv6 ranges (2)

Network trust

what's this?
RPKI hygiene: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (5 of 5)
Possible discrepancies (1)

These blocks are registered to TURBO CAIRES NET 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.

45.162.202.0/23 /23 authorized for AS271617 — AS271617

NIC Handles

35441360000103 AS271617 EZBSI12 PRSRO74 PRSRO74