Country
—
ASN LANDING PAGE
BOOKING-BV - Booking.com BV
Last updated · Apr 4, 2026
Country
—
Total prefixes
26
IPv4 prefixes
17
IPv6 prefixes
9
BOOKING-BV - Booking.com BV currently shows 26 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.
BOOKING-BV - Booking.com BV 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.
AS6461
AS6461
—
AS3356
AS3356
—
AS1299
AS1299
—
AS6939
AS6939
—
AS6762
AS6762
—
AS3320
AS3320
—
AS9002
AS9002
—
AS13030
AS13030
—
AS8283
AS8283
—
AS30781
AS30781
—
AS33891
AS33891
—
AS8218
AS8218
—
AS50304
AS50304
—
AS3214
AS3214
—
AS20764
AS20764
—
AS34177
AS34177
—
AS1267
AS1267
—
AS14840
AS14840
—
AS20562
AS20562
—
AS37468
AS37468
—
AS559
AS559
—
AS1836
AS1836
—
AS6424
AS6424
—
AS8426
AS8426
—
AS8943
AS8943
—
AS12389
AS12389
—
AS12779
AS12779
—
AS15605
AS15605
—
AS15958
AS15958
—
AS30844
AS30844
—
AS37100
AS37100
—
AS37271
AS37271
—
AS37282
AS37282
—
AS37497
AS37497
—
AS39120
AS39120
—
AS41327
AS41327
—
AS44901
AS44901
—
AS45489
AS45489
—
AS47147
AS47147
—
AS48070
AS48070
—
| Prefix | Name | Country |
|---|---|---|
| 2a01:5040:12::/48 | AS43996 | — |
| 2a01:5040:20::/48 | AS43996 | — |
| 2a01:5040:40::/48 | AS43996 | — |
| 2a01:5040::/36 | AS43996 | — |
| 2a01:5040::/48 | AS43996 | — |
| 2a01:5041:2005::/48 | AS43996 | — |
| 2a01:5041:2009::/48 | AS43996 | — |
| 2a01:5041:5::/48 | AS43996 | — |
| 2a01:5041:9::/48 | AS43996 | — |
| 37.10.0.0/24 | AS43996 | — |
| 37.10.13.0/24 | AS43996 | — |
| 37.10.36.0/24 | AS43996 | — |
| 37.10.37.0/24 | AS43996 | — |
| 37.10.38.0/24 | AS43996 | — |
| 37.10.56.0/23 | AS43996 | — |
| 37.10.56.0/24 | AS43996 | — |
| 37.10.57.0/24 | AS43996 | — |
| 37.10.58.0/24 | AS43996 | — |
| 37.10.60.0/23 | AS43996 | — |
| 37.10.61.0/24 | AS43996 | — |
| 5.57.16.0/22 | AS43996 | — |
| 5.57.16.0/24 | AS43996 | — |
| 5.57.17.0/24 | AS43996 | — |
| 5.57.18.0/24 | AS43996 | — |
| 5.57.19.0/24 | AS43996 | — |
| 5.57.22.0/24 | AS43996 | — |
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.
AS43996 is an autonomous system number used to identify an independently operated network. The current page associates it with BOOKING-BV - Booking.com BV 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 AS43996. 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 AS43996, 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.