AS43317 VEESP-AS SIA VEESP
🇱🇻Org handle: ORG-VS198-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
6total
4 IPv42 IPv6
IPv4 Addresses
Allocated (RIR)6,400
Announced (BGP)6,912
IPv6 Addresses
Allocated (RIR)1.5×10²⁹
Announced (BGP)1.5×10²⁹
Announced Prefixes
(BGP)6|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-09 | |
| Valid | RIPE | 2026-10-09 | |
| Valid | RIPE | 2026-10-09 | |
| Valid | RIPE | 2026-10-09 | |
| Valid | RIPE | 2026-10-09 | |
| Valid | RIPE | 2026-10-09 |
Allocated Prefixes
(RIR)5Prefix | Country | RIR | Status |
|---|---|---|---|
| 77.73.64.0/21 | 🇱🇻 LV | RIPENCC | allocated |
| 91.209.70.0/24 | 🇧🇿 BZ | RIPENCC | assigned |
| 94.242.48.0/20 | 🇱🇻 LV | RIPENCC | allocated |
| 2a00:1838::/32 | 🇷🇺 RU | RIPENCC | allocated |
| 2a0a:4784::/32 | 🇷🇺 RU | RIPE | assigned |
All 6 announced prefixes of AS43317 →
BGP Neighbours
(seen in AS paths)Upstreams (2)
Networks AS43317 hands its own prefixes to: transit providers, or peers at an exchange.
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 AS43317 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/43317Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/43317" | jq