Data as of Nov 16, 2026

5.104.248.0/21

27 residential-proxy exits · 30 days

Oxylion Sp. z o.o.

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

Residential-proxy exits

Proxy exits
27
1.3% of its addresses · 30 days
Always-on exits
4
15% of its exits
Spread
8 of 8
/24s with at least one exit
Providers
64
selling exits here
Oct 17, 2026 – Nov 15, 2026

Exits seen per day

7.3K observations

/24s with the most always-on exits

Proxy providers listing exits

  • 2Captcha
  • 2Extract
  • 711Proxy
  • 9Proxy
  • Ake.net
  • AnyIP
  • B2Proxy
  • BartProxies
  • BirdProxies
  • BottingTools
  • BuyingProxy
  • ByteProxies
  • Byteful
  • CliProxy
  • DataImpulse
  • EnigmaProxy
  • Evomi
  • FLAMEPROXIES_BASIC
  • FastProxy
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GEEKPROXY_TURBO
  • GloryCloud
  • GoProxies
  • GonzoProxy
  • IPFly
  • IPOasis
  • IPPeak
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • KindProxy
  • KocerRoxy
  • Kookey
  • LemonBright
  • LightningProxies
  • MangoProxy
  • NextProxy
  • NiuProxy
  • NovaProxy
  • Novada
  • Proxiware
  • Proxy-Seller
  • Proxy302
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • ProxyWing
  • Proxyma
  • PuraRoute
  • RainProxy
  • RapidProxy
  • RolaProxy
  • Shifter
  • TalorData
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VibeProxies
  • VitalExclusive
  • VitalProxy
  • YumiProxy

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
5.104.248.0/212,048PL-OXYLION-20120703Oxylion Sp. z o.o. (ORG-OSA50-RIPE) · PLALLOCATED PAJul 3, 2012abuse@oxylion.pl
└ 5.104.248.0/221,024PL-RDIRDI Broadband ClientsASSIGNED PAAug 30, 2012abuse@oxylion.pl
via PL-OXYLION-20120703
└ 5.104.252.0/221,024PL-RDIRDI Broadband ClientsASSIGNED PAJun 3, 2013abuse@oxylion.pl
via PL-OXYLION-20120703

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
Sep 2012
Current origin since
Aug 2015 · 11 yr
Origin networks
2
Last change of origin
Aug 2015
Recorded history

History

Handoffs
1