Data as of Nov 20, 2026

78.81.198.0/24

6 residential-proxy exits · 30 days

PJSC Rostelecom

Announcement
RPKI valid
Announced by
Type
Residential
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
6
2.3% of its addresses · 30 days
Always-on exits
1
17% of its exits
Providers
28
selling exits here
Oct 21, 2026 – Nov 19, 2026

Exits seen per day

298 observations

Proxy providers listing exits

  • 2Captcha
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CYBERYOZH
  • FLAMEPROXIES_BASIC
  • FLAMEPROXIES_PREMIUM
  • GEEKPROXY_FLEX
  • GSocks
  • Geonix
  • GonzoProxy
  • HydraProxy
  • IPFly
  • Infatica
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • PuraRoute
  • SOTAPROXY
  • Shifter
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
78.81.0.0/16
since Oct 2018
AS12389Residential5,014
815 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.81.0.0/1665,536RU-RTK-20070327PJSC Rostelecom (ORG-JR8-RIPE) · RUALLOCATED PAMar 27, 2007abuse@rt.ru
└ 78.81.192.0/1816,384DATACOM-NETWORKNovgorod DatacomASSIGNED PADec 17, 2013abuse@rt.ru
via RU-RTK-20070327

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

Covering aggregate above, the prefix's own history below

78.81.192.0/18

Routing history

Pattern
Stable
First seen
Mar 2013
Current origin since
Mar 2013 · 14 yr
Origin networks
1