Data as of Nov 11, 2026

178.209.26.0/24

17 residential-proxy exits · 30 days

Telemach BH d.o.o. Sarajevo

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

Residential-proxy exits

Proxy exits
17
6.6% of its addresses · 30 days
Providers
48
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

699 observations

Proxy providers listing exits

  • 711Proxy
  • AnyIP
  • B2Proxy
  • BlurPath
  • Byteful
  • CatProxies
  • CliProxy
  • DataImpulse
  • Decodo
  • EVOPROXY
  • EZProxies
  • FastProxy
  • GSocks
  • Geonix
  • GloryCloud
  • HideProxy
  • IPFly
  • IPPeak
  • IPRoyal
  • Infatica
  • KindProxy
  • Kookey
  • LemonBright
  • LudaxProxy
  • MangoProxy
  • MoMoProxy
  • NextProxy
  • NodeProxy
  • NovProxy
  • PrivateByte
  • ProxiesVision
  • Proxio
  • Proxmint
  • Proxy4U
  • ProxyGeo
  • ProxyRack
  • ProxyWing
  • Proxying
  • PuraRoute
  • Q2IP
  • RainProxy
  • RapidProxy
  • Shifter
  • SwiftProxy
  • TORCHPROXIES_BASIC
  • TORCHPROXIES_PREMIUM
  • Thordata
  • ThunderProxy

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
178.209.0.0/198,192BA-TELEMACH-20100428Telemach BH d.o.o. Sarajevo (ORG-GA121-RIPE) · BAALLOCATED PASep 30, 2016abuse@telemach.ba
└ 178.209.16.0/204,096TELEMACH-BHCable Modem Customers (CPE)ASSIGNED PASep 23, 2017abuse@telemach.ba
via BA-TELEMACH-20100428

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

178.209.0.0/19

Routing history

Pattern
Stable
First seen
May 2010
Current origin since
Mar 2017 · 9.6 yr
Origin networks
3
Last change of origin
Mar 2017
Recorded history

History

Handoffs
3