Data as of Nov 12, 2026

86.100.136.0/24

9 residential-proxy exits · 30 days

UAB 'Balticum TV'

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

Residential-proxy exits

Proxy exits
9
3.5% of its addresses · 30 days
Always-on exits
2
22% of its exits
Providers
37
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

2.7K observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 9Proxy
  • AnyIP
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • DataImpulse
  • Decodo
  • Evomi
  • FastProxy
  • FlashProxy
  • Geonode
  • GonzoProxy
  • IPOasis
  • Infatica
  • LemonBright
  • LightningProxies
  • MangoProxy
  • NodeMaven
  • NovaProxy
  • Oxylabs
  • Proxiware
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • Shifter
  • StrikeProxy
  • Thordata
  • ThunderProxy
  • VibeProxies
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
86.100.128.0/18
since Mar 2013
AS39007Residential237
29 always on
UAB "Balticum TV"

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
86.100.0.0/1665,536LT-BALTICUM-TV-20050523UAB "Balticum TV" (ORG-UT7-RIPE) · LTALLOCATED PAMay 23, 2005abuse@balticum-tv.lt
└ 86.100.128.0/204,096BALTICUM-TV-KLPBalticum TV network (Klaipeda)ASSIGNED PAApr 2, 2009abuse@balticum-tv.lt
via LT-BALTICUM-TV-20050523

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

86.100.128.0/19

Routing history

Pattern
Stable
First seen
Apr 2009
Current origin since
Apr 2009 · 18 yr
Origin networks
1