Data as of Nov 11, 2026

212.178.136.0/22

5 residential-proxy exits · 30 days

Vodafone Libertel B.V.

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

Residential-proxy exits

Proxy exits
5
0.49% of its addresses · 30 days
Spread
2 of 4
/24s with at least one exit
Providers
25
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

175 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
212.178.138.0/2404
212.178.137.0/2401

Proxy providers listing exits

  • 2Extract
  • AnyIP
  • BlurPath
  • BottingTools
  • CliProxy
  • DataImpulse
  • EnigmaProxy
  • FastProxy
  • FloppyData
  • GSocks
  • IPFly
  • IPPeak
  • Infatica
  • Kookey
  • LemonBright
  • NovProxy
  • NovaProxy
  • Oxylabs
  • Proxiware
  • ProxyEmpire
  • ProxyRack
  • PuraRoute
  • RainProxy
  • TalorData
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
212.178.128.0/19
since Sep 2018
AS33915Business27
2 always on
Vodafone Libertel B.V.
via Ziggo

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
212.178.64.0 - 212.178.159.25524,576NL-TNF-19990623Vodafone Libertel B.V. (ORG-TNFB1-RIPE) · NLALLOCATED PAMay 1, 2026esabuse.nl@vodafoneziggo.com
└ 212.178.128.0/198,192ZIGGO-B2B-2ZiggoLIR-PARTITIONED PASep 9, 2010esabuse.nl@vodafoneziggo.com
via NL-TNF-19990623

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

Covering aggregate above, the prefix's own history below

212.178.128.0/20

Routing history

Pattern
Stable
First seen
Jul 2015
Current origin since
Sep 2018 · 8.2 yr
Origin networks
2
Last change of origin
Sep 2018
Recorded history

History

Handoffs
1