Y525 Global Network

BGP inherited
Cluster stats
Netblocks7
All fragments 17 blocks across 11 clusters
Cluster ID211655407
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

Footprint over time

5 weekly snapshots · JSON
17 0 netblocks since 2026-07-05
2026-07-05 peak 17 2026-07-19

IP Ranges (7)

⬇ export CSV
CIDR Org name Registry Status Confidence
2602:fa3d:f4:1::b4/128 Y525 Global Network PEERINGDB ASSIGNED ● high
2602:fed2:fff:ffff:6::fc/128 Y525 Global Network PEERINGDB ASSIGNED ● high
2a0e:8f01:1000:7::132/128 Y525 Global Network PEERINGDB ASSIGNED ● high
2a0e:8f01:1000:11::153/128 Y525 Global Network PEERINGDB ASSIGNED ● high
2a0e:8f01:1000:22::11e/128 Y525 Global Network PEERINGDB ASSIGNED ● high
2a0e:8f01:1000:32::10d/128 Y525 Global Network PEERINGDB ASSIGNED ● high
2a06:a005:4b0::/44 Y525-GLOBAL-NETWORK RIPE ASSIGNED ● low

Network trust

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

These blocks are registered to Y525 Global Network 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.

2a06:a005:4b0::/44 /44 authorized for AS207852 — Yonghan Ching

NIC Handles

AS207852 DUMY-RIPE DUMY-RIPE ROUTE48-MNT y525-mntner