Data as of Nov 18, 2026

213.192.96.0/20

5 residential-proxy exits · 30 days

Technical University of Gdansk, Academic Computer Center TASK

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

Residential-proxy exits

Proxy exits
5
0.12% of its addresses · 30 days
Always-on exits
1
20% of its exits
Spread
2 of 16
/24s with at least one exit
Providers
43
selling exits here
Oct 19, 2026 – Nov 17, 2026

Exits seen per day

4.1K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
213.192.104.0/2413
213.192.98.0/2402

Proxy providers listing exits

  • 2Extract
  • Ake.net
  • AnyIP
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • DataImpulse
  • EVOPROXY
  • EnigmaProxy
  • FLAMEPROXIES_BASIC
  • FLAMEPROXIES_PREMIUM
  • FloppyData
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • GonzoProxy
  • HydraProxy
  • INSTANTSOCKS_BASIC
  • IPOasis
  • IPPeak
  • Infatica
  • LemonBright
  • MagneticProxy
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • PROXIES.RIP
  • PROXYCOVE
  • PROXYLANE
  • PROXYSCRAPE
  • PacketStream
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • SCRAPELESS
  • SOTAPROXY
  • Shifter
  • VitalData
  • VitalExclusive
  • VitalProxy

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
213.192.64.0/1816,384PL-TASK-20001024Technical University of Gdansk, Academic Computer Center TASK (ORG-TUOG1-RIPE) · PLALLOCATED PA—abuse@task.gda.pl
└ 213.192.98.0/24256VLMEDIAunknownASSIGNED PAApr 22, 2021abuse@task.gda.pl
via PL-TASK-20001024
└ 213.192.100.0/221,024PRO-SYSTEMSchmetterlingASSIGNED PAJun 10, 2022abuse@task.gda.pl
via PL-TASK-20001024
└ 213.192.104.0/23512PPNT-NETPPNT GdyniaASSIGNED PAJun 10, 2022abuse@task.gda.pl
via PL-TASK-20001024

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

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
May 2006
Current origin since
May 2006 · 21 yr
Origin networks
1