LAYER3 INTEL
Get started
Sign in
Data as of Nov 13, 2026

185.26.48.0/23

5 residential-proxy exits · 30 days

UpCloud Ltd

Announcement
185.26.48.0/22
RPKI valid
Announced by
AS202053
Type
Hosting
Risk
50 / 100 · Medium

Residential-proxy exits

Proxy exits
5
0.98% of its addresses · 30 days
Spread
2 of 2
/24s with at least one exit
Providers
18
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

155 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
185.26.48.0/2404
185.26.49.0/2401

Proxy providers listing exits

  • BirdProxies
  • ByteProxies
  • Byteful
  • GSocks
  • Geonix
  • Infatica
  • InfiniteProxies
  • LemonPrime
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • PROXYSCRAPE
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • RainProxy
  • SPYDERPROXY_BASIC
  • Shifter

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
185.26.48.0/221,024FI-UPCLOUD-20130515UpCloud Ltd (ORG-UL87-RIPE) · FIALLOCATED PAMay 15, 2013abuse@upcloud.com
└ 185.26.48.0/23512UPCLOUD-FI-HEL1-NET3-AUpCloud Cloud ServersASSIGNED PAMay 23, 2015abuse@upcloud.com
via FI-UPCLOUD-20130515

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

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Who has announced 185.26.48.0/22

185.26.48.0/22

Routing history

Pattern
Stable
First seen
Dec 2014
Current origin since
Apr 2015 · 12 yr
Origin networks
2
Last change of origin
Apr 2015
Recorded history

History

Handoffs
1