Data as of Nov 16, 2026

195.136.168.0/22

3 residential-proxy exits · 30 days

TELNAP TELECOM Sp. z o.o. · space held by Exatel S.A.

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

Residential-proxy exits

Proxy exits
3
0.29% of its addresses · 30 days
Spread
2 of 4
/24s with at least one exit
Providers
21
selling exits here
Oct 17, 2026 – Nov 15, 2026

Exits seen per day

62 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
195.136.168.0/2402
195.136.169.0/2401

Proxy providers listing exits

  • 2Extract
  • Ake.net
  • BirdProxies
  • Byteful
  • EnigmaProxy
  • FastProxy
  • FlexyProxies
  • GSocks
  • Geonix
  • GonzoProxy
  • Infatica
  • LemonBright
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • RainProxy
  • Shifter
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
195.136.0.0/16
since May 2017
AS20804Residential1,541
72 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.168.0/221,024TEL-NAP_NETunknownASSIGNED PAOct 31, 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

Routing timeline

Covering aggregate above, the prefix's own history below

Summary

Routing history

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

History

Handoffs
1