Data as of Nov 11, 2026

89.16.0.0/21

1 residential-proxy exit · 30 days

Outremer Telecom SAS

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

Residential-proxy exits

Proxy exits
1
0.05% of its addresses · 30 days
Spread
1 of 8
/24s with at least one exit
Providers
20
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

37 observations

Proxy providers listing exits

  • 711Proxy
  • BottingTools
  • ByteProxies
  • Byteful
  • CoreProxy
  • Decodo
  • Evomi
  • FlashProxy
  • GoProxies
  • GonzoProxy
  • IPCola
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • Novada
  • Oxylabs
  • Proxy-Seller
  • ProxyRack
  • Proxyma
  • Thordata

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
89.16.0.0/20
since Jun 2016
AS20776Residential19Outremer Telecom SAS
89.16.0.0/19
since Jul 2006
AS20776Residential164
16 always on
Outremer Telecom SAS

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
89.16.0.0/198,192MQ-OUTREMER-20060623Outremer Telecom SAS (ORG-OT1-RIPE) · MQALLOCATED PAJun 23, 2006ripe@outremer-telecom.fr
└ 89.16.0.0/212,048OUTREMER-TELECOMOutremer Telecom NetworkASSIGNED PANov 23, 2007ripe@outremer-telecom.fr
via MQ-OUTREMER-20060623

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
Jun 2016
Current origin since
Apr 2024 · 2.6 yr
Origin networks
1