Data as of Nov 13, 2026

185.4.36.0/22

1 residential-proxy exit · 30 days

Zones AS

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

Residential-proxy exits

Proxy exits
1
0.10% of its addresses · 30 days
Spread
1 of 4
/24s with at least one exit
Providers
1
selling exits here
Oct 14, 2026 – Nov 11, 2026

Exits seen per day

8 observations

Proxy providers listing exits

  • Thordata

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.4.36.0/221,024NO-ZONES-20120925Zones AS (ORG-ZA41-RIPE) · NOALLOCATED PASep 25, 2012kjetil@zones.no
└ 185.4.36.0/23512Kundenett-07unknownSUB-ALLOCATED PASep 23, 2022kjetil@zones.no
via NO-ZONES-20120925
└ 185.4.36.0/24256NO-ZONES_NETWORKunknownASSIGNED PASep 23, 2022kjetil@zones.no
via Kundenett-07
└ 185.4.37.0/2732NO-ZONES_COREunknownASSIGNED PASep 23, 2022kjetil@zones.no
via Kundenett-07
└ 185.4.37.32/2732NO-ZONES_COREunknownASSIGNED PASep 23, 2022kjetil@zones.no
via Kundenett-07
└ 185.4.37.64/2732NO-ZONES_COREunknownASSIGNED PASep 23, 2022kjetil@zones.no
via Kundenett-07
└ 185.4.37.128/25128NO-ZONES_NETWORKunknownASSIGNED PASep 23, 2022kjetil@zones.no
via Kundenett-07
└ 185.4.38.0/23512Kundenett-08unknownSUB-ALLOCATED PASep 23, 2022kjetil@zones.no
via NO-ZONES-20120925

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
Apr 2016
Current origin since
Apr 2016 · 11 yr
Origin networks
1