Data as of Nov 18, 2026

88.223.0.0/20

2 residential-proxy exits · 30 days

UAB Init

Announcement
this exact prefix
RPKI valid
Announced by
Type
Residential
Risk
0 / 100 · Low

Residential-proxy exits

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

Exits seen per day

506 observations

Proxy providers listing exits

  • 711Proxy
  • ASHBURNPROXIES
  • Ake.net
  • B2Proxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • Decodo
  • EZProxies
  • EnigmaProxy
  • FlashProxy
  • GonzoProxy
  • IPFly
  • IPOasis
  • IPPeak
  • Infatica
  • LightningProxies
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • Proxio
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyRack
  • Proxyma
  • PuraRoute
  • Shifter
  • StrikeProxy
  • VibeProxies
  • VitalData
  • VitalExclusive
  • ZENPROXY_PREMIUM

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
88.222.0.0/15131,072LT-INIT-20060207UAB Init (ORG-IC1-RIPE) · LTALLOCATED PAFeb 7, 2006abuse@init.lt
└ 88.223.2.0/23512dpp-knskns dpp dynamic IP addr poolASSIGNED PASep 23, 2025abuse@init.lt
via LT-INIT-20060207
└ 88.223.4.0 - 88.223.15.2553,072MGNT-VLN-LTMGNT Vln area2 networkASSIGNED PASep 23, 2025abuse@init.lt
via LT-INIT-20060207

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
Apr 2025
Current origin since
Apr 2025 · 1.6 yr
Origin networks
1