AS39480 VENIGO-AS VENIGO SARL
🇫🇷Org handle: ORG-VS38-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
3total
3 IPv40 IPv6
IPv4 Addresses
Allocated (RIR)3,072
Announced (BGP)3,072
IPv6 Addresses
Allocated (RIR)7.9×10²⁸
Announced (BGP)0
Announced Prefixes
(BGP)3|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 |
Allocated Prefixes
(RIR)3Prefix | Country | RIR | Status |
|---|---|---|---|
| 46.182.72.0/21 | 🇫🇷 FR | RIPENCC | allocated |
| 195.225.204.0/22 | 🇫🇷 FR | RIPENCC | assigned |
| 2a02:26b8::/32 | 🇫🇷 FR | RIPENCC | allocated |
All 3 announced prefixes of AS39480 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS39480 hands its own prefixes to: transit providers, or peers at an exchange.
- AS174Cogent Communications3
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 AS39480 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/39480Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/39480" | jq