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

87.58.158.0/23

13 residential-proxy exits · 30 days

UpCloud Ltd

Announcement
this exact prefix
RPKI valid
Announced by
AS202053
Type
Hosting
Risk
50 / 100 · Medium
Recent change
New origin Jun 2026
its first announcement on record

Residential-proxy exits

Proxy exits
13
2.5% of its addresses · 30 days
Spread
2 of 2
/24s with at least one exit
Providers
28
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

211 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
87.58.158.0/2407
87.58.159.0/2406

Proxy providers listing exits

  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • FastProxy
  • GSocks
  • Geonix
  • Geonode
  • HideProxy
  • IPFly
  • IPPeak
  • Infatica
  • LudaxProxy
  • NextProxy
  • NodeProxy
  • NovaProxy
  • ProxiesVision
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • Proxyma
  • PuraRoute
  • RainProxy
  • Shifter
  • VitalExclusive
  • ZENPROXY_LITE

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
87.58.144.0/204,096FI-UPCLOUD-20050520UpCloud Ltd (ORG-UL87-RIPE) · FIALLOCATED PAJun 24, 2026abuse@upcloud.com
└ 87.58.158.0/23512UPCLOUD-DK-CPH1-NETUpCloud Cloud ServersASSIGNED PAJun 29, 2026abuse@upcloud.com
via FI-UPCLOUD-20050520

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 this prefix

Summary

Routing history

Pattern
Stable
First seen
Jun 2026
Current origin since
Jun 2026 · 5 mo
Origin networks
1