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

89.35.36.0/23

5 residential-proxy exits · 30 days

Ardalsnett AS

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

Residential-proxy exits

Proxy exits
5
0.98% of its addresses · 30 days
Always-on exits
1
20% of its exits
Spread
2 of 2
/24s with at least one exit
Providers
25
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

8.4K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
89.35.37.0/2414
89.35.36.0/2401

Proxy providers listing exits

  • 2Extract
  • 711Proxy
  • AnyIP
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • Decodo
  • Evomi
  • FlashProxy
  • FloppyData
  • GSocks
  • Geonode
  • GonzoProxy
  • Infatica
  • LemonBright
  • Oxylabs
  • Proxy-Seller
  • ProxyEmpire
  • ProxyRack
  • RainProxy
  • Shifter
  • StrikeProxy
  • Thordata
  • ThunderProxy

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.35.36.0/23512NO-ARDALSNETTAS-20051129Ardalsnett AS (ORG-AA520-RIPE) · NOALLOCATED PANov 10, 2020abuse@ardalsnett.no
└ 89.35.36.0/24256ARDALSNETT-CUSTOMERCustomer DHCP PoolASSIGNED PANov 11, 2020abuse@ardalsnett.no
via NO-ARDALSNETTAS-20051129
└ 89.35.37.0/24256ARDALSNETT-CUSTOMERCustomer DHCP PoolASSIGNED PANov 11, 2020abuse@ardalsnett.no
via NO-ARDALSNETTAS-20051129

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

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
May 2006
Current origin since
Aug 2021 · 5.3 yr
Origin networks
5
Last change of origin
Aug 2021
Recorded history

History

Handoffs
4