Country
—
ASN LANDING PAGE
AS8767
MNET-AS - M-net Telekommunikations GmbH
Last updated · Apr 4, 2026
Total prefixes
79
IPv4 prefixes
68
IPv6 prefixes
11
ASN summary
How to read the scale of AS8767
MNET-AS - M-net Telekommunikations GmbH currently shows 79 prefixes and 80 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 AS8767?
MNET-AS - M-net Telekommunikations GmbH 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 AS8767 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
AS8767 ASN lookupAS8767 BGPAS8767 peersAS8767 prefixesAS8767 upstreamsMNET-AS - M-net Telekommunikations GmbH ASN
Upstreams
Detailed data for this ASN is not available right now.
Downstreams
AS12657
AS12657
—
AS24764
AS24764
—
AS197659
AS197659
—
AS197164
AS197164
—
AS13246
AS13246
—
AS203989
AS203989
—
AS24845
AS24845
—
AS210214
AS210214
—
AS42821
AS42821
—
AS197874
AS197874
—
AS215866
AS215866
—
AS209877
AS209877
—
AS216094
AS216094
—
AS33824
AS33824
—
AS41086
AS41086
—
AS203325
AS203325
—
AS29259
AS29259
—
AS34127
AS34127
—
AS41926
AS41926
—
AS20561
AS20561
—
AS202694
AS202694
—
AS25432
AS25432
—
AS202716
AS202716
—
AS214568
AS214568
—
AS205666
AS205666
—
AS8874
AS8874
—
AS203793
AS203793
—
AS207364
AS207364
—
AS209991
AS209991
—
AS18841
AS18841
—
AS33619
AS33619
—
AS213566
AS213566
—
AS12886
AS12886
—
AS197909
AS197909
—
AS197206
AS197206
—
AS199090
AS199090
—
AS208964
AS208964
—
AS16151
AS16151
—
AS399713
AS399713
—
AS202077
AS202077
—
Peers
AS1299
AS1299
—
AS2914
AS2914
—
AS3356
AS3356
—
AS6939
AS6939
—
AS34549
AS34549
—
AS50673
AS50673
—
AS6461
AS6461
—
AS13030
AS13030
—
AS20764
AS20764
—
AS34019
AS34019
—
AS35625
AS35625
—
AS3214
AS3214
—
AS48362
AS48362
—
AS37497
AS37497
—
AS8298
AS8298
—
AS34927
AS34927
—
AS6057
AS6057
—
AS9002
AS9002
—
AS29691
AS29691
—
AS5405
AS5405
—
AS12779
AS12779
—
AS50629
AS50629
—
AS8758
AS8758
—
AS41327
AS41327
—
AS25091
AS25091
—
AS39351
AS39351
—
AS29632
AS29632
—
AS34177
AS34177
—
AS29075
AS29075
—
AS33891
AS33891
—
AS3320
AS3320
—
AS8218
AS8218
—
AS37468
AS37468
—
AS29504
AS29504
—
AS51185
AS51185
—
AS35710
AS35710
—
AS199524
AS199524
—
AS51873
AS51873
—
AS212635
AS212635
—
AS35369
AS35369
—
Prefix inventory
| Prefix | Name | Country |
|---|---|---|
| 109.68.48.0/21 | AS8767 | — |
| 128.224.248.0/22 | AS8767 | — |
| 131.99.0.0/16 | AS8767 | — |
| 139.29.128.0/17 | AS8767 | — |
| 139.29.176.0/22 | AS8767 | — |
| 139.29.182.0/24 | AS8767 | — |
| 185.110.32.0/22 | AS8767 | — |
| 185.131.236.0/24 | AS8767 | — |
| 185.17.204.0/22 | AS8767 | — |
| 185.174.104.0/23 | AS8767 | — |
| 185.188.65.0/24 | AS8767 | — |
| 185.244.60.0/22 | AS8767 | — |
| 185.29.28.0/23 | AS8767 | — |
| 185.36.117.0/24 | AS8767 | — |
| 185.36.118.0/24 | AS8767 | — |
| 185.47.44.0/22 | AS8767 | — |
| 185.68.156.0/22 | AS8767 | — |
| 185.71.94.0/24 | AS8767 | — |
| 188.174.0.0/16 | AS8767 | — |
| 193.102.45.0/24 | AS8767 | — |
| 193.168.248.0/22 | AS8767 | — |
| 193.19.160.0/22 | AS8767 | — |
| 193.27.18.0/24 | AS8767 | — |
| 193.28.242.0/24 | AS8767 | — |
| 193.30.36.0/24 | AS8767 | — |
| 193.30.37.0/24 | AS8767 | — |
| 193.30.38.0/24 | AS8767 | — |
| 193.98.167.0/24 | AS8767 | — |
| 194.113.192.0/23 | AS8767 | — |
| 194.120.150.0/24 | AS8767 | — |
| 194.127.122.0/24 | AS8767 | — |
| 194.127.207.0/24 | AS8767 | — |
| 194.15.128.0/21 | AS8767 | — |
| 194.15.164.0/24 | AS8767 | — |
| 194.15.165.0/24 | AS8767 | — |
| 194.15.166.0/24 | AS8767 | — |
| 194.15.167.0/24 | AS8767 | — |
| 194.156.145.0/24 | AS8767 | — |
| 194.156.206.0/24 | AS8767 | — |
| 194.246.16.0/24 | AS8767 | — |
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 AS8767 represent?
AS8767 is an autonomous system number used to identify an independently operated network. The current page associates it with MNET-AS - M-net Telekommunikations GmbH 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 AS8767 page?
They help explain the scale, interconnection depth, and route structure of AS8767. 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 AS8767?
The best next step is usually to return to a concrete IP landing page to see how a specific address maps into AS8767, 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.