LAYER3 INTEL
Get started
Sign in
Data as of Nov 13, 2026

212.158.0.0/17

3 residential-proxy exits · 30 days

Vodafone Global Network · space held by Vodafone Enterprise Equipment Limited

Announcement
this exact prefix
RPKI valid
Announced by
AS1273
Type
Mobile
Risk
10 / 100 · Low
Shared address

Residential-proxy exits

Proxy exits
3
<0.01% of its addresses · 30 days
Spread
3 of 128
/24s with at least one exit
Providers
7
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

99 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
212.158.0.0/2401
212.158.3.0/2401
212.158.56.0/2401

Proxy providers listing exits

  • AnyIP
  • BlurPath
  • Byteful
  • CliProxy
  • IPPeak
  • MoMoProxy
  • NovProxy

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
212.158.0.0/1732,768UK-VEEL-19990217Vodafone Enterprise Equipment Limited (ORG-VEEL1-RIPE) · GBALLOCATED PAJan 9, 2025ipabuse@vodafone.co.uk
└ 212.158.0.0/212,048VODAFONEAS1273 Customer WANsASSIGNED PAJan 14, 2026ipabuse@vodafone.co.uk
via UK-VEEL-19990217
└ 212.158.8.0/212,048VODAFONEAS1273 Customer WANsASSIGNED PAJan 14, 2026ipabuse@vodafone.co.uk
via UK-VEEL-19990217
└ 212.158.16.0/212,048VODAFONEAS1273 Customer WANsASSIGNED PAJan 14, 2026ipabuse@vodafone.co.uk
via UK-VEEL-19990217
└ 212.158.24.0/212,048VODAFONEAS1273 Customer WANsASSIGNED PAJan 14, 2026ipabuse@vodafone.co.uk
via UK-VEEL-19990217
└ 212.158.32.0/212,048VODAFONEAS1273 Customer WANsASSIGNED PAJan 14, 2026ipabuse@vodafone.co.uk
via UK-VEEL-19990217
└ 212.158.40.0/212,048VODAFONEAS1273 Customer WANsASSIGNED PAJan 14, 2026ipabuse@vodafone.co.uk
via UK-VEEL-19990217
└ 212.158.48.0/212,048VODAFONEAS1273 Customer WANsASSIGNED PAJan 14, 2026ipabuse@vodafone.co.uk
via UK-VEEL-19990217
└ 212.158.56.0/212,048VODAFONEAS1273 Customer WANsASSIGNED PAJan 14, 2026ipabuse@vodafone.co.uk
via UK-VEEL-19990217
└ 212.158.64.0/212,048VODAFONEAS1273 Customer WANsASSIGNED PAJan 14, 2026ipabuse@vodafone.co.uk
via UK-VEEL-19990217
└ 212.158.72.0/212,048VODAFONEAS1273 Customer WANsASSIGNED PAJan 14, 2026ipabuse@vodafone.co.uk
via UK-VEEL-19990217
└ 212.158.80.0/212,048VODAFONEAS1273 Customer WANsASSIGNED PAJan 14, 2026ipabuse@vodafone.co.uk
via UK-VEEL-19990217
└ 212.158.88.0/212,048VODAFONEAS1273 Customer WANsASSIGNED PAJan 14, 2026ipabuse@vodafone.co.uk
via UK-VEEL-19990217
└ 212.158.96.0/212,048VODAFONEAS1273 Customer WANsASSIGNED PAJan 14, 2026ipabuse@vodafone.co.uk
via UK-VEEL-19990217
└ 212.158.104.0/212,048VODAFONEAS1273 Customer WANsASSIGNED PAJan 14, 2026ipabuse@vodafone.co.uk
via UK-VEEL-19990217
└ 212.158.112.0/212,048VODAFONEAS1273 Customer WANsASSIGNED PAJan 14, 2026ipabuse@vodafone.co.uk
via UK-VEEL-19990217
└ 212.158.120.0/212,048VODAFONEAS1273 Customer WANsASSIGNED PAJan 14, 2026ipabuse@vodafone.co.uk
via UK-VEEL-19990217

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

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
May 2005
Current origin since
Jun 2006 · 20 yr
Origin networks
2
Last change of origin
Jun 2006
Recorded history

History

Handoffs
1