Data as of Nov 12, 2026

80.70.24.0/23

6 residential-proxy exits · 30 days

AS 'Latvenergo'

Announcement
this exact prefix
RPKI valid
Announced by
Type
Unknown
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
6
1.2% of its addresses · 30 days
Always-on exits
1
17% of its exits
Spread
2 of 2
/24s with at least one exit
Providers
34
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

5.7K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
80.70.24.0/2413
80.70.25.0/2403

Proxy providers listing exits

  • 711Proxy
  • AnyIP
  • BlurPath
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • Decodo
  • EnigmaProxy
  • Evomi
  • FlashProxy
  • Geonode
  • GoProxies
  • GonzoProxy
  • IPFly
  • IPPeak
  • IPRoyal
  • Infatica
  • LemonBright
  • MoMoProxy
  • NovProxy
  • NovaProxy
  • Oxylabs
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyRack
  • ProxyWing
  • PuraRoute
  • RainProxy
  • StrikeProxy
  • Thordata
  • VantageProxies
  • Webshare

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
80.70.16.0/20
since May 2005
AS29600Internet provider6
1 always on
AS "Latvenergo"

Registrations in this block

The registry's network records over the announcement: those covering it, widest first, then every record inside it, under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
80.70.16.0/204,096LV-LATVENERGO-20041217AS "Latvenergo" (ORG-LA13-RIPE) · LVALLOCATED PADec 17, 2004sakaru.dispecers@latvenergo.lv
└ 80.70.24.0/23512ForeversGForeverG-ViesiteASSIGNED PADec 27, 2011sakaru.dispecers@latvenergo.lv
via LV-LATVENERGO-20041217

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

Summary

Routing history

Pattern
Stable
First seen
Jan 2026
Current origin since
Jan 2026 · 10 mo
Origin networks
1