Data as of Nov 7, 2026
195.12.64.0/19
No anonymizer space · no proxy exits in 30 daysPJSC 'Vimpelcom'
Registrations in this block
The registry's network records over the announcement: those covering it, widest first, then every record inside it, under its parent.
| Range | Addresses | Netname | Holder | Type | Created | Abuse contact |
|---|---|---|---|---|---|---|
| 195.12.64.0/19 | 8,192 | RU-SOVINTEL-20040809 | PJSC "Vimpelcom" (ORG-ES15-RIPE) · RU | ALLOCATED PA | Jan 9, 2002 | abuse-b2b@ |
| └ 195.12.64.0/24 | 256 | UTNET | UTNET Customers | ASSIGNED PA | May 19, 2009 | abuse-b2b@ via RU-SOVINTEL-20040809 |
| └ 195.12.65.48/29 | 8 | UTNET-IKT | "Golden ISP" Ltd. | ASSIGNED PA | May 20, 2009 | abuse-b2b@ via RU-SOVINTEL-20040809 |
| └ 195.12.65.64/28 | 16 | UTNET-IPDANELYUK | "Golden ISP" Ltd. | ASSIGNED PA | May 20, 2009 | abuse-b2b@ via RU-SOVINTEL-20040809 |
| └ 195.12.65.80/28 | 16 | UTNET-IPSAVCHENKO | "Golden ISP" Ltd. | ASSIGNED PA | May 20, 2009 | abuse-b2b@ via RU-SOVINTEL-20040809 |
| └ 195.12.65.96/29 | 8 | UTNET-IPDROZDOFF | "Golden ISP" Ltd. | ASSIGNED PA | May 20, 2009 | abuse-b2b@ via RU-SOVINTEL-20040809 |
| └ 195.12.65.120/29 | 8 | UTNET-ICEU | "Golden ISP" Ltd. | ASSIGNED PA | May 20, 2009 | abuse-b2b@ via RU-SOVINTEL-20040809 |
| └ 195.12.65.136/29 | 8 | UTNET-IPKISEL | "Golden ISP" Ltd. | ASSIGNED PA | May 20, 2009 | abuse-b2b@ via RU-SOVINTEL-20040809 |
| └ 195.12.65.144/28 | 16 | UTNET-URALPHARM | "Golden ISP" Ltd. | ASSIGNED PA | May 20, 2009 | abuse-b2b@ via RU-SOVINTEL-20040809 |
| └ 195.12.65.192/27 | 32 | UTNET-STUDIOIT | "Golden ISP" Ltd. | ASSIGNED PA | May 20, 2009 | abuse-b2b@ via RU-SOVINTEL-20040809 |
| └ 195. | 1,792 | FTTB | Dynamic FTTB users block | ASSIGNED PA | May 28, 2009 | abuse-b2b@ via RU-SOVINTEL-20040809 |
| └ 195.12.73.0/24 | 256 | UTNET | UTNET Customers | ASSIGNED PA | May 19, 2009 | abuse-b2b@ via RU-SOVINTEL-20040809 |
| └ 195.12.74.0/24 | 256 | UTNET | UTNET Customers | ASSIGNED PA | May 19, 2009 | abuse-b2b@ via RU-SOVINTEL-20040809 |
| └ 195.12.75.0/24 | 256 | UTNET | UTNET Customers | ASSIGNED PA | May 20, 2009 | abuse-b2b@ via RU-SOVINTEL-20040809 |
| └ 195.12.76.0/24 | 256 | UTNET | UTNET Customers | ASSIGNED PA | May 20, 2009 | abuse-b2b@ via RU-SOVINTEL-20040809 |
| └ 195.12.77.0/24 | 256 | UTNET | UTNET Customers | ASSIGNED PA | May 20, 2009 | abuse-b2b@ via RU-SOVINTEL-20040809 |
| └ 195.12.78.0/24 | 256 | UTNET | UTNET Customers | ASSIGNED PA | May 20, 2009 | abuse-b2b@ via RU-SOVINTEL-20040809 |
| └ 195.12.79.0/24 | 256 | UTNET | UTNET Customers | ASSIGNED PA | May 20, 2009 | abuse-b2b@ via RU-SOVINTEL-20040809 |
| └ 195.12.80.0/24 | 256 | UTNET | UTNET Customers | ASSIGNED PA | May 19, 2009 | abuse-b2b@ via RU-SOVINTEL-20040809 |
| └ 195.12.81.0/24 | 256 | UTNET | UTNET Customers | ASSIGNED PA | Jul 6, 2004 | abuse-b2b@ via RU-SOVINTEL-20040809 |
| └ 195.12.82.0/24 | 256 | UTNET | UTNET Customers | ASSIGNED PA | May 20, 2009 | abuse-b2b@ via RU-SOVINTEL-20040809 |
| └ 195.12.83.0/24 | 256 | UTNET | UTNET Customers | ASSIGNED PA | May 20, 2009 | abuse-b2b@ via RU-SOVINTEL-20040809 |
| └ 195.12.84.0/24 | 256 | UTNET | UTNET Customers | ASSIGNED PA | May 20, 2009 | abuse-b2b@ via RU-SOVINTEL-20040809 |
| └ 195.12.85.0/24 | 256 | UTNET | UTNET Customers | ASSIGNED PA | May 20, 2009 | abuse-b2b@ via RU-SOVINTEL-20040809 |
| └ 195.12.86.0/24 | 256 | UTNET | UTNET Customers | ASSIGNED PA | May 20, 2009 | abuse-b2b@ via RU-SOVINTEL-20040809 |
| └ 195.12.87.0/24 | 256 | UTNET | UTNET Customers | ASSIGNED PA | May 20, 2009 | abuse-b2b@ via RU-SOVINTEL-20040809 |
| └ 195.12.88.0/24 | 256 | UTNET | UTNET Customers | ASSIGNED PA | May 20, 2009 | abuse-b2b@ via RU-SOVINTEL-20040809 |
| └ 195.12.89.0/24 | 256 | UTNET | UTNET Customers | ASSIGNED PA | May 20, 2009 | abuse-b2b@ via RU-SOVINTEL-20040809 |
| └ 195. | 1,536 | FTTB | Dynamic FTTB users block | ASSIGNED PA | May 28, 2009 | abuse-b2b@ via RU-SOVINTEL-20040809 |
A contact marked “via” is the registry's: the record names none of its own, so the registry hands down its parent's.
Composition
The types across the prefix's announced space, by addresses.
Announced space
Address share
Announced space
Types across the prefix
8,192 addresses
| Type | Addresses | Share | Ranges | |
|---|---|---|---|---|
| Residential | 8,080 | 99% | 6 | |
| Business | 112 | 1.4% | 8 |
Network & registry
Origin network
AS3253
RU
- Name
- PJSC 'Vimpelcom'
- Type
- Internet provider
- Registered
- Sep 16, 1994
- Domain
- beeline.ru
- Industry
- Internet Service Provider (ISP)
- Spamhaus ASN-DROP
- not listed
Routing timeline
Who has announced this prefix
Summary
Routing history
- Pattern
- Stable
- First seen
- May 2005
- Current origin since
- Apr 2014 · 13 yr
- Origin networks
- 2
- Last change of origin
- Apr 2014
Recorded history
History
- Handoffs
- 1
IRR
Route objects on the exact prefix
| Origin | Registry | Description | Maintainer | Modified |
|---|---|---|---|---|
| AS3235 not the origin | RIPE | DELEGATED BLOCK | QUORUS-MNT | Sep 22, 2001 |
Whois
Registration for this announcement
- Range
- 195.
12. 64. 0/ 19 - Netname
- RU-SOVINTEL-20040809
- Registrant
- PJSC "Vimpelcom"
- Registrant country
- RU
- Organization
- PJSC "Vimpelcom" (ORG-ES15-RIPE)
- Org country
- RU
- Type
- ALLOCATED PA
- Created
- Jan 9, 2002
- Updated
- Oct 27, 2016
- Maintainer
- RIPE-NCC-HM-MNT
- RIR
- RIPE NCC
- Country
- RU
- Delegated
- Jan 28, 1997
- Status
- assigned
Report abuse
Abuse contact
- abuse-b2b@
beeline. ru - Name
- Sovintel Abuse Department
- Handle
- SVNT2-RIPE