Data as of Nov 19, 2026

81.248.16.0/20

53 residential-proxy exits · 30 days

Orange S.A.

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

Residential-proxy exits

Proxy exits
53
1.3% of its addresses · 30 days
Always-on exits
2
3.8% of its exits
Spread
15 of 16
/24s with at least one exit
Providers
76
selling exits here
Oct 20, 2026 – Nov 18, 2026

Exits seen per day

20K observations

Proxy providers listing exits

  • 711Proxy
  • 9HTTP
  • 9Proxy
  • Ake.net
  • AnyIP
  • BirdProxies
  • BlurPath
  • BottingTools
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • CoreProxy
  • DataImpulse
  • Decodo
  • EVOPROXY
  • EnigmaProxy
  • Evomi
  • FastProxy
  • FlashProxy
  • GSocks
  • GeekProxy
  • Geonix
  • Geonode
  • GloryCloud
  • GoProxies
  • GonzoProxy
  • IPFly
  • IPPeak
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • KindProxy
  • KocerRoxy
  • LemonBright
  • LemonLabs
  • LemonPrime
  • LudaxProxy
  • MagneticProxy
  • MangoProxy
  • MarsProxies
  • MoMoProxy
  • NextProxy
  • NiuProxy
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXYCOVE
  • PSBProxy
  • PrivateByte
  • Proxies.fo
  • Proxiware
  • Proxmint
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyRack
  • ProxyWing
  • Proxyma
  • PuraRoute
  • Q2IP
  • RH7Proxy
  • RainProxy
  • RapidProxy
  • RoamProxy
  • SPYDERPROXY_PREMIUM
  • Shifter
  • SwiftProxy
  • Thordata
  • ThunderProxy
  • VProxy
  • VantageProxies
  • VitalExclusive

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
81.248.0.0/13524,288FR-TELECOM-20030213Orange S.A. (ORG-FT2-RIPE) · FRALLOCATED PAFeb 13, 2003gestionip.ft@orange.com
└ 81.248.16.0/24256IP2000-ADSL-BASLNPAP656 Pointe a Pitre Bloc 1ASSIGNED PANov 16, 2005gestionip.ft@orange.com
via FR-TELECOM-20030213
└ 81.248.17.0/24256IP2000-ADSL-BASLNPAP656 Pointe a Pitre Bloc 1ASSIGNED PAMar 26, 2003gestionip.ft@orange.com
via FR-TELECOM-20030213
└ 81.248.18.0/24256IP2000-ADSL-BASLNPAP656 Pointe a Pitre Bloc 1ASSIGNED PAJan 7, 2005gestionip.ft@orange.com
via FR-TELECOM-20030213
└ 81.248.19.0/24256IP2000-ADSL-BASLNPAP656 Pointe a Pitre Bloc 1ASSIGNED PAJun 28, 2005gestionip.ft@orange.com
via FR-TELECOM-20030213
└ 81.248.20.0/24256IP2000-ADSL-BASLNPAP656 Pointe a Pitre Bloc 1ASSIGNED PAJan 9, 2008gestionip.ft@orange.com
via FR-TELECOM-20030213
└ 81.248.21.0/24256IP2000-ADSL-BASLNPAP656 Pointe a Pitre Bloc 1ASSIGNED PAJul 16, 2009gestionip.ft@orange.com
via FR-TELECOM-20030213
└ 81.248.22.0/24256IP2000-ADSL-BASLNPAP656 Pointe a Pitre Bloc 1ASSIGNED PAJul 16, 2009gestionip.ft@orange.com
via FR-TELECOM-20030213
└ 81.248.23.0/24256IP2000-ADSL-BASLNPAP656 Pointe a Pitre Bloc 1ASSIGNED PAJul 16, 2009gestionip.ft@orange.com
via FR-TELECOM-20030213
└ 81.248.24.0/24256IP2000-ADSL-BASLNPAP656 Pointe a Pitre Bloc 2ASSIGNED PAFeb 9, 2005gestionip.ft@orange.com
via FR-TELECOM-20030213
└ 81.248.25.0/24256IP2000-ADSL-BASLNPAP656 Pointe a Pitre Bloc 2ASSIGNED PAMar 26, 2003gestionip.ft@orange.com
via FR-TELECOM-20030213
└ 81.248.26.0/24256IP2000-ADSL-BASLNPAP656 Pointe a Pitre Bloc 2ASSIGNED PAJan 7, 2005gestionip.ft@orange.com
via FR-TELECOM-20030213
└ 81.248.27.0/24256IP2000-ADSL-BASLNPAP656 Pointe a Pitre Bloc 2ASSIGNED PAJan 7, 2005gestionip.ft@orange.com
via FR-TELECOM-20030213
└ 81.248.28.0/24256IP2000-ADSL-BASLNPAP656 Pointe a Pitre Bloc 2ASSIGNED PAJun 28, 2005gestionip.ft@orange.com
via FR-TELECOM-20030213
└ 81.248.29.0/24256IP2000-ADSL-BASLNPAP656 Pointe a Pitre Bloc 1ASSIGNED PASep 30, 2005gestionip.ft@orange.com
via FR-TELECOM-20030213
└ 81.248.30.0/24256IP2000-ADSL-BASLNPAP656 Pointe a Pitre Bloc 2ASSIGNED PANov 30, 2005gestionip.ft@orange.com
via FR-TELECOM-20030213
└ 81.248.31.0/24256IP2000-ADSL-BASLNPAP656 Pointe a Pitre Bloc 1ASSIGNED PASep 26, 2012gestionip.ft@orange.com
via FR-TELECOM-20030213

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