Data as of Nov 16, 2026

185.150.56.0/22

3 residential-proxy exits · 30 days

Case Telecom B.V.

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

Residential-proxy exits

Proxy exits
3
0.29% of its addresses · 30 days
Spread
2 of 4
/24s with at least one exit
Providers
14
selling exits here
Oct 17, 2026 – Nov 15, 2026

Exits seen per day

102 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
185.150.57.0/2402
185.150.56.0/2401

Proxy providers listing exits

  • EnigmaProxy
  • FastProxy
  • IPFly
  • KocerRoxy
  • LemonBright
  • NovaProxy
  • Proxiware
  • Proxy302
  • ProxyEmpire
  • ProxyRack
  • PuraRoute
  • ThunderProxy
  • VantageProxies
  • 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.150.56.0/221,024NL-BITBUNKER-20160502Case Telecom B.V. (ORG-CTB5-RIPE) · NLALLOCATED PAMay 2, 2016info@bitbunker.nl
└ 185.150.56.0/24256CASE-INTERNET56unknownSUB-ALLOCATED PANov 19, 2019info@bitbunker.nl
via NL-BITBUNKER-20160502
└ 185.150.56.48/2816CASE-INTERNET-V125unknownASSIGNED PANov 19, 2019info@bitbunker.nl
via CASE-INTERNET56
└ 185.150.57.0/24256CASEINTERNETONLY57unknownASSIGNED PANov 19, 2019info@bitbunker.nl
via NL-BITBUNKER-20160502
└ 185.150.58.0/24256CASE-INTERNET58unknownASSIGNED PANov 19, 2019info@bitbunker.nl
via NL-BITBUNKER-20160502

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