AS50147 CITY26-AS Posazhennikov Vladimir Vasilevich
π·πΊOrg handle: ORG-PVV3-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
2total
2 IPv40 IPv6
IPv4 Addresses
Allocated (RIR)17,920
Announced (BGP)1,280
IPv6 Addresses
Allocated (RIR)6.3Γ10Β²βΉ
Announced (BGP)0
Prefix Limit (IPv4)
20
Prefix Limit (IPv6)
5
Country
π·πΊ RURIR
RIPE NCCStatus
allocated
Allocated
2009-11-23
Announced Prefixes
(BGP)2|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| No ROA | RIPE | 2026-10-08 | |
| No ROA | RIPE | 2026-10-08 |
Allocated Prefixes
(RIR)6Prefix | Country | RIR | Status |
|---|---|---|---|
| 31.204.0.0/18 | π·πΊ RU | RIPENCC | allocated |
| 31.204.0.0/24 | π·πΊ RU | RIPE | assigned |
| 78.24.204.0/25 | πΊπΈ US | RIPE | assigned |
| 78.24.204.128/25 | πΊπΈ US | RIPE | assigned |
| 185.175.16.0/22 | π·πΊ RU | RIPENCC | allocated |
| 2a0a:a6c0::/29 | π·πΊ RU | RIPENCC | allocated |
All 2 announced prefixes of AS50147 β
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS50147 hands its own prefixes to: transit providers, or peers at an exchange.
- AS12389ROSTELECOM PJSC Rostelecom2
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 AS50147 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/50147Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/50147" | jq