Data as of Nov 14, 2026

185.26.56.0/22

11 residential-proxy exits · 30 days

DELTA Fiber Nederland B.V.

Announcement
this exact prefix
RPKI valid
Announced by
Type
Residential

Residential-proxy exits

Proxy exits
11
1.1% of its addresses · 30 days
Always-on exits
2
18% of its exits
Spread
2 of 4
/24s with at least one exit
Providers
46
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

17K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
185.26.57.0/2429
185.26.58.0/2402

Proxy providers listing exits

  • 2Extract
  • 711Proxy
  • Ake.net
  • AnyIP
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CatProxies
  • Decodo
  • EnigmaProxy
  • Evomi
  • FastProxy
  • FlashProxy
  • FloppyData
  • GSocks
  • Geonode
  • GoProxies
  • GonzoProxy
  • HPROXY
  • HideProxy
  • IPOasis
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • LemonBright
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • Oxylabs
  • PROXYSCRAPE
  • PrivateProxy
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • ProxyRack
  • ProxyWing
  • Proxyma
  • RainProxy
  • SPYDERPROXY_BASIC
  • Shifter
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VitalExclusive
  • 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.26.56.0/221,024NL-ZEELANDNET-20130515DELTA Fiber Nederland B.V. (ORG-ZB1-RIPE) · NLALLOCATED PAMay 15, 2013abuse@deltafiber.nl
└ 185.26.56.0/24256CBIZZ-FTTBFiber to the BusinessASSIGNED PAMay 16, 2013abuse@deltafiber.nl
via NL-ZEELANDNET-20130515
└ 185.26.57.0/24256CBIZZ-FTTBFiber to the BusinessASSIGNED PAMay 16, 2013abuse@deltafiber.nl
via NL-ZEELANDNET-20130515
└ 185.26.58.0/24256CBIZZ-FTTBFiber to the BusinessASSIGNED PAMay 16, 2013abuse@deltafiber.nl
via NL-ZEELANDNET-20130515
└ 185.26.59.0/24256CBIZZ-FTTBFiber to the BusinessASSIGNED PAMay 16, 2013abuse@deltafiber.nl
via NL-ZEELANDNET-20130515

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
Jul 2013
Current origin since
Jul 2013 · 13 yr
Origin networks
1