Country
—
ASN LANDING PAGE
WESERVE - Weserve B.V.
Last updated · Apr 4, 2026
Country
—
Total prefixes
30
IPv4 prefixes
28
IPv6 prefixes
2
WESERVE - Weserve B.V. currently shows 30 prefixes and 40 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.
WESERVE - Weserve 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.
Detailed data for this ASN is not available right now.
AS50673
AS50673
—
AS6939
AS6939
—
AS57112
AS57112
—
AS34019
AS34019
—
AS5405
AS5405
—
AS20764
AS20764
—
AS50304
AS50304
—
AS8298
AS8298
—
AS14840
AS14840
—
AS22356
AS22356
—
AS24961
AS24961
—
AS25091
AS25091
—
AS39351
AS39351
—
AS41327
AS41327
—
AS58057
AS58057
—
AS58299
AS58299
—
AS61049
AS61049
—
AS205112
AS205112
—
AS1031
AS1031
—
AS3399
AS3399
—
AS6204
AS6204
—
AS8283
AS8283
—
AS9044
AS9044
—
AS12859
AS12859
—
AS24482
AS24482
—
AS28917
AS28917
—
AS29049
AS29049
—
AS34927
AS34927
—
AS36236
AS36236
—
AS39120
AS39120
—
AS39122
AS39122
—
AS41441
AS41441
—
AS43727
AS43727
—
AS50869
AS50869
—
AS56655
AS56655
—
AS56911
AS56911
—
AS60326
AS60326
—
AS62167
AS62167
—
AS198150
AS198150
—
AS199524
AS199524
—
| Prefix | Name | Country |
|---|---|---|
| 128.0.68.0/23 | AS208864 | — |
| 178.170.148.0/22 | AS208864 | — |
| 178.170.152.0/22 | AS208864 | — |
| 185.145.24.0/22 | AS208864 | — |
| 185.178.232.0/22 | AS208864 | — |
| 185.192.144.0/24 | AS208864 | — |
| 185.192.145.0/24 | AS208864 | — |
| 185.252.244.0/22 | AS208864 | — |
| 185.252.76.0/22 | AS208864 | — |
| 185.35.96.0/22 | AS208864 | — |
| 185.42.59.0/24 | AS208864 | — |
| 188.120.32.0/22 | AS208864 | — |
| 188.120.44.0/22 | AS208864 | — |
| 188.72.64.0/22 | AS208864 | — |
| 188.72.68.0/23 | AS208864 | — |
| 193.151.184.0/23 | AS208864 | — |
| 193.151.186.0/23 | AS208864 | — |
| 2a00:dfa0::/32 | AS208864 | — |
| 2a0a:6f80::/32 | AS208864 | — |
| 37.18.4.0/22 | AS208864 | — |
| 45.11.15.0/24 | AS208864 | — |
| 46.243.152.0/22 | AS208864 | — |
| 46.243.188.0/22 | AS208864 | — |
| 46.243.192.0/21 | AS208864 | — |
| 5.59.188.0/22 | AS208864 | — |
| 5.59.200.0/22 | AS208864 | — |
| 85.208.160.0/22 | AS208864 | — |
| 91.201.124.0/22 | AS208864 | — |
| 91.212.139.0/24 | AS208864 | — |
| 91.220.53.0/24 | AS208864 | — |
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.
AS208864 is an autonomous system number used to identify an independently operated network. The current page associates it with WESERVE - Weserve 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 AS208864. 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 AS208864, 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.