AS53388 TEFEXIA - Tefexia LC
🇺🇸ARINassigned
Announced Prefixes (BGP)
5total
3 IPv42 IPv6
IPv4 Addresses
Allocated (RIR)512
Announced (BGP)768
IPv6 Addresses
Allocated (RIR)7.9×10²⁸
Announced (BGP)7.9×10²⁸
Routing hygiene
Score 5/100 · Low riskRPKI ROA coverage
100%
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 48/100
- All announced prefixes have a valid ROA and a matching IRR route object
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 | |
| Valid | ARIN | 2026-10-26 | |
| Valid | ARIN | 2026-10-26 | |
| Valid | ARIN | 2026-10-26 | |
| Valid | - | 2026-10-26 |
Allocated Prefixes
(RIR)3Prefix | Country | RIR | Status |
|---|---|---|---|
| 23.128.236.0/24 | 🇺🇸 US | ARIN | allocated |
| 23.140.36.0/24 | 🇺🇸 US | ARIN | allocated |
| 2607:eb40::/32 | 🇺🇸 US | ARIN | allocated |
All 5 announced prefixes of AS53388 →
BGP Neighbours
(seen in AS paths)Upstreams (2)
Networks AS53388 hands its own prefixes to: transit providers, or peers at an exchange.
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 AS53388 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/53388Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/53388" | jq