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

85.116.136.0/22

11 residential-proxy exits · 30 days

Rocket Way S.R.L.

Announcement
this exact prefix
RPKI valid
Announced by
AS208920
Type
Residential
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
11
1.1% of its addresses · 30 days
Always-on exits
2
18% of its exits
Spread
3 of 4
/24s with at least one exit
Providers
42
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

22K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
85.116.136.0/2414
85.116.138.0/2414
85.116.137.0/2403

Proxy providers listing exits

  • 2Extract
  • 711Proxy
  • Ake.net
  • AnyIP
  • B2Proxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • DataImpulse
  • Decodo
  • EnigmaProxy
  • Evomi
  • FastProxy
  • FlashProxy
  • FloppyData
  • Geonode
  • GoProxies
  • GonzoProxy
  • IPFly
  • IPPeak
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • Kookey
  • LemonBright
  • MangoProxy
  • NovaProxy
  • Oxylabs
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyRack
  • ProxyWing
  • Proxyma
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VitalExclusive
  • Webshare
  • YumiProxy

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
85.116.136.0/221,024IT-ROCKETWAY-20050311Rocket Way S.R.L. (ORG-PBCT1-RIPE) · ITALLOCATED PADec 17, 2019abuse@rocketway.it
└ 85.116.136.0/24256Dynamic_Access_Networks_1unknownASSIGNED PASep 26, 2026abuse@rocketway.it
via IT-ROCKETWAY-20050311
└ 85.116.137.0/24256Dynamic_Access_Networks_2unknownASSIGNED PASep 26, 2026abuse@rocketway.it
via IT-ROCKETWAY-20050311
└ 85.116.138.0/24256Dynamic_Access_Networks_3unknownASSIGNED PASep 26, 2026abuse@rocketway.it
via IT-ROCKETWAY-20050311
└ 85.116.139.0/24256Dynamic_Access_Networks_4unknownASSIGNED PASep 26, 2026abuse@rocketway.it
via IT-ROCKETWAY-20050311

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 this prefix

Summary

Routing history

Pattern
Stable
First seen
Oct 2017
Current origin since
Nov 2019 · 7.0 yr
Origin networks
2
Last change of origin
Nov 2019
Recorded history

History

Handoffs
1