Data as of Nov 13, 2026

86.111.0.0/19

4 residential-proxy exits · 30 days

PJSC Rostelecom

Announcement
this exact prefix
RPKI valid
Announced by
Type
Residential
99% of it

Residential-proxy exits

Proxy exits
4
0.05% of its addresses · 30 days
Always-on exits
1
25% of its exits
Spread
2 of 32
/24s with at least one exit
Providers
29
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

1.8K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
86.111.3.0/2411
86.111.22.0/2403

Proxy providers listing exits

  • 2Captcha
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • DataImpulse
  • GSocks
  • GonzoProxy
  • IPFly
  • IPOasis
  • Infatica
  • LightningProxies
  • MangoProxy
  • NodeMaven
  • NodeProxy
  • PSBProxy
  • Proxiware
  • Proxmint
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • PuraRoute
  • RainProxy
  • Shifter
  • VitalExclusive
  • VitalProxy

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
86.111.0.0/198,192RU-RTK-20050729PJSC Rostelecom (ORG-JR8-RIPE) · RUALLOCATED PAJul 29, 2005abuse@rt.ru
└ 86.111.0.0/24256FCI-RUSSIAFCI of RussiaASSIGNED PANov 1, 2005abuse@rt.ru
via RU-RTK-20050729
└ 86.111.3.0/24256ROSNET-VSERosnet ( Russian Data Communication Company )ASSIGNED PASep 30, 2005abuse@rt.ru
via RU-RTK-20050729
└ 86.111.4.0/24256ROSNET-VSERosnet ( Russian Data Communication Company )ASSIGNED PAJan 24, 2006abuse@rt.ru
via RU-RTK-20050729
└ 86.111.5.0/2664VNIIOFIFGUC. All - Russian Research InstituteASSIGNED PANov 7, 2005abuse@rt.ru
via RU-RTK-20050729
└ 86.111.6.64/2732PIVZZavod bezalc. napitkovASSIGNED PANov 13, 2007abuse@rt.ru
via RU-RTK-20050729
└ 86.111.7.0/24256RTS-PETERBURGRTS in St. PeterburgASSIGNED PANov 14, 2005abuse@rt.ru
via RU-RTK-20050729
└ 86.111.8.0/24256MGTS-RMGTS915 customersASSIGNED PADec 19, 2007abuse@rt.ru
via RU-RTK-20050729
└ 86.111.9.0/24256ROSNET-VSERosnet ( Russian Data Communication Company )ASSIGNED PAApr 7, 2010abuse@rt.ru
via RU-RTK-20050729
└ 86.111.10.0/24256ROSNET-DEVICESRosnet ( Russian Data Communication Company )ASSIGNED PAJan 24, 2006abuse@rt.ru
via RU-RTK-20050729
└ 86.111.11.0/24256ROSNET-VSERosnet ( Russian Data Communication Company )ASSIGNED PADec 7, 2005abuse@rt.ru
via RU-RTK-20050729
└ 86.111.12.0/24256MGTS915Rosnet customers via MGTS915ASSIGNED PAMar 20, 2006abuse@rt.ru
via RU-RTK-20050729
└ 86.111.13.0/24256ROSNET-VSERosnet ( Russian Data Communication Company )ASSIGNED PADec 27, 2005abuse@rt.ru
via RU-RTK-20050729
└ 86.111.14.0/24256ROSNET-VSERosnet ( Russian Data Communication Company )ASSIGNED PAFeb 2, 2006abuse@rt.ru
via RU-RTK-20050729
└ 86.111.15.0/24256ROSNET-VSERosnet ( Russian Data Communication Company )ASSIGNED PAMar 30, 2006abuse@rt.ru
via RU-RTK-20050729
└ 86.111.16.0/24256ROSNET-VSERosnet ( Russian Data Communication Company )ASSIGNED PAAug 14, 2006abuse@rt.ru
via RU-RTK-20050729
└ 86.111.17.0/24256ROSNET-VSERosnet ( Russian Data Communication Company )ASSIGNED PASep 15, 2006abuse@rt.ru
via RU-RTK-20050729
└ 86.111.18.0/24256ROSNET-VSERosnet ( Russian Data Communication Company )ASSIGNED PAOct 31, 2006abuse@rt.ru
via RU-RTK-20050729
└ 86.111.19.0/24256ROSNET-VSERosnet ( Russian Data Communication Company )ASSIGNED PANov 16, 2006abuse@rt.ru
via RU-RTK-20050729
└ 86.111.20.0/24256ROSNET-VSERosnet ( Russian Data Communication Company )ASSIGNED PAMar 30, 2006abuse@rt.ru
via RU-RTK-20050729
└ 86.111.21.0/24256ROSNET-VSERosnet ( Russian Data Communication Company )ASSIGNED PAFeb 2, 2010abuse@rt.ru
via RU-RTK-20050729
└ 86.111.23.0/24256ROSNET-VSERosnet ( Russian Data Communication Company )ASSIGNED PAFeb 12, 2007abuse@rt.ru
via RU-RTK-20050729
└ 86.111.24.0/24256ROSNET-VSERosnet ( Russian Data Communication Company )ASSIGNED PAMar 15, 2007abuse@rt.ru
via RU-RTK-20050729
└ 86.111.25.0/24256ROSNET-VSERosnet ( Russian Data Communication Company )ASSIGNED PAApr 23, 2007abuse@rt.ru
via RU-RTK-20050729
└ 86.111.26.0/24256ROSNET-VSERosnet ( Russian Data Communication Company )ASSIGNED PAJun 4, 2007abuse@rt.ru
via RU-RTK-20050729
└ 86.111.27.0/24256ROSNET-VSERosnet ( Russian Data Communication Company )ASSIGNED PAJul 11, 2007abuse@rt.ru
via RU-RTK-20050729
└ 86.111.28.0/24256ROSNET-VSERosnet ( Russian Data Communication Company )ASSIGNED PAJul 31, 2007abuse@rt.ru
via RU-RTK-20050729
└ 86.111.29.0/24256ROSNET-VSERosnet ( Russian Data Communication Company )ASSIGNED PASep 3, 2007abuse@rt.ru
via RU-RTK-20050729
└ 86.111.30.0/24256ROSNET-VSERosnet ( Russian Data Communication Company )ASSIGNED PASep 28, 2007abuse@rt.ru
via RU-RTK-20050729
└ 86.111.31.0/24256ROSNET-VSERosnet ( Russian Data Communication Company )ASSIGNED PAOct 30, 2007abuse@rt.ru
via RU-RTK-20050729

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
TypeAddressesShareRanges
Residential8,09699%3
Business961.2%2

Network & registry

Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
Sep 2005
Current origin since
Sep 2005 · 21 yr
Origin networks
1