Data as of Nov 11, 2026

185.166.48.0/22

6 residential-proxy exits · 30 days

Stichting Ipse de Bruggen

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

Residential-proxy exits

Proxy exits
6
0.59% of its addresses · 30 days
Spread
1 of 4
/24s with at least one exit
Providers
26
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

88 observations

Proxy providers listing exits

  • 2Captcha
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • Decodo
  • FastProxy
  • FlashProxy
  • GonzoProxy
  • Infatica
  • LemonBright
  • LightningProxies
  • NodeMaven
  • Oxylabs
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyRack
  • Proxyma
  • Shifter
  • Thordata
  • ThunderProxy
  • VibeProxies
  • VitalExclusive
  • VitalProxy
  • 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.166.48.0/221,024NL-IPSEDEBRUGGEN-20160901Stichting Ipse de Bruggen (ORG-SIDB3-RIPE) · NLALLOCATED PASep 1, 2016abuse@ipsedebruggen.nl
└ 185.166.48.0/24256IPSEDEBRUGGENStichting Ipse de Bruggen: ProductionASSIGNED PAFeb 20, 2017abuse@ipsedebruggen.nl
via NL-IPSEDEBRUGGEN-20160901
└ 185.166.49.128/25128IPSEDEBRUGGENStichting Ipse de Bruggen: Development, Testing and AcceptanceASSIGNED PAFeb 21, 2017abuse@ipsedebruggen.nl
via NL-IPSEDEBRUGGEN-20160901
└ 185.166.50.0/24256IPSEDEBRUGGENStichting Ipse de Bruggen: Clients Point to PointASSIGNED PAFeb 21, 2017abuse@ipsedebruggen.nl
via NL-IPSEDEBRUGGEN-20160901
└ 185.166.51.0 - 185.166.51.2324IPSEDEBRUGGENStichting Ipse de Bruggen: Backbone - DCASSIGNED PAFeb 21, 2017abuse@ipsedebruggen.nl
via NL-IPSEDEBRUGGEN-20160901
└ 185.166.51.240/2816IPSEDEBRUGGENStichting Ipse de Bruggen: Backbone - CoreASSIGNED PAFeb 21, 2017abuse@ipsedebruggen.nl
via NL-IPSEDEBRUGGEN-20160901

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
Sep 2016
Current origin since
Dec 2016 · 9.9 yr
Origin networks
2
Last change of origin
Dec 2016
Recorded history

History

Handoffs
1