Data as of Nov 21, 2026

217.171.200.80/29

1 residential-proxy exit · 30 days

Monsternett AS

Announcement
No RPKI
Announced by
Type
Business
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
1
13% of its addresses · 30 days
Providers
26
selling exits here
Oct 22, 2026 – Nov 20, 2026

Exits seen per day

123 observations

Proxy providers listing exits

  • 2Extract
  • BirdProxies
  • BottingTools
  • Byteful
  • Decodo
  • FLAMEPROXIES_BASIC
  • FLAMEPROXIES_PREMIUM
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • HASDATA
  • Infatica
  • KocerRoxy
  • LemonBright
  • MangoProxy
  • NodeProxy
  • Oxylabs
  • PROXYLANE
  • PROXYSCRAPE
  • Proxy-Seller
  • Proxy302
  • Proxyma
  • SOTAPROXY
  • Shifter
  • Thordata
  • VitalExclusive

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
217.171.192.0/204,096NO-MONSTERNETT-20091002Monsternett AS (ORG-MA388-RIPE) · NOALLOCATED PAOct 2, 2009abuse@monsternett.no
└ 217.171.200.80/298MN-NO-HALDEN-CU122308CU122308, Halden, NorwayASSIGNED PAJan 3, 2011abuse@monsternett.no
via NO-MONSTERNETT-20091002

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 217.171.192.0/20

217.171.192.0/20

Routing history

Pattern
Stable
First seen
May 2005
Current origin since
Oct 2014 · 12 yr
Origin networks
3
Last change of origin
Oct 2014
Recorded history

History

Handoffs
2