AS22403 TRINICOM - TRINICOM COMMUNICATIONS
🇺🇸ARINassigned
Announced Prefixes (BGP)
4total
4 IPv40 IPv6
IPv4 Addresses
Allocated (RIR)0
Announced (BGP)2,048
IPv6 Addresses
Allocated (RIR)0
Announced (BGP)0
Routing hygiene
Score 55/100 · High riskRPKI ROA coverage
0%
no RPKI invalid prefixes
IRR route objects
0%
no origin mismatches
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
- Only one upstream seen in the AS paths of its routes
Based on 4 announced prefixes, updated daily (2026-10-12). How the score works · RPKI explained
Announced Prefixes
(BGP)4|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| No ROA | - | 2026-10-12 | |
| No ROA | - | 2026-10-12 | |
| No ROA | - | 2026-10-12 | |
| No ROA | - | 2026-10-12 |
All 4 announced prefixes of AS22403 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS22403 hands its own prefixes to: transit providers, or peers at an exchange.
- AS3356Level 3 Parent4
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 AS22403 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/22403Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/22403" | jq