Data as of Nov 17, 2026

212.98.252.0/22

1 residential-proxy exit · 30 days

Vodafone Net Iletisim Hizmetler AS

Announcement
this exact prefix
RPKI valid
Announced by
Type
Residential

Residential-proxy exits

Proxy exits
1
0.10% of its addresses · 30 days
Spread
1 of 4
/24s with at least one exit
Providers
19
selling exits here
Oct 18, 2026 – Nov 16, 2026

Exits seen per day

108 observations

Proxy providers listing exits

  • 2Extract
  • BirdProxies
  • ByteProxies
  • Byteful
  • EnigmaProxy
  • GEEKPROXY_FLEX
  • GSocks
  • Geonix
  • Infatica
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • PROXYSCRAPE
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • Shifter
  • VantageProxies
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
212.98.240.0/20
since May 2010
AS15924Residential53
10 always on
Vodafone Net Iletisim Hizmetler AS
212.98.192.0/18
since May 2005
AS15924Residential373
95 always on
Vodafone Net Iletisim Hizmetler AS
More specific

Announcements inside

PrefixOriginTypeHolderRPKI
212.98.253.0/24
since Oct 2024
AS15924ResidentialVodafone Net Iletisim Hizmetler AS

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.98.192.0/1816,384TR-VFNET-990604Vodafone Net Iletisim Hizmetler AS (ORG-BIHA1-RIPE) · TRALLOCATED PAOct 24, 2002abuse@vodafone.net.tr
└ 212.98.252.0/24256SR-NBorusan Telekom Serial NetworkASSIGNED PAJan 8, 2004abuse@vodafone.net.tr
via TR-VFNET-990604
└ 212.98.253.0/24256CN-DMZBorusan Telekom Hosting NetworkASSIGNED PASep 18, 2002abuse@vodafone.net.tr
via TR-VFNET-990604
└ 212.98.254.0/24256BTelekom-DIALUP-STATIC-NETBorusan Telekom Static Dialup PoolASSIGNED PAJan 16, 2003abuse@vodafone.net.tr
via TR-VFNET-990604
└ 212.98.255.0/24256ESENTEPE-ROUTERS-NETIstanbul, TurkeyASSIGNED PAJan 17, 2003abuse@vodafone.net.tr
via TR-VFNET-990604

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

Summary

Routing history

Pattern
Stable
First seen
Apr 2007
Current origin since
Apr 2007 · 20 yr
Origin networks
1