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

77.93.2.0/24

8 residential-proxy exits · 30 days

JSC Balticom

Announcement
77.93.0.0/20
RPKI valid
Announced by
AS24651
Type
Residential
Risk
0 / 100 · Low
Proxy exits nearby

Residential-proxy exits

Proxy exits
8
3.1% of its addresses · 30 days
Always-on exits
4
50% of its exits
Providers
38
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

5.1K observations

Proxy providers listing exits

  • 2Captcha
  • 2Extract
  • AnyIP
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • Decodo
  • EnigmaProxy
  • Evomi
  • FastProxy
  • FlashProxy
  • GhostConnect
  • GonzoProxy
  • IPFly
  • IPOasis
  • IPPeak
  • Infatica
  • InfiniteProxies
  • LemonBright
  • LightningProxies
  • MangoProxy
  • NodeMaven
  • NovaProxy
  • Novada
  • Oxylabs
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • PuraRoute
  • Shifter
  • Thordata
  • ThunderProxy
  • VibeProxies
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
77.93.0.0/19
since May 2007
AS24651Residential183
37 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.0.0 - 77.93.5.2551,536LVBALTICOM-NETWORK-77-2"Balticom" JSCASSIGNED PANov 15, 2007abuse@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

AnnouncementRouting historyRPKI & IRRWhois & abuse
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.0 yr
Origin networks
1