AS402415 VPECEDGE - Vpecedge
🇺🇸ARINassigned
Announced Prefixes (BGP)
1total
1 IPv40 IPv6
IPv4 Addresses
Allocated (RIR)512
Announced (BGP)256
IPv6 Addresses
Allocated (RIR)3×10²⁶
Announced (BGP)0
Routing hygiene
Score 70/100 · High riskRPKI ROA coverage
0%
2 prefixes RPKI invalid
IRR route objects
0%
2 prefixes registered for another origin
Hijack signals
0
0 announced against others' ROAs, 0 own announced by others
Upstreams
1
diversity 0/100
- 100% of announced prefixes (2 of 2) have no valid ROA, 2 of them RPKI invalid
- 100% of announced prefixes (2 of 2) have no IRR route object for this ASN
- 1 prefix registered in IRR route objects for another active network and not authorized by a ROA
- Only one upstream seen in the AS paths of its routes
Based on 2 announced prefixes, updated daily (2026-10-20). How the score works · RPKI explained
Announced Prefixes
(BGP)1|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
2.26.171.0/24MOAS | Invalid | - | 2026-10-24 |
Allocated Prefixes
(RIR)3Prefix | Country | RIR | Status |
|---|---|---|---|
| 2.26.171.0/24 | 🇪🇺 EU | RIPE | assigned |
| 23.156.132.0/24 | 🇺🇸 US | ARIN | allocated |
| 2602:f3fa::/40 | 🇺🇸 US | ARIN | allocated |
All 1 announced prefix of AS402415 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS402415 hands its own prefixes to: transit providers, or peers at an exchange.
- AS62610Zenlayer2
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 AS402415 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/402415Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/402415" | jq