Data as of Nov 10, 2026

80.243.252.0/24

5 residential-proxy exits · 30 days

Outremer Telecom SAS

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

Residential-proxy exits

Proxy exits
5
2.0% of its addresses · 30 days
Providers
37
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

668 observations

Proxy providers listing exits

  • 711Proxy
  • Ake.net
  • B2Proxy
  • BartProxies
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • DataImpulse
  • Decodo
  • EZProxies
  • EnigmaProxy
  • FloppyData
  • GSocks
  • GloryCloud
  • IPFly
  • IPPeak
  • Infatica
  • KindProxy
  • LemonBright
  • MangoProxy
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Oxylabs
  • Proxio
  • ProxyEmpire
  • ProxyRack
  • Proxyma
  • PuraRoute
  • RainProxy
  • RapidProxy
  • Shifter
  • StrikeProxy
  • VantageProxies
  • VitalExclusive
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
80.243.240.0/20
since Oct 2005
AS20776Residential52
3 always on
Outremer Telecom SAS

Registrations in this block

The registry's network records over this block, widest first, each under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
80.243.240.0/204,096MQ-OUTREMER-20050922Outremer Telecom SAS (ORG-OT1-RIPE) · MQALLOCATED PASep 22, 2005ripe@outremer-telecom.fr
└ 80.243.252.0/221,024OUTREMER-TELECOMOutremer Telecom NetworkASSIGNED PANov 23, 2007ripe@outremer-telecom.fr
via MQ-OUTREMER-20050922

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

80.243.248.0/21

Routing history

Pattern
Stable
First seen
Jan 2017
Current origin since
Jan 2017 · 9.8 yr
Origin networks
1