Data as of Nov 12, 2026

77.93.9.0/24

8 residential-proxy exits · 30 days

JSC Balticom

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

Residential-proxy exits

Proxy exits
8
3.1% of its addresses · 30 days
Always-on exits
2
25% of its exits
Providers
34
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

2.9K observations

Proxy providers listing exits

  • 2Captcha
  • 9Proxy
  • Ake.net
  • AnyIP
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • Evomi
  • FastProxy
  • FlashProxy
  • Geonix
  • Geonode
  • GonzoProxy
  • IPOasis
  • Infatica
  • InfiniteProxies
  • LemonBright
  • LightningProxies
  • NodeMaven
  • Novada
  • Oxylabs
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyRack
  • Proxyma
  • Shifter
  • Thordata
  • ThunderProxy
  • VibeProxies
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
77.93.0.0/19
since May 2007
AS24651Residential187
31 always on
JSC Balticom

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
77.93.0.0/198,192LV-BALTICOM-20070511JSC Balticom (ORG-JB1-RIPE) · LVALLOCATED PAMay 11, 2007abuse@balticom.info
└ 77.93.8.0 - 77.93.10.255768LVBALTICOM-NETWORK-77-8"Balticom" JSCASSIGNED PANov 5, 2010abuse@balticom.info
via LV-BALTICOM-20070511

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

77.93.0.0/20

Routing history

Pattern
Stable
First seen
Oct 2021
Current origin since
Oct 2021 · 5.1 yr
Origin networks
1