AS399936 PBX-SALTLAKECITY - PBXIO LLC
🇺🇸ARINassigned
Announced Prefixes (BGP)
3total
2 IPv41 IPv6
IPv4 Addresses
Allocated (RIR)256
Announced (BGP)512
IPv6 Addresses
Allocated (RIR)4.9×10²⁷
Announced (BGP)4.9×10²⁷
Routing hygiene
Score 26/100 · Medium riskRPKI ROA coverage
33.3%
no RPKI invalid prefixes
IRR route objects
100%
no origin mismatches
Hijack signals
0
0 announced against others' ROAs, 0 own announced by others
Upstreams
2
diversity 44/100
- 67% of announced prefixes (2 of 3) have no valid ROA
Based on 3 announced prefixes, updated daily (2026-10-12). How the score works · RPKI explained
Announced Prefixes
(BGP)3|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | Other IRR | 2026-10-12 | |
| No ROA | Other IRR | 2026-10-12 | |
| No ROA | Other IRR | 2026-10-12 |
Allocated Prefixes
(RIR)2Prefix | Country | RIR | Status |
|---|---|---|---|
| 23.187.208.0/24 | 🇺🇸 US | ARIN | allocated |
| 2602:fc38::/36 | 🇺🇸 US | ARIN | allocated |
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 AS399936 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/399936Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/399936" | jq