Data as of Nov 13, 2026

80.88.49.0/24

24 residential-proxy exits · 30 days

PJSC Rostelecom

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

Residential-proxy exits

Proxy exits
24
9.4% of its addresses · 30 days
Providers
47
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

1.8K observations

Proxy providers listing exits

  • 711Proxy
  • Ake.net
  • B2Proxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FloppyData
  • GSocks
  • Geonix
  • Geonode
  • GonzoProxy
  • HideProxy
  • IPFly
  • IPPeak
  • IPROCKET_BASIC
  • IPROCKET_PREMIUM
  • Infatica
  • InfiniteProxies
  • LemonLabs
  • LemonPrime
  • LudaxProxy
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • Oxylabs
  • PROXYSCRAPE
  • ProxiesVision
  • Proxio
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • Proxyma
  • PuraRoute
  • RainProxy
  • SPYDERPROXY_PREMIUM
  • Shifter
  • Thordata
  • VantageProxies
  • VitalExclusive

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
80.88.48.0/204,096RU-RTK-20050525PJSC Rostelecom (ORG-JR8-RIPE) · RUALLOCATED PAMay 25, 2005abuse@rt.ru
└ 80.88.48.0/23512SPBNITOJSC "North-West Telecom"ASSIGNED PAJun 6, 2005abuse@rt.ru
via RU-RTK-20050525

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 80.88.48.0/20

80.88.48.0/20

Routing history

Pattern
Stable
First seen
Jun 2005
Current origin since
Dec 2018 · 7.9 yr
Origin networks
3
Last change of origin
Dec 2018
Recorded history

History

Handoffs
2