Country
—
ASN LANDING PAGE
MIRAN-AS - Miran Ltd.
Last updated · Apr 4, 2026
Country
—
Total prefixes
44
IPv4 prefixes
42
IPv6 prefixes
2
MIRAN-AS - Miran Ltd. currently shows 44 prefixes and 52 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.
MIRAN-AS - Miran Ltd. 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.
AS20764
AS20764
—
AS6939
AS6939
—
AS20485
AS20485
—
AS12389
AS12389
—
AS9498
AS9498
—
AS137409
AS137409
—
AS29049
AS29049
—
AS201706
AS201706
—
AS9049
AS9049
—
AS28917
AS28917
—
AS60299
AS60299
—
AS41327
AS41327
—
AS35598
AS35598
—
AS8400
AS8400
—
AS25091
AS25091
—
AS28910
AS28910
—
AS29226
AS29226
—
AS13194
AS13194
—
AS24482
AS24482
—
AS29076
AS29076
—
AS57724
AS57724
—
AS60280
AS60280
—
AS31500
AS31500
—
AS55818
AS55818
—
AS9198
AS9198
—
AS43727
AS43727
—
AS8641
AS8641
—
AS35168
AS35168
—
AS2854
AS2854
—
AS49581
AS49581
—
AS199599
AS199599
—
AS52025
AS52025
—
AS3267
AS3267
—
AS30823
AS30823
—
AS8449
AS8449
—
AS35000
AS35000
—
AS8932
AS8932
—
AS202984
AS202984
—
AS43298
AS43298
—
AS56534
AS56534
—
| Prefix | Name | Country |
|---|---|---|
| 178.249.68.0/24 | AS41722 | — |
| 178.249.69.0/24 | AS41722 | — |
| 178.249.70.0/24 | AS41722 | — |
| 178.249.71.0/24 | AS41722 | — |
| 178.250.152.0/24 | AS41722 | — |
| 178.250.153.0/24 | AS41722 | — |
| 178.250.154.0/24 | AS41722 | — |
| 178.250.155.0/24 | AS41722 | — |
| 185.147.80.0/24 | AS41722 | — |
| 185.147.81.0/24 | AS41722 | — |
| 185.147.82.0/24 | AS41722 | — |
| 185.147.83.0/24 | AS41722 | — |
| 185.162.92.0/24 | AS41722 | — |
| 185.162.93.0/24 | AS41722 | — |
| 185.162.94.0/24 | AS41722 | — |
| 185.162.95.0/24 | AS41722 | — |
| 185.174.164.0/24 | AS41722 | — |
| 185.174.165.0/24 | AS41722 | — |
| 185.53.20.0/24 | AS41722 | — |
| 185.53.21.0/24 | AS41722 | — |
| 185.53.22.0/24 | AS41722 | — |
| 185.53.23.0/24 | AS41722 | — |
| 185.73.212.0/24 | AS41722 | — |
| 185.73.213.0/24 | AS41722 | — |
| 185.73.214.0/24 | AS41722 | — |
| 185.73.215.0/24 | AS41722 | — |
| 2a03:21c0::/32 | AS41722 | — |
| 2a07:a500::/32 | AS41722 | — |
| 91.142.80.0/24 | AS41722 | — |
| 91.142.81.0/24 | AS41722 | — |
| 91.142.82.0/24 | AS41722 | — |
| 91.142.83.0/24 | AS41722 | — |
| 91.142.84.0/24 | AS41722 | — |
| 91.142.85.0/24 | AS41722 | — |
| 91.142.86.0/24 | AS41722 | — |
| 91.142.87.0/24 | AS41722 | — |
| 91.142.88.0/24 | AS41722 | — |
| 91.142.89.0/24 | AS41722 | — |
| 91.142.90.0/24 | AS41722 | — |
| 91.142.91.0/24 | AS41722 | — |
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.
AS41722 is an autonomous system number used to identify an independently operated network. The current page associates it with MIRAN-AS - Miran Ltd. 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 AS41722. 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 AS41722, 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.