Country
—
ASN LANDING PAGE
NETROUTING-AS - Netrouting B.V.
Last updated · Apr 4, 2026
Country
—
Total prefixes
54
IPv4 prefixes
45
IPv6 prefixes
9
NETROUTING-AS - Netrouting B.V. currently shows 54 prefixes and 57 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.
NETROUTING-AS - Netrouting B.V. 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
—
AS2914
AS2914
—
AS6453
AS6453
—
AS3356
AS3356
—
AS3491
AS3491
—
AS174
AS174
—
AS13030
AS13030
—
AS3303
AS3303
—
AS37468
AS37468
—
AS34549
AS34549
—
AS25091
AS25091
—
AS20764
AS20764
—
AS50304
AS50304
—
AS3214
AS3214
—
AS5405
AS5405
—
AS34927
AS34927
—
AS34019
AS34019
—
AS34177
AS34177
—
AS49434
AS49434
—
AS50673
AS50673
—
AS29075
AS29075
—
AS8218
AS8218
—
AS35280
AS35280
—
AS12779
AS12779
—
AS24482
AS24482
—
AS1828
AS1828
—
AS8298
AS8298
—
AS36236
AS36236
—
AS41327
AS41327
—
AS48362
AS48362
—
AS52320
AS52320
—
AS137409
AS137409
—
AS1103
AS1103
—
AS37100
AS37100
—
AS199524
AS199524
—
AS4455
AS4455
—
AS8529
AS8529
—
AS39351
AS39351
—
AS50763
AS50763
—
| Prefix | Name | Country |
|---|---|---|
| 103.101.0.0/23 | AS6206 | — |
| 103.101.0.0/24 | AS6206 | — |
| 103.101.1.0/24 | AS6206 | — |
| 107.178.48.0/22 | AS6206 | — |
| 107.178.50.0/24 | AS6206 | — |
| 107.178.52.0/23 | AS6206 | — |
| 107.178.54.0/24 | AS6206 | — |
| 109.235.48.0/21 | AS6206 | — |
| 172.98.34.0/23 | AS6206 | — |
| 185.126.237.0/24 | AS6206 | — |
| 185.155.170.0/24 | AS6206 | — |
| 185.165.237.0/24 | AS6206 | — |
| 185.186.78.0/24 | AS6206 | — |
| 192.142.2.0/23 | AS6206 | — |
| 192.142.33.0/24 | AS6206 | — |
| 193.23.60.0/24 | AS6206 | — |
| 194.110.67.0/24 | AS6206 | — |
| 198.52.247.0/24 | AS6206 | — |
| 209.135.176.0/23 | AS6206 | — |
| 23.188.19.0/24 | AS6206 | — |
| 23.188.21.0/24 | AS6206 | — |
| 23.188.22.0/24 | AS6206 | — |
| 2401:c740::/32 | AS6206 | — |
| 2602:fc2a:1::/48 | AS6206 | — |
| 2602:fc48::/36 | AS6206 | — |
| 2a00:dd0::/32 | AS6206 | — |
| 2a00:dd0:aaaa::/48 | AS6206 | — |
| 2a00:dd0:bbbb::/48 | AS6206 | — |
| 2a00:dd0:cccc::/48 | AS6206 | — |
| 2a00:dd0:ffff::/48 | AS6206 | — |
| 2a11:840:3::/48 | AS6206 | — |
| 37.46.192.0/22 | AS6206 | — |
| 37.46.196.0/23 | AS6206 | — |
| 37.46.198.0/23 | AS6206 | — |
| 45.126.36.0/22 | AS6206 | — |
| 45.126.38.0/24 | AS6206 | — |
| 45.133.174.0/24 | AS6206 | — |
| 45.88.216.0/24 | AS6206 | — |
| 45.89.48.0/24 | AS6206 | — |
| 45.91.108.0/24 | AS6206 | — |
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.
AS6206 is an autonomous system number used to identify an independently operated network. The current page associates it with NETROUTING-AS - Netrouting B.V. 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 AS6206. 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 AS6206, 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.