LAYER3 INTEL
Get started
Sign in
Data as of Nov 13, 2026

86.100.22.0/24

11 residential-proxy exits · 30 days

UAB 'Balticum TV'

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

Residential-proxy exits

Proxy exits
11
4.3% of its addresses · 30 days
Always-on exits
1
9.1% of its exits
Providers
41
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

1.4K observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • AnyIP
  • BirdProxies
  • BottingTools
  • BuyingProxy
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • Evomi
  • FastProxy
  • FlashProxy
  • GSocks
  • Geonix
  • Geonode
  • GonzoProxy
  • IPOasis
  • IPPeak
  • Infatica
  • InfiniteProxies
  • LemonBright
  • LightningProxies
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • ProxyRack
  • Proxyma
  • RainProxy
  • Shifter
  • StrikeProxy
  • Thordata
  • VantageProxies
  • VibeProxies
  • VitalExclusive
  • VitalProxy

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.16.0/204,096BALTICUM-TV-KLPBalticum TV cable network (Klaipeda)ASSIGNED PAMay 26, 2005abuse@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

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Who has announced 86.100.0.0/17

86.100.0.0/17

Routing history

Pattern
Stable
First seen
Jun 2005
Current origin since
Apr 2006 · 21 yr
Origin networks
2
Last change of origin
Apr 2006
Recorded history

History

Handoffs
1