Data as of Nov 20, 2026

95.163.32.0/19

3 residential-proxy exits · 30 days

LLC VK

Announcement
this exact prefix
RPKI valid
Announced by
Type
Hosting
Risk
50 / 100 · Medium

Residential-proxy exits

Proxy exits
3
0.04% of its addresses · 30 days
Spread
1 of 32
/24s with at least one exit
Providers
2
selling exits here
Oct 21, 2026 – Nov 19, 2026

Exits seen per day

6 observations

Proxy providers listing exits

  • IPFly
  • PuraRoute

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.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
95.163.32.0/198,192RU-NETBRIDGE-20081230LLC VK (ORG-LLCN4-RIPE) · RUALLOCATED PAJul 8, 2014abuse@corp.mail.ru
└ 95.163.32.0/221,024VK-FRONTVK ServicesASSIGNED PANov 28, 2018abuse@corp.mail.ru
via RU-NETBRIDGE-20081230
└ 95.163.36.0/221,024VK-FRONTVK ServicesASSIGNED PANov 28, 2018abuse@corp.mail.ru
via RU-NETBRIDGE-20081230
└ 95.163.40.0/212,048VK-FRONTVK ServicesASSIGNED PANov 28, 2018abuse@corp.mail.ru
via RU-NETBRIDGE-20081230
└ 95.163.48.0/204,096VK-FRONTVK ServicesASSIGNED PANov 28, 2018abuse@corp.mail.ru
via RU-NETBRIDGE-20081230

A contact marked “via” is the registry's: the record names none of its own, so the registry hands down its parent's.

Network & registry

Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
Feb 2009
Current origin since
Jul 2014 · 12 yr
Origin networks
2
Last change of origin
Jul 2014
Recorded history

History

Handoffs
1