AS215313 LINEAR-NETWORK Emily Ingalls
🇺🇸Org handle: ORG-EI95-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
2total
0 IPv42 IPv6
IPv4 Addresses
Allocated (RIR)0
Announced (BGP)0
IPv6 Addresses
Allocated (RIR)2×10²⁵
Announced (BGP)2×10²⁵
Routing hygiene
Score 15/100 · Low riskRPKI ROA coverage
100%
no RPKI invalid prefixes
IRR route objects
100%
no origin mismatches
Hijack signals
1
0 announced against others' ROAs, 1 own announced by others
Upstreams
1
diversity 0/100
- Only one upstream seen in the AS paths of its routes
- 1 prefix of this ASN announced by another network against its ROAs
Based on 2 announced prefixes, updated daily (2026-10-25). How the score works · RPKI explained
Announced Prefixes
(BGP)2|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | Other IRRRIPE | 2026-10-25 | |
| Valid | RIPE | 2026-10-25 |
Allocated Prefixes
(RIR)2Prefix | Country | RIR | Status |
|---|---|---|---|
| 2a0f:85c1:398::/48 | 🇺🇸 US | RIPE | assigned |
| 2a0f:85c1:b20::/44 | 🇺🇸 US | RIPE | assigned |
All 2 announced prefixes of AS215313 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS215313 hands its own prefixes to: transit providers, or peers at an exchange.
- AS34927IFog2
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 AS215313 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/215313Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/215313" | jq