AS501 AFCONC-BLOCK1-AS - Air Force Systems Networking
Announced Prefixes (BGP)
4total
4 IPv40 IPv6
IPv4 Addresses
Allocated (RIR)0
Announced (BGP)1,024
IPv6 Addresses
Allocated (RIR)0
Announced (BGP)0
Prefix Limit (IPv4)
10
Prefix Limit (IPv6)
5
Allocated
-
Routing hygiene
Score 65/100 · High riskRPKI ROA coverage
0%
no RPKI invalid prefixes
IRR route objects
0%
4 prefixes registered for another origin
Hijack signals
0
0 announced against others' ROAs, 0 own announced by others
Upstreams
1
diversity 0/100
- 100% of announced prefixes (4 of 4) have no valid ROA
- 100% of announced prefixes (4 of 4) have no IRR route object for this ASN
- 4 prefixes registered in IRR route objects for another active network and not authorized by a ROA
- Only one upstream seen in the AS paths of its routes
Based on 4 announced prefixes, updated daily (2026-10-17). How the score works · RPKI explained
Announced Prefixes
(BGP)4|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
205.173.217.0/24MOAS | No ROA | - | 2026-10-17 |
205.173.218.0/24MOAS | No ROA | - | 2026-10-17 |
205.173.219.0/24MOAS | No ROA | - | 2026-10-17 |
205.173.221.0/24MOAS | No ROA | - | 2026-10-17 |
All 4 announced prefixes of AS501 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS501 hands its own prefixes to: transit providers, or peers at an exchange.
- AS54355NETWORK SERVICES4
ASPA
No ASPA
External Links
Learn more
- What is an ASN?Autonomous systems, ASN ranges and how they are assigned
- RPKI and route origin validationWhat the RPKI badges on the prefix list mean
- ASPA explainedWhy AS501 should publish an ASPA object
- IPv4 transfer marketTransfers published by all five RIRs
- ASN data in AI agents and SIEMMCP server and API integrations
API
Open https://api.ipctl.io/v1/asn/501Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/501" | jq