Data as of Nov 11, 2026

212.16.149.0/24

20 residential-proxy exits · 30 days

Tarr Kft.

Announcement
RPKI valid
Announced by
Type
Residential
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
20
7.8% of its addresses · 30 days
Always-on exits
1
5.0% of its exits
Providers
42
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

1.1K observations

Proxy providers listing exits

  • Ake.net
  • AnyIP
  • BartProxies
  • BirdProxies
  • ByteProxies
  • Byteful
  • CliProxy
  • DataImpulse
  • EVOPROXY
  • EnigmaProxy
  • FastProxy
  • GSocks
  • GloryCloud
  • IPFly
  • IPMUSK
  • IPPeak
  • Infatica
  • KindProxy
  • LemonBright
  • LudaxProxy
  • MangoProxy
  • MoMoProxy
  • NiuProxy
  • NodeProxy
  • NovaProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyWing
  • Proxyma
  • PuraRoute
  • RainProxy
  • RapidProxy
  • Shifter
  • SwiftProxy
  • TORCHPROXIES_BASIC
  • TORCHPROXIES_PREMIUM
  • ThunderProxy
  • VantageProxies
  • VitalExclusive
  • ZENPROXY_LITE
  • ZENPROXY_PREMIUM

Registrations in this block

The registry's network records over this block, widest first, each under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
212.16.128.0/198,192HU-TARR-20071108Tarr Kft. (ORG-TK9-RIPE) · HUALLOCATED PANov 8, 2007abuse@tolna.net
└ 212.16.148.0 - 212.16.155.2552,048TARR-CABLEPOOL-200808Tarr Ltd.ASSIGNED PADec 20, 2008abuse@tolna.net
via HU-TARR-20071108

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 212.16.128.0/19

212.16.128.0/19

Routing history

Pattern
Stable
First seen
Nov 2007
Current origin since
Nov 2007 · 19 yr
Origin networks
1