Country
—
ASN LANDING PAGE
BUSINESS-SVYAZ - Dmitriy V. Kozmenko
Last updated · Apr 4, 2026
Country
—
Total prefixes
35
IPv4 prefixes
34
IPv6 prefixes
1
BUSINESS-SVYAZ - Dmitriy V. Kozmenko currently shows 35 prefixes and 43 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.
BUSINESS-SVYAZ - Dmitriy V. Kozmenko 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.
AS3216
AS3216
—
AS8359
AS8359
—
AS6939
AS6939
—
AS25091
AS25091
—
AS49434
AS49434
—
AS61049
AS61049
—
AS28917
AS28917
—
AS41327
AS41327
—
AS29049
AS29049
—
AS35598
AS35598
—
AS37721
AS37721
—
AS36236
AS36236
—
AS28910
AS28910
—
AS41722
AS41722
—
AS137409
AS137409
—
AS24482
AS24482
—
AS34927
AS34927
—
AS49673
AS49673
—
AS9198
AS9198
—
AS20764
AS20764
—
AS43727
AS43727
—
AS50673
AS50673
—
AS56911
AS56911
—
AS3170
AS3170
—
AS6204
AS6204
—
AS8218
AS8218
—
AS13004
AS13004
—
AS15958
AS15958
—
AS42295
AS42295
—
AS48678
AS48678
—
AS60171
AS60171
—
AS200612
AS200612
—
AS205112
AS205112
—
AS208972
AS208972
—
AS209823
AS209823
—
AS215638
AS215638
—
| Prefix | Name | Country |
|---|---|---|
| 109.235.184.0/21 | AS47586 | — |
| 109.235.184.0/22 | AS47586 | — |
| 109.235.188.0/22 | AS47586 | — |
| 146.19.211.0/24 | AS47586 | — |
| 158.58.128.0/21 | AS47586 | — |
| 158.58.128.0/22 | AS47586 | — |
| 158.58.132.0/22 | AS47586 | — |
| 185.30.116.0/22 | AS47586 | — |
| 185.30.116.0/23 | AS47586 | — |
| 193.0.148.0/22 | AS47586 | — |
| 193.0.148.0/23 | AS47586 | — |
| 193.0.150.0/23 | AS47586 | — |
| 194.114.128.0/22 | AS47586 | — |
| 194.114.128.0/23 | AS47586 | — |
| 194.114.130.0/23 | AS47586 | — |
| 195.64.156.0/23 | AS47586 | — |
| 195.64.156.0/24 | AS47586 | — |
| 195.64.157.0/24 | AS47586 | — |
| 2a00:b160::/32 | AS47586 | — |
| 37.77.108.0/22 | AS47586 | — |
| 37.77.108.0/23 | AS47586 | — |
| 37.77.110.0/23 | AS47586 | — |
| 80.249.204.0/22 | AS47586 | — |
| 80.249.204.0/23 | AS47586 | — |
| 80.249.206.0/23 | AS47586 | — |
| 87.239.0.0/21 | AS47586 | — |
| 87.239.0.0/22 | AS47586 | — |
| 87.239.4.0/22 | AS47586 | — |
| 91.214.56.0/22 | AS47586 | — |
| 91.214.56.0/23 | AS47586 | — |
| 91.214.58.0/23 | AS47586 | — |
| 91.214.59.0/24 | AS47586 | — |
| 93.190.16.0/21 | AS47586 | — |
| 93.190.16.0/22 | AS47586 | — |
| 93.190.20.0/22 | AS47586 | — |
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.
AS47586 is an autonomous system number used to identify an independently operated network. The current page associates it with BUSINESS-SVYAZ - Dmitriy V. Kozmenko 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 AS47586. 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 AS47586, 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.