YAGUMYAGUM

Data as of 2026-10-11
Handle
This organisation
Netblocks8
IPv6 7 prefixes (largest 2a13:9500:a6::/48)
Record ID246704927
RegistryPEERINGDB
Customerssee who runs inside this network →
Evidence & provenance ?
Attribution RIR handle
Shared handles clustered on 6 shared RIR contact/maintainer handles
Registry names 2 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works · report an issue

IP Ranges (8)

⬇ export CSV
CIDR Org name Registry Status Confidence
164.132.186.206/32 YAGUMYAGUM PEERINGDB ASSIGNED ● high
2001:504:125:e1::94/128 YAGUMYAGUM PEERINGDB ASSIGNED ● high
2001:7f8:d0::3:3690:1/128 YAGUMYAGUM PEERINGDB ASSIGNED ● high
2a0e:8f01:1000:7::107/128 YAGUMYAGUM PEERINGDB ASSIGNED ● high
2a0e:8f01:1000:9::109/128 YAGUMYAGUM PEERINGDB ASSIGNED ● high
2a0e:8f01:1000:10::105/128 YAGUMYAGUM PEERINGDB ASSIGNED ● high
2a0e:8f01:1000:32::100/128 YAGUMYAGUM PEERINGDB ASSIGNED ● high
2a13:9500:a6::/48 YAGUMYAGUM RIPE ASSIGNED ● high

IPv6 ranges (7)

CIDR
2a13:9500:a6::/48
2001:504:125:e1::94/128
2001:7f8:d0::3:3690:1/128
2a0e:8f01:1000:10::105/128
2a0e:8f01:1000:32::100/128
2a0e:8f01:1000:7::107/128
2a0e:8f01:1000:9::109/128

Footprint over time

14 weekly snapshots · JSON
8 -2 netblocks since 2026-07-05
2026-07-05 peak 10 2026-10-11

Network trust

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

NIC Handles

AS210576 DUMY-RIPE DUMY-RIPE ORG-YA196-RIPE YAC15-RIPE netutils-mnt