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

195.136.4.0/22

6 residential-proxy exits · 30 days

SERVIRE Adam Kozlowski · space held by Exatel S.A.

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

Residential-proxy exits

Proxy exits
6
0.59% of its addresses · 30 days
Spread
4 of 4
/24s with at least one exit
Providers
22
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

502 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
195.136.4.0/2402
195.136.7.0/2402
195.136.5.0/2401
195.136.6.0/2401

Proxy providers listing exits

  • 2Captcha
  • 2Extract
  • AnyIP
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • FastProxy
  • FlashProxy
  • FloppyData
  • GonzoProxy
  • IPOasis
  • Infatica
  • LemonBright
  • LightningProxies
  • MangoProxy
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • Shifter
  • VibeProxies
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
195.136.0.0/16
since May 2017
AS20804Residential1,510
70 always on
Exatel S.A.

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
195.136.0.0/1665,536PL-TELENERGO-960503Exatel S.A. (ORG-TS16-RIPE) · PLALLOCATED PAOct 10, 2001abuse@exatel.pl
└ 195.136.4.0/221,024SERVIRE-NETunknownASSIGNED PAJun 14, 2017abuse@exatel.pl
via PL-TELENERGO-960503

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

Covering aggregate above, the prefix's own history below

Summary

Routing history

Pattern
Stable
First seen
Aug 2016
Current origin since
Nov 2017 · 9.0 yr
Origin networks
2
Last change of origin
Nov 2017
Recorded history

History

Handoffs
1