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

87.245.192.0/20

3 residential-proxy exits · 30 days

JSC 'RetnNet'

Announcement
this exact prefix
RPKI valid
Announced by
AS57304
Type
Internet provider
86% of it

Residential-proxy exits

Proxy exits
3
0.07% of its addresses · 30 days
Always-on exits
1
33% of its exits
Spread
3 of 16
/24s with at least one exit
Providers
28
selling exits here
Oct 16, 2026 – Nov 14, 2026

Exits seen per day

242 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
87.245.196.0/2411
87.245.199.0/2401
87.245.203.0/2401

Proxy providers listing exits

  • 711Proxy
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • DataImpulse
  • Decodo
  • GSocks
  • Geonode
  • GloryCloud
  • GonzoProxy
  • IPFly
  • Infatica
  • InfiniteProxies
  • Kookey
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • Novada
  • ProxyWing
  • RainProxy
  • Shifter
  • StrikeProxy
  • TalorData
  • Thordata
  • VantageProxies

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
87.245.192.0/204,096RU-RETNNET-20050824JSC "RetnNet" (ORG-CA1293-RIPE) · RUALLOCATED PANov 25, 2022abuse@retn.ru
└ 87.245.192.128/2732RETN-RU-KZN-1unknownASSIGNED PAFeb 7, 2017abuse@retn.ru
via RU-RETNNET-20050824
└ 87.245.194.192/2664RETN-AKAMAI-NSBRETN Akamai Novosibirsk CDN nodeASSIGNED PAJan 30, 2014abuse@retn.ru
via RU-RETNNET-20050824
└ 87.245.195.0/2664RETN-GGC-STVRETN Google Global Cache Saratov nodeASSIGNED PAJan 31, 2014abuse@retn.ru
via RU-RETNNET-20050824
└ 87.245.195.192/2664RETN-AKAMAI-CEKRETN Akamai Chelyabinsk CDN nodeASSIGNED PADec 12, 2014abuse@retn.ru
via RU-RETNNET-20050824
└ 87.245.196.0/2664RETN-GGC-NNVRETN Google Global Cache Nizhny Novgorod nodeASSIGNED PAJan 31, 2014abuse@retn.ru
via RU-RETNNET-20050824
└ 87.245.196.64/2664RETN-AKAMAI-NNVRETN Akamai Nizhny Novgorod CDN nodeASSIGNED PAJan 30, 2014abuse@retn.ru
via RU-RETNNET-20050824
└ 87.245.196.128/2732RETN-GGC-VOZRETN Google Global Cache Voronezh nodeASSIGNED PAJun 19, 2023abuse@retn.ru
via RU-RETNNET-20050824
└ 87.245.196.192/2664RETN-AKAMAI-VOZRETN Akamai Voronezh CDN nodeASSIGNED PADec 12, 2014abuse@retn.ru
via RU-RETNNET-20050824
└ 87.245.197.0/2664RETN-AKAMAI-MSK-NET2RETN Akamai Moscow CDN node 2ASSIGNED PADec 12, 2014abuse@retn.ru
via RU-RETNNET-20050824
└ 87.245.197.128/2664RETN-GGC-MSKRETN Google Global Cache Moscow nodeASSIGNED PAJan 31, 2014abuse@retn.ru
via RU-RETNNET-20050824

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

4,096 addresses
TypeAddressesShareRanges
Internet provider3,52086%6
Business57614%10

Network & registry

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Rotating
First seen
Mar 2022
Current origin since
Jan 2023 · 3.8 yr
Origin networks
2
Last change of origin
Jan 2023
Recorded history

History

Handoffs
1