Data as of Nov 12, 2026

89.10.0.0/17

150 residential-proxy exits · 30 days

NextGenTel AS

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

Residential-proxy exits

Proxy exits
150
0.46% of its addresses · 30 days
Always-on exits
9
6.0% of its exits
Spread
50 of 128
/24s with at least one exit
Providers
81
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

32K observations

Proxy providers listing exits

  • 2Captcha
  • 2Extract
  • 711Proxy
  • 9Proxy
  • Ake.net
  • AnyIP
  • B2Proxy
  • BartProxies
  • BirdProxies
  • BottingTools
  • BuyingProxy
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • CoreProxy
  • DataImpulse
  • Datarama
  • Decodo
  • EnigmaProxy
  • Evomi
  • FLEETPROXY
  • FastProxy
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GSocks
  • Geonix
  • Geonode
  • GonzoProxy
  • HideProxy
  • HydraProxy
  • IPFly
  • IPOasis
  • IPPeak
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • KocerRoxy
  • Kookey
  • LemonBright
  • LightningProxies
  • LudaxProxy
  • MangoProxy
  • MoMoProxy
  • NextProxy
  • NodeMaven
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • ProxiesVision
  • Proxiware
  • Proxy-Seller
  • Proxy302
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • ProxyRack
  • ProxyWing
  • Proxying
  • Proxyma
  • PuraRoute
  • RainProxy
  • RapidProxy
  • SPYDERPROXY_PREMIUM
  • Shifter
  • Smartproxy
  • StrikeProxy
  • TORCHPROXIES_X
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VibeProxies
  • VitalExclusive
  • VitalProxy
  • Webshare
  • YumiProxy
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
89.10.0.0/16
since Oct 2021
AS15659Residential458
28 always on
NextGenTel AS

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
89.10.0.0 - 89.11.127.25598,304NO-NEXTGENTEL-20060629NextGenTel AS (ORG-NA36-RIPE) · NOALLOCATED PADec 7, 2021abuse@nextgentel.com
└ 89.10.4.0/221,024NEXTGENTEL-NOXDSL access and service provider in NorwayASSIGNED PAJun 18, 2013abuse@nextgentel.com
via NO-NEXTGENTEL-20060629
└ 89.10.8.0/23512NEXTGENTEL-NOXDSL access and service provider in NorwayASSIGNED PAJun 1, 2011abuse@nextgentel.com
via NO-NEXTGENTEL-20060629
└ 89.10.10.0/24256NEXTGENTEL-NOXDSL access and service provider in NorwayASSIGNED PAJun 1, 2011abuse@nextgentel.com
via NO-NEXTGENTEL-20060629
└ 89.10.11.0 - 89.10.12.255512NEXTGENTEL-NOXDSL access and service provider in NorwayASSIGNED PAApr 16, 2008abuse@nextgentel.com
via NO-NEXTGENTEL-20060629
└ 89.10.13.0 - 89.10.14.255512NEXTGENTEL-NOXDSL access and service provider in NorwayASSIGNED PAFeb 28, 2008abuse@nextgentel.com
via NO-NEXTGENTEL-20060629
└ 89.10.15.0/24256NEXTGENTEL-NOXDSL access and service provider in NorwayASSIGNED PADec 5, 2012abuse@nextgentel.com
via NO-NEXTGENTEL-20060629
└ 89.10.16.0/221,024NEXTGENTEL-NOXDSL access and service provider in NorwayASSIGNED PAJul 5, 2013abuse@nextgentel.com
via NO-NEXTGENTEL-20060629
└ 89.10.20.0/221,024NEXTGENTEL-NOXDSL access and service provider in NorwayASSIGNED PAAug 13, 2015abuse@nextgentel.com
via NO-NEXTGENTEL-20060629
└ 89.10.24.0/221,024NEXTGENTEL-NOXDSL access and service provider in NorwayASSIGNED PAJun 1, 2016abuse@nextgentel.com
via NO-NEXTGENTEL-20060629
└ 89.10.28.0/23512NEXTGENTEL-NOXDSL access and service provider in NorwayASSIGNED PAMar 14, 2017abuse@nextgentel.com
via NO-NEXTGENTEL-20060629
└ 89.10.30.0/23512NEXTGENTEL-NOXDSL access and service provider in NorwayASSIGNED PAApr 28, 2016abuse@nextgentel.com
via NO-NEXTGENTEL-20060629
└ 89.10.32.0/221,024NEXTGENTEL-NOXDSL access and service provider in NorwayASSIGNED PAMar 30, 2017abuse@nextgentel.com
via NO-NEXTGENTEL-20060629
└ 89.10.36.0/221,024NEXTGENTEL-NOXDSL access and service provider in NorwayASSIGNED PASep 6, 2018abuse@nextgentel.com
via NO-NEXTGENTEL-20060629
└ 89.10.40.0/24256NEXTGENTEL-NOXDSL access and service provider in NorwayASSIGNED PAMar 1, 2019abuse@nextgentel.com
via NO-NEXTGENTEL-20060629
└ 89.10.44.0/221,024NEXTGENTEL-NOXDSL access and service provider in NorwayASSIGNED PAJul 3, 2020abuse@nextgentel.com
via NO-NEXTGENTEL-20060629
└ 89.10.48.0/204,096NEXTGENTEL-NOXDSL access and service provider in NorwayASSIGNED PAMay 19, 2015abuse@nextgentel.com
via NO-NEXTGENTEL-20060629
└ 89.10.64.0/212,048NEXTGENTEL-NOXDSL access and service provider in NorwayASSIGNED PAOct 4, 2013abuse@nextgentel.com
via NO-NEXTGENTEL-20060629
└ 89.10.72.0/212,048NEXTGENTEL-NOXDSL access and service provider in NorwayASSIGNED PAOct 4, 2013abuse@nextgentel.com
via NO-NEXTGENTEL-20060629
└ 89.10.80.0/212,048NEXTGENTEL-NOXDSL access and service provider in NorwayASSIGNED PAOct 4, 2013abuse@nextgentel.com
via NO-NEXTGENTEL-20060629
└ 89.10.88.0/212,048NEXTGENTEL-NOXDSL access and service provider in NorwayASSIGNED PAOct 4, 2013abuse@nextgentel.com
via NO-NEXTGENTEL-20060629
└ 89.10.96.0/212,048NEXTGENTEL-NOXDSL access and service provider in NorwayASSIGNED PANov 8, 2006abuse@nextgentel.com
via NO-NEXTGENTEL-20060629
└ 89.10.104.0/221,024NEXTGENTEL-NOXDSL access and service provider in NorwayASSIGNED PAJul 4, 2007abuse@nextgentel.com
via NO-NEXTGENTEL-20060629
└ 89.10.108.0/221,024NEXTGENTEL-NOXDSL access and service provider in NorwayASSIGNED PASep 5, 2007abuse@nextgentel.com
via NO-NEXTGENTEL-20060629
└ 89.10.112.0/221,024NEXTGENTEL-NOXDSL access and service provider in NorwayASSIGNED PASep 12, 2007abuse@nextgentel.com
via NO-NEXTGENTEL-20060629
└ 89.10.116.0/23512NEXTGENTEL-NOXDSL access and service provider in NorwayASSIGNED PAOct 16, 2007abuse@nextgentel.com
via NO-NEXTGENTEL-20060629
└ 89.10.118.0/23512NEXTGENTEL-NOXDSL access and service provider in NorwayASSIGNED PANov 26, 2007abuse@nextgentel.com
via NO-NEXTGENTEL-20060629
└ 89.10.120.0/23512NEXTGENTEL-NOXDSL access and service provider in NorwayASSIGNED PAJan 23, 2008abuse@nextgentel.com
via NO-NEXTGENTEL-20060629

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
Apr 2026
Current origin since
Apr 2026 · 7 mo
Origin networks
1