AS197583 NEXARUBE Nexarube LLC
RIPE NCCreserved
Announced Prefixes (BGP)
3total
0 IPv43 IPv6
IPv4 Addresses
Allocated (RIR)0
Announced (BGP)0
IPv6 Addresses
Allocated (RIR)5.2×10²⁷
Announced (BGP)2.1×10²⁵
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 (3 of 3) have no valid ROA
- 100% of announced prefixes (3 of 3) have no IRR route object for this ASN
- Only one upstream seen in the AS paths of its routes
Based on 3 announced prefixes, updated daily (2026-10-23). How the score works · RPKI explained
Announced Prefixes
(BGP)3|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| No ROA | - | 2026-10-26 | |
| No ROA | - | 2026-10-26 | |
| No ROA | - | 2026-10-26 |
Allocated Prefixes
(RIR)3Prefix | Country | RIR | Status |
|---|---|---|---|
| 2a14:7580:eb00::/40 | 🇰🇷 KR | RIPE | assigned |
| 2a14:7581:9f80::/44 | 🇰🇷 KR | RIPE | assigned |
| 2a14:7586:e000::/36 | 🇺🇸 US | RIPE | assigned |
All 3 announced prefixes of AS197583 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS197583 hands its own prefixes to: transit providers, or peers at an exchange.
- AS209735LAGRANGE Cloud Technologies Limited3
Transfer History
Registry transfers of AS197583 between organisations.
- AS197583Transfer ·
ASPA
No ASPA
Abuse Contact
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 AS197583 should publish an ASPA object
- IPv4 transfers in the RIPE NCC 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/197583Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/197583" | jq