AUYL

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

Footprint over time

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

IP Ranges (10)

⬇ export CSV
CIDR Org name Registry Status Confidence
78.4.100.216/29 AUYL RIPE ASSIGNED PA ● low
78.4.101.200/29 AUYL RIPE ASSIGNED PA ● low
78.4.130.24/29 AUYL RIPE ASSIGNED PA ● low
78.6.85.88/29 AUYL RIPE ASSIGNED PA ● low
78.6.85.128/29 AUYL RIPE ASSIGNED PA ● low
89.119.241.208/29 AUYL RIPE ASSIGNED PA ● low
89.119.241.216/29 AUYL RIPE ASSIGNED PA ● low
89.119.241.224/29 AUYL RIPE ASSIGNED PA ● low
213.255.92.8/29 AUYL RIPE ASSIGNED PA ● low
213.255.92.32/29 AUYL RIPE ASSIGNED PA ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “AUYL” — often per-country or per-system registrations of the same brand, occasionally a different organisation sharing the name. Not counted in this organisation's own footprint.
Sub-allocations under carriers
IP blocks an ISP reassigned to a similarly-named customer — decoded from the ISP's own naming convention, not a direct registration.

Network trust

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

NIC Handles

BTI-MNT DUMY-RIPE DUMY-RIPE