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

5.228.232.0/24

14 residential-proxy exits · 30 days

PJSC Rostelecom

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

Residential-proxy exits

Proxy exits
14
5.5% of its addresses · 30 days
Always-on exits
1
7.1% of its exits
Providers
47
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

4.1K observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 9Proxy
  • Ake.net
  • BestProxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • DataImpulse
  • EnigmaProxy
  • Evomi
  • FlashProxy
  • FloppyData
  • GSocks
  • Geonix
  • Geonode
  • GonzoProxy
  • HydraProxy
  • IPFly
  • IPPeak
  • Infatica
  • InfiniteProxies
  • LemonLabs
  • LemonPrime
  • LightningProxies
  • MangoProxy
  • NSocks
  • NodeProxy
  • NovaProxy
  • Oxylabs
  • PrivateProxy
  • Proxiware
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • PuraRoute
  • RainProxy
  • RoamProxy
  • Shifter
  • Smartproxy
  • VantageProxies
  • VitalExclusive
  • VitalProxy

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
5.228.0.0/1665,536RU-RTK-20120907PJSC Rostelecom (ORG-JR8-RIPE) · RUALLOCATED PASep 7, 2012abuse@rt.ru
└ 5.228.128.0/1732,768NCN-BBCUSTNCNET Broadband customersASSIGNED PAJul 27, 2026abuse@rt.ru
via RU-RTK-20120907

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

Who has announced 5.228.0.0/16

5.228.0.0/16

Routing history

Pattern
Stable
First seen
Sep 2012
Current origin since
Sep 2012 · 14 yr
Origin networks
1