AS47541 VKONTAKTE-SPB-AS LLC VK
๐ท๐บOrg handle: ORG-VL47-RIPE
http://vk.com
RIPE NCCallocated
Announced Prefixes (BGP)
29total
21 IPv48 IPv6
IPv4 Addresses
Allocated (RIR)61,440
Announced (BGP)80,384
IPv6 Addresses
Allocated (RIR)7.9ร10ยฒโธ
Announced (BGP)7.8ร10ยฒโน
Prefix Limit (IPv4)
100
Prefix Limit (IPv6)
50
Country
๐ท๐บ RURIR
RIPE NCCStatus
allocated
Allocated
2008-07-03
Announced Prefixes
(BGP)29|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| No ROA | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| No ROA | RIPE | 2026-10-11 | |
| No ROA | RIPE | 2026-10-11 | |
87.240.166.0/24MOAS | No ROA | RIPE | 2026-10-11 |
87.240.167.0/24MOAS | No ROA | RIPE | 2026-10-11 |
| Valid | RIPE | 2026-10-11 | |
91.231.133.0/24MOAS | No ROA | RIPE | 2026-10-11 |
91.231.134.0/24MOAS | No ROA | RIPE | 2026-10-11 |
1-10 of 29
1 / 3
Allocated Prefixes
(RIR)12Prefix | Country | RIR | Status |
|---|---|---|---|
| 79.137.139.0/24 | ๐ท๐บ RU | RIPENCC | allocated |
| 79.137.164.0/24 | ๐ท๐บ RU | RIPENCC | allocated |
| 79.137.180.0/24 | ๐ท๐บ RU | RIPENCC | allocated |
| 79.137.183.0/24 | ๐ท๐บ RU | RIPE | assigned |
| 87.240.128.0/18 | ๐ท๐บ RU | RIPENCC | allocated |
| 93.186.224.0/21 | ๐ท๐บ RU | RIPE | assigned |
| 93.186.232.0/21 | ๐ท๐บ RU | RIPE | assigned |
| 95.142.192.0/20 | ๐ท๐บ RU | RIPENCC | allocated |
| 95.142.192.0/21 | ๐ท๐บ RU | RIPE | assigned |
| 95.213.0.0/17 | ๐ท๐บ RU | RIPENCC | allocated |
1-10 of 12
1 / 2
All 29 announced prefixes of AS47541 โ
BGP Neighbours
(seen in AS paths)Upstreams (6)
Networks AS47541 hands its own prefixes to: transit providers, or peers at an exchange.
Downstreams (3)
Networks whose own prefixes AS47541 passes on: usually its customers.
Transfer History
Registry transfers of AS47541 between organisations.
- AS47541M&A ยท
| Date | Resource | From | To | Type |
|---|---|---|---|---|
| AS47541 | VKontakte Ltd | LLC VK | M&A |
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 AS47541 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/47541Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/47541" | jq