Country
—
ASN LANDING PAGE
RIPN-NS5-RU-MSK Join-stock company "Internet Exchange"MSK-IX"
Last updated · Apr 10, 2026
Country
—
Total prefixes
22
IPv4 prefixes
12
IPv6 prefixes
10
RIPN-NS5-RU-MSK Join-stock company "Internet Exchange"MSK-IX" currently shows 22 prefixes and 29 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.
RIPN-NS5-RU-MSK Join-stock company "Internet Exchange"MSK-IX" 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.
AS8985
AS8985
—
AS20485
AS20485
—
AS42139
AS42139
—
AS3216
AS3216
—
AS6939
AS6939
—
AS47445
AS47445
—
AS12389
AS12389
—
AS25091
AS25091
—
AS5568
AS5568
—
AS41327
AS41327
—
AS3316
AS3316
—
AS45029
AS45029
—
AS8932
AS8932
—
AS24482
AS24482
—
AS28910
AS28910
—
AS36236
AS36236
—
AS42728
AS42728
—
AS20764
AS20764
—
AS28917
AS28917
—
AS45018
AS45018
—
AS35598
AS35598
—
AS41722
AS41722
—
AS49673
AS49673
—
| Prefix | Name | Country |
|---|---|---|
| 193.232.124.0/24 | AS43832 | — |
| 193.232.128.0/23 | AS43832 | — |
| 193.232.128.0/24 | AS43832 | — |
| 193.232.160.0/24 | AS43832 | — |
| 193.232.177.0/24 | AS43832 | — |
| 193.232.93.0/24 | AS43832 | — |
| 194.190.168.0/24 | AS43832 | — |
| 194.226.75.0/24 | AS43832 | — |
| 194.85.104.0/24 | AS43832 | — |
| 194.85.108.0/24 | AS43832 | — |
| 2001:678:17::/48 | AS43832 | — |
| 2001:67c:1442::/48 | AS43832 | — |
| 2001:67c:1444::/48 | AS43832 | — |
| 2001:6d0:6d0::/48 | AS43832 | — |
| 2001:6d0:d6::/48 | AS43832 | — |
| 2001:6d0:ffb9::/48 | AS43832 | — |
| 2001:6d0:ffd4::/48 | AS43832 | — |
| 2001:6d0:fffc::/48 | AS43832 | — |
| 2a0c:a9c7:160::/48 | AS43832 | — |
| 2a0c:a9c7:177::/48 | AS43832 | — |
| 62.76.62.0/24 | AS43832 | — |
| 62.76.76.0/24 | AS43832 | — |
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.
AS43832 is an autonomous system number used to identify an independently operated network. The current page associates it with RIPN-NS5-RU-MSK Join-stock company "Internet Exchange"MSK-IX" 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 AS43832. 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 AS43832, 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.