Country
—
ASN LANDING PAGE
MT-AS-OWN - Makedonski Telekom AD-Skopje
Last updated · Apr 4, 2026
Country
—
Total prefixes
87
IPv4 prefixes
86
IPv6 prefixes
1
MT-AS-OWN - Makedonski Telekom AD-Skopje currently shows 87 prefixes and 38 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.
MT-AS-OWN - Makedonski Telekom AD-Skopje 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.
AS41557
AS41557
—
AS209442
AS209442
—
AS61332
AS61332
—
AS8661
AS8661
—
AS199128
AS199128
—
AS205623
AS205623
—
AS214632
AS214632
—
AS57116
AS57116
—
AS199969
AS199969
—
AS206769
AS206769
—
AS25467
AS25467
—
AS204031
AS204031
—
AS213562
AS213562
—
AS198159
AS198159
—
AS206311
AS206311
—
AS44777
AS44777
—
AS6939
AS6939
—
AS1299
AS1299
—
AS5405
AS5405
—
AS47394
AS47394
—
AS43227
AS43227
—
| Prefix | Name | Country |
|---|---|---|
| 195.26.128.0/19 | AS6821 | — |
| 195.26.149.0/24 | AS6821 | — |
| 2a00:5c40::/29 | AS6821 | — |
| 37.25.80.0/21 | AS6821 | — |
| 37.25.84.0/22 | AS6821 | — |
| 46.217.0.0/19 | AS6821 | — |
| 46.217.0.0/21 | AS6821 | — |
| 46.217.104.0/21 | AS6821 | — |
| 46.217.112.0/21 | AS6821 | — |
| 46.217.120.0/21 | AS6821 | — |
| 46.217.128.0/21 | AS6821 | — |
| 46.217.136.0/21 | AS6821 | — |
| 46.217.144.0/21 | AS6821 | — |
| 46.217.152.0/21 | AS6821 | — |
| 46.217.16.0/21 | AS6821 | — |
| 46.217.160.0/19 | AS6821 | — |
| 46.217.192.0/19 | AS6821 | — |
| 46.217.198.0/23 | AS6821 | — |
| 46.217.224.0/19 | AS6821 | — |
| 46.217.224.0/20 | AS6821 | — |
| 46.217.24.0/21 | AS6821 | — |
| 46.217.254.0/24 | AS6821 | — |
| 46.217.32.0/21 | AS6821 | — |
| 46.217.40.0/21 | AS6821 | — |
| 46.217.48.0/21 | AS6821 | — |
| 46.217.56.0/21 | AS6821 | — |
| 46.217.64.0/21 | AS6821 | — |
| 46.217.72.0/21 | AS6821 | — |
| 46.217.8.0/21 | AS6821 | — |
| 46.217.80.0/21 | AS6821 | — |
| 46.217.88.0/21 | AS6821 | — |
| 46.217.96.0/21 | AS6821 | — |
| 62.162.0.0/16 | AS6821 | — |
| 62.162.0.0/18 | AS6821 | — |
| 62.162.120.0/24 | AS6821 | — |
| 62.162.129.0/24 | AS6821 | — |
| 62.162.133.0/24 | AS6821 | — |
| 62.162.134.0/24 | AS6821 | — |
| 62.162.136.0/24 | AS6821 | — |
| 62.162.138.0/24 | AS6821 | — |
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.
AS6821 is an autonomous system number used to identify an independently operated network. The current page associates it with MT-AS-OWN - Makedonski Telekom AD-Skopje 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 AS6821. 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 AS6821, 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.