LAYER3 INTEL
Get started
Sign in
Data as of Nov 12, 2026

78.85.48.0/24

256 residential-proxy exits · 30 days

PJSC Rostelecom

Announcement
78.85.48.0/23
RPKI valid
Announced by
AS12389
Type
Residential
Risk
0 / 100 · Low
Proxy exits nearby

Residential-proxy exits

Proxy exits
256
100% of its addresses · 30 days
Always-on exits
170
66% of its exits
Providers
41
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

301K observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 9Proxy
  • Ake.net
  • AnyIP
  • BirdProxies
  • BottingTools
  • Bright Data
  • ByteProxies
  • Byteful
  • CoreProxy
  • DataImpulse
  • Decodo
  • Evomi
  • FlashProxy
  • FloppyData
  • Geonode
  • GoProxies
  • GonzoProxy
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • Kookey
  • MarsProxies
  • Maskify
  • NSocks
  • Oxylabs
  • PrivateProxy
  • Proxy-Cheap
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyRack
  • ProxyWing
  • Proxying
  • Proxyma
  • Shifter
  • StrikeProxy
  • Thordata
  • ThunderProxy
  • Webshare

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
78.85.0.0/16
since May 2016
AS12389Residential9,563
1,047 always on
PJSC Rostelecom

Registrations in this block

The registry's network records over this block, widest first, each under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
78.85.0.0/1665,536RU-RTK-20070419PJSC Rostelecom (ORG-JR8-RIPE) · RUALLOCATED PAApr 19, 2007abuse@rt.ru
└ 78.85.45.0 - 78.85.64.2555,120UDMVT-NETSecond assignmentASSIGNED PAOct 23, 2026abuse@rt.ru
via RU-RTK-20070419

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

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Covering aggregate above, the prefix's own history below

78.85.48.0/23

Routing history

Pattern
Stable
First seen
Jun 2017
Current origin since
Jun 2017 · 9.4 yr
Origin networks
1