RED INTERCABLE PERU SAC

BGP inherited
Cluster stats
Netblocks10
All fragments 11 blocks across 2 clusters
Cluster ID204750850
RegistryBGP
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 2 shared RIR contact/maintainer handles
Registry names 2 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

IP Ranges (10)

⬇ export CSV
CIDR Org name Registry Status Confidence
168.194.100.0/22 AS264783 BGP ANNOUNCED ● medium
168.194.100.0/24 AS264783 BGP ANNOUNCED ● medium
168.194.101.0/24 AS264783 BGP ANNOUNCED ● medium
168.194.102.0/24 AS264783 BGP ANNOUNCED ● medium
168.194.103.0/24 AS264783 BGP ANNOUNCED ● medium
201.77.49.0/24 RED INTERCABLE PERU SAC BGP ANNOUNCED ● medium
2803:4f40:1000::/36 AS264783 BGP ANNOUNCED ● medium
2803:4f40:2000::/36 AS264783 BGP ANNOUNCED ● medium
2803:4f40:3000::/36 AS264783 BGP ANNOUNCED ● medium
2803:4f40:8000::/36 AS264783 BGP ANNOUNCED ● medium

Network trust

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

These blocks are registered to RED INTERCABLE PERU SAC 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.

2803:4f40:1000::/36 /36 authorized for AS264783 — AS264783
2803:4f40:2000::/36 /36 authorized for AS264783 — AS264783
2803:4f40:3000::/36 /36 authorized for AS264783 — AS264783
2803:4f40:8000::/36 /36 authorized for AS264783 — AS264783
168.194.100.0/22 /22 authorized for AS264783 — AS264783
168.194.100.0/24 /24 authorized for AS264783 — AS264783
168.194.101.0/24 /24 authorized for AS264783 — AS264783
168.194.102.0/24 /24 authorized for AS264783 — AS264783
168.194.103.0/24 /24 authorized for AS264783 — AS264783
201.77.49.0/24 /24 authorized for AS264783 — AS264783

NIC Handles

AS264783 mnt-ipbroker