Data as of Nov 12, 2026

185.210.4.0/22

2 residential-proxy exits · 30 days

Ardalsnett AS

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

Residential-proxy exits

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

Exits seen per day

1.2K observations

Proxy providers listing exits

  • BottingTools
  • Decodo
  • LemonBright
  • Oxylabs
  • StrikeProxy
  • Thordata
  • Webshare

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.210.4.0/221,024NO-ARDALSNETT-20170623Ardalsnett AS (ORG-AA1828-RIPE) · NOALLOCATED PAJun 23, 2017abuse@ardalsnett.no
└ 185.210.4.0/24256ARDALSNETT-CUSTOMERCustomer DHCP PoolASSIGNED PANov 10, 2020abuse@ardalsnett.no
via NO-ARDALSNETT-20170623
└ 185.210.5.0/24256ARDALSNETT-CUSTOMERCustomer DHCP PoolASSIGNED PANov 10, 2020abuse@ardalsnett.no
via NO-ARDALSNETT-20170623
└ 185.210.6.0/24256ARDALSNETT-CUSTOMERCustomer DHCP PoolASSIGNED PANov 10, 2020abuse@ardalsnett.no
via NO-ARDALSNETT-20170623
└ 185.210.7.0/24256ARDALSNETT-CUSTOMERCustomer DHCP PoolASSIGNED PANov 10, 2020abuse@ardalsnett.no
via NO-ARDALSNETT-20170623

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
Jul 2017
Current origin since
Jul 2017 · 9.3 yr
Origin networks
1