Data as of Nov 19, 2026

37.122.216.0/22

8 residential-proxy exits · 30 days

Free Technologies Excom S.L.

Announcement
this exact prefix
RPKI valid
Announced by
Type
Residential
Recent change
New origin Jul 2026
from AS205262 Free Technologies Excom S.L., after 8.1 years unannounced

Residential-proxy exits

Proxy exits
8
0.78% of its addresses · 30 days
Always-on exits
1
13% of its exits
Spread
1 of 4
/24s with at least one exit
Providers
45
selling exits here
Oct 20, 2026 – Nov 18, 2026

Exits seen per day

2.1K observations

Proxy providers listing exits

  • 2Captcha
  • 2Extract
  • 711Proxy
  • 9Proxy
  • Ake.net
  • B2Proxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • FROXY
  • FastProxy
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GSocks
  • Geonix
  • Geonode
  • GonzoProxy
  • Infatica
  • InfiniteProxies
  • KocerRoxy
  • Kookey
  • LemonBright
  • LemonLabs
  • LemonPrime
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • Novada
  • PROXYSCRAPE
  • PrivateProxy
  • Proxies.fo
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • Shifter
  • SwiftProxy
  • TalorData
  • ThunderProxy
  • VantageProxies
  • VitalExclusive

Announcements

More specific

Announcements inside

PrefixOriginTypeProxy exitsHolderRPKI
37.122.219.0/24
since Mar 2024
AS34471Residential8
1 always on
Free Technologies Excom S.L.

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
37.122.216.0/221,024ES-EXCOM-20180613Free Technologies Excom S.L. (ORG-FTES1-RIPE) · ESALLOCATED PADec 19, 2022sat@excom.es
└ 37.122.216.0/24256CONRED_CLIENTES1unknownASSIGNED PAJul 2, 2018sat@excom.es
via ES-EXCOM-20180613
└ 37.122.217.0/24256CONRED_CLIENTES2unknownASSIGNED PAJul 2, 2018sat@excom.es
via ES-EXCOM-20180613
└ 37.122.218.0/24256CONRED_CLIENTES3unknownASSIGNED PAJul 2, 2018sat@excom.es
via ES-EXCOM-20180613

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
Jun 2018
Current origin since
Jul 2026 · 4 mo
Origin networks
1