Data as of Nov 20, 2026

185.110.18.0/24

5 residential-proxy exits · 30 days

XFERA Moviles S.A.

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

Residential-proxy exits

Proxy exits
5
2.0% of its addresses · 30 days
Always-on exits
2
40% of its exits
Providers
46
selling exits here
Oct 21, 2026 – Nov 19, 2026

Exits seen per day

1.8K observations

Proxy providers listing exits

  • 711Proxy
  • Ake.net
  • AnyIP
  • B2Proxy
  • BirdProxies
  • BlurPath
  • BottingTools
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • DataImpulse
  • Decodo
  • EVOPROXY
  • Evomi
  • FloppyData
  • GeekProxy
  • GonzoProxy
  • IPFly
  • IPPeak
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • LudaxProxy
  • MarsProxies
  • MoMoProxy
  • NovProxy
  • Novada
  • Oxylabs
  • PSBProxy
  • Proxmint
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyWing
  • PuraRoute
  • Q2IP
  • RH7Proxy
  • RainProxy
  • RapidProxy
  • ResiProxies
  • SwiftProxy
  • Thordata
  • ThunderProxy
  • VProxy
  • YumiProxy

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
185.110.16.0/221,024ES-XFERA-20150720XFERA Moviles S.A. (ORG-XMS1-RIPE) · ESALLOCATED PADec 28, 2021abuse.es@masorange.es
└ 185.110.18.0/23512ALMA-TELECOM-GPON-2unknownASSIGNED PAJan 22, 2021abuse.es@masorange.es
via ES-XFERA-20150720

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 185.110.16.0/22

185.110.16.0/22

Routing history

Pattern
Stable
First seen
Aug 2015
Current origin since
Mar 2018 · 8.7 yr
Origin networks
2
Last change of origin
Mar 2018
Recorded history

History

Handoffs
2