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

83.136.248.0/22

13 residential-proxy exits · 30 days

UpCloud Ltd

Announcement
83.136.248.0/21
RPKI valid
Announced by
AS202053
Type
Hosting

Residential-proxy exits

Proxy exits
13
1.3% of its addresses · 30 days
Spread
4 of 4
/24s with at least one exit
Providers
30
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

534 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
83.136.248.0/2404
83.136.250.0/2404
83.136.249.0/2403
83.136.251.0/2402

Proxy providers listing exits

  • BirdProxies
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • Evomi
  • FastProxy
  • GSocks
  • Geonode
  • IPFly
  • IPPeak
  • Infatica
  • LudaxProxy
  • MangoProxy
  • NodeProxy
  • NovProxy
  • NovaProxy
  • PROXYSCRAPE
  • ProxiesVision
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • ProxyRack
  • Proxyma
  • PuraRoute
  • RainProxy
  • Shifter
  • VantageProxies
  • VitalExclusive
  • ZENPROXY_LITE

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
83.136.248.0/212,048FI-UPCLOUD-20100913UpCloud Ltd (ORG-UL87-RIPE) · FIALLOCATED PAMay 27, 2015abuse@upcloud.com
└ 83.136.248.0/221,024GB-UPCLOUD-LON1UpCloud Cloud ServersASSIGNED PAApr 12, 2015abuse@upcloud.com
via FI-UPCLOUD-20100913

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 83.136.248.0/21

83.136.248.0/21

Routing history

Pattern
Stable
First seen
May 2005
Current origin since
Mar 2015 · 12 yr
Origin networks
3
Last change of origin
Mar 2015
Recorded history

History

Handoffs
2