YUPNET TELECOMUNICACOES
BGP inherited
Cluster stats
Netblocks8
All fragments 31 blocks across 2 clusters
Cluster ID193388428
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

2 weekly snapshots · JSON
8 0 netblocks since 2026-07-05
2026-07-05 peak 8 2026-07-06

IP Ranges (8)

⬇ export CSV
CIDR Org name Registry Status Confidence
45.68.81.203/32 YUPNET TELECOMUNICACOES PEERINGDB ASSIGNED ● high
187.16.212.97/32 YUPNET TELECOMUNICACOES PEERINGDB ASSIGNED ● high
187.16.214.99/32 YUPNET TELECOMUNICACOES PEERINGDB ASSIGNED ● high
200.219.139.34/32 YUPNET TELECOMUNICACOES PEERINGDB ASSIGNED ● high
2001:12f8::212:97/128 YUPNET TELECOMUNICACOES PEERINGDB ASSIGNED ● high
2001:12f8::214:99/128 YUPNET TELECOMUNICACOES PEERINGDB ASSIGNED ● high
2001:12f8:0:2::53:203/128 YUPNET TELECOMUNICACOES PEERINGDB ASSIGNED ● high
2001:12f8:0:3::34/128 YUPNET TELECOMUNICACOES PEERINGDB ASSIGNED ● high

Network trust

what's this?
RPKI hygiene: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (8 of 8)
No discrepancies found among checked blocks.

NIC Handles

AS61712