Country
—
ASN LANDING PAGE
UPCLOUD UpCloud Ltd
Last updated · Jul 20, 2026
Country
—
Total prefixes
80
IPv4 prefixes
64
IPv6 prefixes
16
UPCLOUD UpCloud Ltd currently reports 80 prefixes and 41 upstream, downstream, or peer relationships. These counts describe the current dataset; they do not by themselves prove network quality, reach, or service use.
An ASN page shows the public organization label, country or region, BGP prefixes, and available peer and upstream relationships. It adds network context but cannot confirm a website host, physical facility, security status, or service quality.
UPCLOUD UpCloud Ltd is currently associated with an unknown region. These values come from public network sources and are useful lookup clues; an organization label, registration region, and actual service location may differ.
The page shows ASN data returned by the current upstream query; interpret it with the update time. Open representative IP pages from the same network and compare prefixes, source labels, and query times. Verify operator or service claims with the relevant registry or network operator.
Detailed data for this ASN is not available right now.
AS1299
AS1299
—
AS4637
AS4637
—
AS4657
AS4657
—
AS50304
AS50304
—
AS174
AS174
—
AS6939
AS6939
—
AS3356
AS3356
—
AS2914
AS2914
—
AS3491
AS3491
—
AS3320
AS3320
—
AS42229
AS42229
—
AS25091
AS25091
—
AS9002
AS9002
—
AS33891
AS33891
—
AS35280
AS35280
—
AS34549
AS34549
—
AS8218
AS8218
—
AS29075
AS29075
—
AS39351
AS39351
—
AS50673
AS50673
—
AS3214
AS3214
—
AS5405
AS5405
—
AS8298
AS8298
—
AS8455
AS8455
—
AS14907
AS14907
—
AS20485
AS20485
—
AS20764
AS20764
—
AS37468
AS37468
—
AS49434
AS49434
—
AS137409
AS137409
—
AS14840
AS14840
—
AS20562
AS20562
—
AS24748
AS24748
—
AS34019
AS34019
—
AS34927
AS34927
—
AS37721
AS37721
—
AS50629
AS50629
—
AS212483
AS212483
—
AS1103
AS1103
—
AS1140
AS1140
—
| Prefix | Name | Country |
|---|---|---|
| 109.71.54.0/24 | AS202053 | — |
| 109.71.55.0/24 | AS202053 | — |
| 185.20.136.0/22 | AS202053 | — |
| 185.26.48.0/22 | AS202053 | — |
| 185.70.196.0/22 | AS202053 | — |
| 194.107.180.0/24 | AS202053 | — |
| 194.39.109.0/24 | AS202053 | — |
| 194.62.96.0/22 | AS202053 | — |
| 212.147.224.0/22 | AS202053 | — |
| 212.147.228.0/22 | AS202053 | — |
| 212.147.232.0/22 | AS202053 | — |
| 212.147.236.0/22 | AS202053 | — |
| 212.147.240.0/22 | AS202053 | — |
| 212.147.244.0/22 | AS202053 | — |
| 212.147.248.0/23 | AS202053 | — |
| 212.147.250.0/23 | AS202053 | — |
| 212.147.252.0/22 | AS202053 | — |
| 213.163.192.0/20 | AS202053 | — |
| 2a03:3b00:1::/48 | AS202053 | — |
| 2a03:3b00:2::/48 | AS202053 | — |
| 2a04:3540::/32 | AS202053 | — |
| 2a04:3541:8000::/34 | AS202053 | — |
| 2a04:3541::/32 | AS202053 | — |
| 2a04:3542:8000::/34 | AS202053 | — |
| 2a04:3542::/32 | AS202053 | — |
| 2a04:3543::/32 | AS202053 | — |
| 2a04:3544:8000::/34 | AS202053 | — |
| 2a04:3544::/32 | AS202053 | — |
| 2a04:3545:4000::/34 | AS202053 | — |
| 2a04:3545:8000::/34 | AS202053 | — |
| 2a04:3545::/32 | AS202053 | — |
| 2a04:3546::/32 | AS202053 | — |
| 2a09:51c0::/29 | AS202053 | — |
| 2a0d:7980:2::/48 | AS202053 | — |
| 5.22.208.0/22 | AS202053 | — |
| 5.22.212.0/22 | AS202053 | — |
| 5.22.216.0/22 | AS202053 | — |
| 5.22.220.0/22 | AS202053 | — |
| 5.253.32.0/22 | AS202053 | — |
| 77.81.0.0/24 | AS202053 | — |
Review Google network organization fields, prefixes, peers, upstreams, and downstreams.
Review Cloudflare network organization fields, prefixes, peers, upstreams, and downstreams.
Review Microsoft network organization fields, prefixes, peers, upstreams, and downstreams.
Review Amazon network organization fields, prefixes, peers, upstreams, and downstreams.
AS202053 is an autonomous system number. The current source associates it with UPCLOUD UpCloud Ltd and the region field an unknown region; those values add network context but do not prove a specific service, physical location, or quality level.
They help explain the scale, interconnection depth, and route structure of AS202053. Richer peering and upstream data often indicate broader network reach, but they should still be interpreted together with prefixes and related IP landing pages.
Open a concrete IP page to check how the address maps into AS202053, then compare the prefix, source labels, and query time. Verify operator or service claims with the relevant registry or network operator.
Use real IP and ASN pages to understand ASNs, BGP prefixes, peers, upstreams, and downstreams, including the limits of each snapshot.
Build troubleshooting context from an IP, BGP prefix, ASN, and public network relationships without treating static route data as a packet path.
Compare representative cloud and edge networks by ASN, announced prefixes, peers, upstreams, and downstreams without inferring a specific host or customer workload.