AS401847 321-WLCS-ASN - 321 Communications, Inc.
🇺🇸ARINassigned
Announced Prefixes (BGP)
5total
2 IPv43 IPv6
IPv4 Addresses
Allocated (RIR)256
Announced (BGP)512
IPv6 Addresses
Allocated (RIR)3×10²⁶
Announced (BGP)3.6×10²⁴
Routing hygiene
Score 28/100 · Medium riskRPKI ROA coverage
60%
no RPKI invalid prefixes
IRR route objects
60%
2 prefixes registered for another origin
Hijack signals
0
0 announced against others' ROAs, 0 own announced by others
Upstreams
1
diversity 0/100
- 40% of announced prefixes (2 of 5) have no valid ROA
- Only one upstream seen in the AS paths of its routes
- 40% of announced prefixes (2 of 5) have no IRR route object for this ASN
Based on 5 announced prefixes, updated daily (2026-10-26). How the score works · RPKI explained
Announced Prefixes
(BGP)5|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | ARIN | 2026-10-26 | |
| No ROA | - | 2026-10-26 | |
| No ROA | - | 2026-10-26 | |
| Valid | ARIN | 2026-10-26 | |
| Valid | ARIN | 2026-10-26 |
Allocated Prefixes
(RIR)2Prefix | Country | RIR | Status |
|---|---|---|---|
| 23.142.140.0/24 | 🇺🇸 US | ARIN | allocated |
| 2602:f5ca::/40 | 🇺🇸 US | ARIN | allocated |
All 5 announced prefixes of AS401847 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS401847 hands its own prefixes to: transit providers, or peers at an exchange.
- AS174Cogent Communications5
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 AS401847 should publish an ASPA object
- IPv4 transfers in the ARIN regionMonthly volume and the latest registry transfers
- ASN data in AI agents and SIEMMCP server and API integrations
API
Open https://api.ipctl.io/v1/asn/401847Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/401847" | jq