RB C+C

Data as of 2026-07-26
BGP inherited
Cluster stats
Netblocks6
IPv6 3 prefixes (largest 2001:7f8:33::a103:4966:1/128)
All fragments 13 blocks across 2 clusters
Cluster ID214583583
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 · report an issue

Footprint over time

4 weekly snapshots · JSON
6 0 netblocks since 2026-07-05
2026-07-05 peak 6 2026-07-13

IP Ranges (6)

⬇ export CSV
CIDR Org name Registry Status Confidence
80.81.193.101/32 RB C+C PEERINGDB ASSIGNED ● high
185.1.102.136/32 RB C+C PEERINGDB ASSIGNED ● high
193.189.82.198/32 RB C+C PEERINGDB ASSIGNED ● high
2001:7f8::8896:0:1/128 RB C+C PEERINGDB ASSIGNED ● high
2001:7f8:33::a103:4966:1/128 RB C+C PEERINGDB ASSIGNED ● high
2001:7f8:bd::3:4966:1/128 RB C+C PEERINGDB ASSIGNED ● high

IPv6 ranges (3)

Network trust

what's this?
RPKI hygiene: B how networks compare →
83.3% of checked blocks have valid RPKI ROA coverage (5 of 6)
No discrepancies found among checked blocks.

NIC Handles

AS34966