Country
—
ASN LANDING PAGE
UCOMINT - Ucom CJSC
Last updated · Apr 4, 2026
Country
—
Total prefixes
6
IPv4 prefixes
4
IPv6 prefixes
2
UCOMINT - Ucom CJSC currently shows 6 prefixes and 80 upstream, downstream, or peer relationships. Larger prefix inventories often indicate broader network footprint, but they should still be read together with country and peering context.
ASN landing pages are more useful than a single IP page when you want cloud provider attribution, routing research, infrastructure comparison, or network topology analysis at the organization level.
UCOMINT - Ucom CJSC is currently associated with an unknown region. Country data is only a starting point; the more important signals are the organization name, website, prefix volume, and peering relationships that reveal whether the network behaves like a cloud platform, ISP, CDN, or enterprise backbone.
This page is currently showing live ASN data that can be used for peer, prefix, and network scale analysis. The most useful next step is usually to return to a related IP landing page, then compare that concrete address with this ASN profile and with broader topic pages for routing, cloud attribution, or WHOIS ownership analysis.
Detailed data for this ASN is not available right now.
AS201986
AS201986
—
AS208339
AS208339
—
AS39216
AS39216
—
AS44395
AS44395
—
AS43733
AS43733
—
AS205368
AS205368
—
AS199524
AS199524
—
AS215421
AS215421
—
AS13335
AS13335
—
AS197834
AS197834
—
AS42991
AS42991
—
AS199698
AS199698
—
AS48008
AS48008
—
AS44786
AS44786
—
AS7809
AS7809
—
AS57162
AS57162
—
AS198441
AS198441
—
AS42688
AS42688
—
AS207092
AS207092
—
AS204267
AS204267
—
AS201063
AS201063
—
AS212505
AS212505
—
AS204620
AS204620
—
AS204194
AS204194
—
AS48406
AS48406
—
AS211704
AS211704
—
AS206543
AS206543
—
AS207810
AS207810
—
AS216058
AS216058
—
AS208175
AS208175
—
AS47623
AS47623
—
AS200348
AS200348
—
AS205605
AS205605
—
AS214198
AS214198
—
AS201921
AS201921
—
AS201363
AS201363
—
AS199062
AS199062
—
AS212749
AS212749
—
AS25160
AS25160
—
AS4651
AS4651
—
AS9002
AS9002
—
AS3356
AS3356
—
AS174
AS174
—
AS6939
AS6939
—
AS35280
AS35280
—
AS14907
AS14907
—
AS15576
AS15576
—
AS50673
AS50673
—
AS8455
AS8455
—
AS12637
AS12637
—
AS49434
AS49434
—
AS8298
AS8298
—
AS37468
AS37468
—
AS6057
AS6057
—
AS39351
AS39351
—
AS3214
AS3214
—
AS34177
AS34177
—
AS50629
AS50629
—
AS5405
AS5405
—
AS29075
AS29075
—
AS28917
AS28917
—
AS51185
AS51185
—
AS49544
AS49544
—
AS1140
AS1140
—
AS31027
AS31027
—
AS37497
AS37497
—
AS25091
AS25091
—
AS205112
AS205112
—
AS51873
AS51873
—
AS58299
AS58299
—
AS18106
AS18106
—
AS61049
AS61049
—
AS205206
AS205206
—
AS8218
AS8218
—
AS34019
AS34019
—
AS36236
AS36236
—
AS12859
AS12859
—
AS271253
AS271253
—
AS1103
AS1103
—
AS1828
AS1828
—
| Prefix | Name | Country |
|---|---|---|
| 185.48.240.0/22 | AS8932 | — |
| 2a00:cc40:1::/48 | AS8932 | — |
| 2a00:cc40:2::/48 | AS8932 | — |
| 46.162.220.0/22 | AS8932 | — |
| 46.36.124.0/22 | AS8932 | — |
| 46.36.124.0/24 | AS8932 | — |
A strong reference ASN for Google DNS, Google Cloud, and global network footprint analysis.
Useful for analyzing CDN, Anycast, WAF, and large-scale edge network behavior.
Helpful when comparing Azure, enterprise backbone, and large-cloud routing patterns.
A useful ASN landing page for understanding AWS and large cloud-network ownership.
Continue from this ASN into the differences between WHOIS ownership and ASN ownership.
Continue from this ASN into route troubleshooting and network analysis.
Useful when you want to compare this ASN against larger cloud and edge networks.
Continue from the ASN page into WHOIS and ownership verification.
AS8932 is an autonomous system number used to identify an independently operated network. The current page associates it with UCOMINT - Ucom CJSC in an unknown region, which helps determine whether it behaves like a cloud provider, ISP, CDN, or enterprise backbone.
They help explain the scale, interconnection depth, and route structure of AS8932. Richer peering and upstream data often indicate broader network reach, but they should still be interpreted together with prefixes and related IP landing pages.
The best next step is usually to return to a concrete IP landing page to see how a specific address maps into AS8932, then continue into cloud, WHOIS, or routing topic pages to understand the network in a broader context.
Understand why WHOIS ownership and ASN ownership can differ, and how to combine both when deciding who really owns or operates an IP.
Use WHOIS, ASN, prefixes, and organization data to determine who ultimately owns an IP, range, or resolved domain target.
Learn what ASN, BGP routes, prefixes, upstreams, downstreams, and peers mean, then explore real ASN pages.
Compare large cloud and edge networks such as Google, Cloudflare, Microsoft, and Amazon through their ASN landing pages.