Data as of Nov 20, 2026

185.24.188.0/22

13 residential-proxy exits · 30 days

Neas Energi Telekom AS

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

Residential-proxy exits

Proxy exits
13
1.3% of its addresses · 30 days
Always-on exits
2
15% of its exits
Spread
4 of 4
/24s with at least one exit
Providers
46
selling exits here
Oct 21, 2026 – Nov 19, 2026

Exits seen per day

12K observations

/24s with the most always-on exits

Proxy providers listing exits

  • 2Extract
  • 711Proxy
  • AETHYN_ELITE
  • Ake.net
  • B2Proxy
  • BirdProxies
  • BottingTools
  • Byteful
  • DataImpulse
  • Decodo
  • EVOPROXY
  • EnigmaProxy
  • FastProxy
  • FloppyData
  • GSocks
  • Geonix
  • IPFly
  • IPPeak
  • Infatica
  • KocerRoxy
  • LOKIPROXY
  • LemonBright
  • LemonLabs
  • LudaxProxy
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • Oxylabs
  • PROXIWARE_ECO
  • PYPROXY
  • Proxiware
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • Proxyma
  • PuraRoute
  • Q2IP
  • RainProxy
  • SPYDERPROXY_PREMIUM
  • Shifter
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VitalExclusive
  • YumiProxy
  • ZENPROXY_LITE

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
185.24.188.0/221,024NO-NONEAS-20130423Neas Energi Telekom AS (ORG-NEA2-RIPE) · NOALLOCATED PAApr 23, 2013abuse@neas.mr.no
└ 185.24.188.0/24256FBB-CUSTOMERNET-1Fraena Breiband ASASSIGNED PAOct 17, 2013abuse@neas.mr.no
via NO-NONEAS-20130423
└ 185.24.189.0/24256FBB-CUSTOMER-1850241890Fraena Breiband ASASSIGNED PASep 5, 2014abuse@neas.mr.no
via NO-NONEAS-20130423
└ 185.24.190.0/24256FBB-CUSTOMER-1850241900Fraena Breiband ASASSIGNED PASep 5, 2014abuse@neas.mr.no
via NO-NONEAS-20130423
└ 185.24.191.0/24256FBB-CUSTOMER-1850241910Fraena Breiband ASASSIGNED PASep 5, 2014abuse@neas.mr.no
via NO-NONEAS-20130423

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

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
Nov 2013
Current origin since
Dec 2014 · 12 yr
Origin networks
2
Last change of origin
Dec 2014
Recorded history

History

Handoffs
1