Data as of Nov 14, 2026

213.91.124.0/24

21 residential-proxy exits · 30 days

TXTV d.o.o. Tuzla

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

Residential-proxy exits

Proxy exits
21
8.2% of its addresses · 30 days
Always-on exits
3
14% of its exits
Providers
72
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

11K observations

Proxy providers listing exits

  • 711Proxy
  • Ake.net
  • AnyIP
  • B2Proxy
  • BirdProxies
  • BlurPath
  • BottingTools
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • DataImpulse
  • Decodo
  • EVOPROXY
  • EnigmaProxy
  • Evomi
  • FLEETPROXY
  • FastProxy
  • FlashProxy
  • GSocks
  • Geonode
  • GloryCloud
  • GonzoProxy
  • IPFly
  • IPOasis
  • IPPeak
  • IPRoyal
  • Infatica
  • KindProxy
  • Kookey
  • LemonBright
  • LightningProxies
  • LudaxProxy
  • MangoProxy
  • MoMoProxy
  • NextProxy
  • NiuProxy
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXYSCRAPE
  • PYPROXY
  • Proxiware
  • Proxmint
  • Proxy-Seller
  • Proxy302
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • ProxyRack
  • Proxyma
  • PuraRoute
  • Q2IP
  • RH7Proxy
  • RainProxy
  • RapidProxy
  • RoamProxy
  • SPYDERPROXY_PREMIUM
  • Shifter
  • SwiftProxy
  • Thordata
  • ThunderProxy
  • TrueProxies
  • VantageProxies
  • VitalData
  • VitalExclusive
  • Webshare
  • ZENPROXY_LITE
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
213.91.112.0/20
since Oct 2017
AS202632Residential200
17 always on
TXTV d.o.o. Tuzla

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.91.112.0/204,096BA-TXTV-20050311TXTV d.o.o. Tuzla (ORG-TDT1-RIPE) · BAALLOCATED PAFeb 7, 2017abuse@txtv-tz.com
└ 213.91.124.0/24256ORG-TDT1-RIPEunknownASSIGNED PAOct 18, 2017abuse@txtv-tz.com
via BA-TXTV-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

Routing timeline

Covering aggregate above, the prefix's own history below

Summary

Routing history

Pattern
Stable
First seen
Nov 2017
Current origin since
Nov 2017 · 9.0 yr
Origin networks
1