Country
—
ASN LANDING PAGE
AS6720
MAGWIEN - Magistrat der Stadt Wien, Magistratsabteilung 01
Last updated · Apr 4, 2026
Total prefixes
4
IPv4 prefixes
2
IPv6 prefixes
2
ASN summary
How to read the scale of AS6720
MAGWIEN - Magistrat der Stadt Wien, Magistratsabteilung 01 currently shows 4 prefixes and 41 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.
When is an ASN page most useful?
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.
How should you read the country, organization, and role of AS6720?
MAGWIEN - Magistrat der Stadt Wien, Magistratsabteilung 01 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.
What should you inspect next after the AS6720 page?
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.
Search intents this ASN page helps cover
AS6720 ASN lookupAS6720 BGPAS6720 peersAS6720 prefixesAS6720 upstreamsMAGWIEN - Magistrat der Stadt Wien, Magistratsabteilung 01 ASN
Upstreams
Detailed data for this ASN is not available right now.
Downstreams
Peers
AS1764
AS1764
—
AS1853
AS1853
—
AS6939
AS6939
—
AS9002
AS9002
—
AS33891
AS33891
—
AS57463
AS57463
—
AS20804
AS20804
—
AS5405
AS5405
—
AS6663
AS6663
—
AS16276
AS16276
—
AS6204
AS6204
—
AS8218
AS8218
—
AS5603
AS5603
—
AS8400
AS8400
—
AS3303
AS3303
—
AS50629
AS50629
—
AS5606
AS5606
—
AS6774
AS6774
—
AS23764
AS23764
—
AS34779
AS34779
—
AS3212
AS3212
—
AS44306
AS44306
—
AS8412
AS8412
—
AS47147
AS47147
—
AS34772
AS34772
—
AS24940
AS24940
—
AS29208
AS29208
—
AS5578
AS5578
—
AS196844
AS196844
—
AS32787
AS32787
—
AS9119
AS9119
—
AS13004
AS13004
—
AS25255
AS25255
—
AS15576
AS15576
—
AS49544
AS49544
—
AS43061
AS43061
—
AS21013
AS21013
—
AS47692
AS47692
—
AS49808
AS49808
—
AS21215
AS21215
—
Prefix inventory
| Prefix | Name | Country |
|---|---|---|
| 141.203.0.0/16 | AS6720 | — |
| 217.149.224.0/20 | AS6720 | — |
| 2a00:1ba0:2::/48 | AS6720 | — |
| 2a00:1ba0:3::/48 | AS6720 | — |
Related ASN pages
AS15169 · Google
A strong reference ASN for Google DNS, Google Cloud, and global network footprint analysis.
AS13335 · Cloudflare
Useful for analyzing CDN, Anycast, WAF, and large-scale edge network behavior.
AS8075 · Microsoft
Helpful when comparing Azure, enterprise backbone, and large-cloud routing patterns.
AS16509 · Amazon
A useful ASN landing page for understanding AWS and large cloud-network ownership.
Related lookups and next steps
WHOIS vs ASN Ownership Guide
Continue from this ASN into the differences between WHOIS ownership and ASN ownership.
Routing Troubleshooting and Network Analysis
Continue from this ASN into route troubleshooting and network analysis.
Cloud Network and ASN Comparison
Useful when you want to compare this ASN against larger cloud and edge networks.
WHOIS and IP Ownership Guide
Continue from the ASN page into WHOIS and ownership verification.
Frequently asked questions about this ASN page
What does AS6720 represent?
AS6720 is an autonomous system number used to identify an independently operated network. The current page associates it with MAGWIEN - Magistrat der Stadt Wien, Magistratsabteilung 01 in an unknown region, which helps determine whether it behaves like a cloud provider, ISP, CDN, or enterprise backbone.
What are peers, upstreams, and prefixes useful for on the AS6720 page?
They help explain the scale, interconnection depth, and route structure of AS6720. Richer peering and upstream data often indicate broader network reach, but they should still be interpreted together with prefixes and related IP landing pages.
What should you do after reviewing AS6720?
The best next step is usually to return to a concrete IP landing page to see how a specific address maps into AS6720, then continue into cloud, WHOIS, or routing topic pages to understand the network in a broader context.
Related topics
WHOIS vs ASN Ownership Guide
Understand why WHOIS ownership and ASN ownership can differ, and how to combine both when deciding who really owns or operates an IP.
WHOIS and IP Ownership Guide
Use WHOIS, ASN, prefixes, and organization data to determine who ultimately owns an IP, range, or resolved domain target.
BGP and ASN Basics Guide
Learn what ASN, BGP routes, prefixes, upstreams, downstreams, and peers mean, then explore real ASN pages.
Cloud Network and ASN Comparison
Compare large cloud and edge networks such as Google, Cloudflare, Microsoft, and Amazon through their ASN landing pages.