Data as of Nov 20, 2026

185.20.168.0/22

4 residential-proxy exits · 30 days

Monsternett AS

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

Residential-proxy exits

Proxy exits
4
0.39% of its addresses · 30 days
Spread
2 of 4
/24s with at least one exit
Providers
13
selling exits here
Oct 21, 2026 – Nov 19, 2026

Exits seen per day

117 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
185.20.171.0/2403
185.20.170.0/2401

Proxy providers listing exits

  • BlurPath
  • CliProxy
  • FastProxy
  • IPFly
  • IPPeak
  • KocerRoxy
  • LemonBright
  • NovProxy
  • Proxiware
  • Proxy302
  • PuraRoute
  • ThunderProxy
  • VitalExclusive

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.20.168.0/221,024NO-MONSTERNETT-20130307Monsternett AS (ORG-MA388-RIPE) · NOALLOCATED PAMar 7, 2013abuse@monsternett.no
└ 185.20.168.0/24256NO-MONSTERNETT-NAS-CUSTBBMonsternett AS (ORG-MA388-RIPE) · NOASSIGNED PAFeb 7, 2017abuse@monsternett.no
└ 185.20.169.0/24256NO-MONSTERNETT-NAS-CUSTBBMonsternett AS (ORG-MA388-RIPE) · NOASSIGNED PAMay 25, 2018abuse@monsternett.no
└ 185.20.170.0/24256NO-MONSTERNETT-NAS-CUSTBBunknownASSIGNED PAJul 6, 2018abuse@monsternett.no
via NO-MONSTERNETT-20130307
└ 185.20.171.0/24256NO-MONSTERNETT-NAS-CUSTBBunknownASSIGNED PASep 30, 2022abuse@monsternett.no
via NO-MONSTERNETT-20130307

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
Mar 2013
Current origin since
Oct 2014 · 12 yr
Origin networks
2
Last change of origin
Oct 2014
Recorded history

History

Handoffs
1