AAFES

BGP inherited
Cluster stats
Netblocks8
Registered in United Kingdom (6) · KW (2)
All fragments 18 blocks across 6 clusters
Cluster ID208908709
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 4 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
8 0 netblocks since 2026-07-05
2026-07-05 peak 8 2026-07-19

IP Ranges (8)

⬇ export CSV
CIDR Org name Registry Status Confidence
62.150.79.160 – 62.150.79.189 Aafes RIPE ASSIGNED PA ● low
62.150.218.128 – 62.150.218.141 Aafes RIPE ASSIGNED PA ● low
81.142.168.96/29 AAFES RIPE ASSIGNED PA ● low
81.142.171.160/29 AAFES RIPE ASSIGNED PA ● low
86.188.153.192/29 AAFES RIPE ASSIGNED PA ● low
217.37.118.248/29 AAFES RIPE ASSIGNED PA ● low
217.37.179.120/29 AAFES RIPE ASSIGNED PA ● low
217.46.222.64/29 AAFES RIPE ASSIGNED PA ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “AAFES” — 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: C how networks compare →
75.0% of checked blocks have valid RPKI ROA coverage (6 of 8)
No discrepancies found among checked blocks.

NIC Handles

BTNET-MNT DUMY-RIPE DUMY-RIPE QNET-NOC