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

178.23.100.0/23

5 residential-proxy exits · 30 days

Ardalsnett AS

Announcement
178.23.96.0/21
No RPKI
Announced by
AS197212
Type
Residential
Risk
0 / 100 · Low

Residential-proxy exits

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

Exits seen per day

302 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
178.23.100.0/2403
178.23.101.0/2402

Proxy providers listing exits

  • 2Extract
  • BirdProxies
  • ByteProxies
  • Byteful
  • EnigmaProxy
  • GSocks
  • IPFly
  • Infatica
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • Proxiware
  • ProxyEmpire
  • Proxyma
  • PuraRoute
  • RainProxy
  • Shifter
  • Thordata
  • VantageProxies
  • VitalExclusive

Registrations in this block

The registry's network records over this block, widest first, each under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
178.23.96.0/212,048NO-ARDALSNETTAS-20100422Ardalsnett AS (ORG-AA520-RIPE) · NOALLOCATED PAApr 22, 2010abuse@ardalsnett.no
└ 178.23.100.0/23512ARDALSNETT-CUSTOMERCustomer DHCP PoolASSIGNED PANov 8, 2010abuse@ardalsnett.no
via NO-ARDALSNETTAS-20100422

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 178.23.96.0/21

178.23.96.0/21

Routing history

Pattern
Stable
First seen
Nov 2010
Current origin since
Oct 2011 · 15 yr
Origin networks
2
Last change of origin
Oct 2011
Recorded history

History

Handoffs
1