Data as of Nov 18, 2026

213.34.183.0/28

No anonymizer space · no proxy exits in 30 days

Vodafone Libertel B.V.

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

Residential-proxy exits

Proxy exits
3
19% of its addresses · listed by providers
Providers
7
selling exits here

Proxy providers listing exits

  • Evomi
  • FloppyData
  • Geonode
  • InfiniteProxies
  • LemonBright
  • RainProxy
  • Shifter

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
213.34.160.0/19
since Sep 2018
AS33915Mobile19
2 always on
Vodafone Libertel B.V.

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
213.34.64.0 - 213.34.191.25532,768NL-TNF-19990917Vodafone Libertel B.V. (ORG-TNFB1-RIPE) · NLALLOCATED PAJul 7, 2026esabuse.nl@vodafoneziggo.com
└ 213.34.180.0/221,024ZIGGO-B2B-ASD-1B2B AmsterdamLIR-PARTITIONED PAMay 20, 2011esabuse.nl@vodafoneziggo.com
via NL-TNF-19990917
└ 213.34.183.0/2816GEMEENTE_EMMEN_GTVGemeente Emmen GTVASSIGNED PAOct 21, 2020esabuse.nl@vodafoneziggo.com
via ZIGGO-B2B-ASD-1

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

213.34.176.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