Country
—
ASN LANDING PAGE
ONE-NETWORK - dogado GmbH
Last updated · Apr 4, 2026
Country
—
Total prefixes
72
IPv4 prefixes
63
IPv6 prefixes
9
ONE-NETWORK - dogado GmbH currently shows 72 prefixes and 46 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.
ONE-NETWORK - dogado 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.
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.
AS6939
AS6939
—
AS1299
AS1299
—
AS5405
AS5405
—
AS3356
AS3356
—
AS3320
AS3320
—
AS9002
AS9002
—
AS33891
AS33891
—
AS34019
AS34019
—
AS13030
AS13030
—
AS20764
AS20764
—
AS34549
AS34549
—
AS35625
AS35625
—
AS29075
AS29075
—
AS8218
AS8218
—
AS3214
AS3214
—
AS6057
AS6057
—
AS12779
AS12779
—
AS25091
AS25091
—
AS34177
AS34177
—
AS34927
AS34927
—
AS37468
AS37468
—
AS39351
AS39351
—
AS41327
AS41327
—
AS62275
AS62275
—
AS137409
AS137409
—
AS8298
AS8298
—
AS20562
AS20562
—
AS58115
AS58115
—
AS1764
AS1764
—
AS8220
AS8220
—
AS29691
AS29691
—
AS37100
AS37100
—
AS1267
AS1267
—
AS15412
AS15412
—
AS21232
AS21232
—
AS24961
AS24961
—
AS29222
AS29222
—
AS680
AS680
—
AS6667
AS6667
—
AS8426
AS8426
—
| Prefix | Name | Country |
|---|---|---|
| 128.127.64.0/21 | AS8648 | — |
| 178.20.102.0/24 | AS8648 | — |
| 178.20.103.0/24 | AS8648 | — |
| 178.20.96.0/22 | AS8648 | — |
| 178.20.99.0/24 | AS8648 | — |
| 178.250.168.0/21 | AS8648 | — |
| 178.250.171.0/24 | AS8648 | — |
| 185.102.20.0/22 | AS8648 | — |
| 185.102.21.0/24 | AS8648 | — |
| 185.117.248.0/22 | AS8648 | — |
| 185.129.244.0/22 | AS8648 | — |
| 185.207.228.0/24 | AS8648 | — |
| 185.207.230.0/24 | AS8648 | — |
| 185.207.231.0/24 | AS8648 | — |
| 185.3.235.0/24 | AS8648 | — |
| 185.65.221.0/24 | AS8648 | — |
| 185.65.222.0/24 | AS8648 | — |
| 185.80.92.0/22 | AS8648 | — |
| 185.84.80.0/22 | AS8648 | — |
| 185.84.80.0/23 | AS8648 | — |
| 185.84.82.0/23 | AS8648 | — |
| 185.84.82.0/24 | AS8648 | — |
| 188.64.40.0/22 | AS8648 | — |
| 188.64.44.0/23 | AS8648 | — |
| 192.162.28.0/24 | AS8648 | — |
| 192.162.30.0/23 | AS8648 | — |
| 192.162.84.0/22 | AS8648 | — |
| 193.22.255.0/24 | AS8648 | — |
| 193.25.114.0/23 | AS8648 | — |
| 194.116.186.0/23 | AS8648 | — |
| 194.97.192.0/19 | AS8648 | — |
| 195.110.42.0/23 | AS8648 | — |
| 195.181.248.0/22 | AS8648 | — |
| 195.225.133.0/24 | AS8648 | — |
| 195.34.82.0/23 | AS8648 | — |
| 195.42.120.0/23 | AS8648 | — |
| 195.62.125.0/24 | AS8648 | — |
| 195.62.126.0/24 | AS8648 | — |
| 195.62.96.0/19 | AS8648 | — |
| 2001:748:400::/48 | AS8648 | — |
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.
AS8648 is an autonomous system number used to identify an independently operated network. The current page associates it with ONE-NETWORK - dogado GmbH 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 AS8648. 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 AS8648, 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.