asn.dev

Observed topology

AS43996 Booking-BV Booking.com BV

Hosting RIPE

Upstreams 18 carry this network
Downstreams 0 this network carries
Adjacent (IPv4) 17
Adjacent (IPv6) 10
Upstream graph Who carries AS43996, and who carries them, drawn as a map up to the transit-free core. 9 exchanges Where AS43996 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

All 18

Networks observed carrying traffic for AS43996: the AS immediately before it in a routing path. Ranked by how many paths showed the relationship, which reflects how widely it is used, not how much traffic crosses it.

ASNetworkTypeFamiliesPaths seen
AS3356Level 3 Parent, LLCTransitIPv4 IPv6211
AS6461Zayo BandwidthTransitIPv4 IPv6210
AS6939Hurricane Electric LLCTransitIPv4 IPv6173
AS3320Deutsche Telekom AGMobileIPv4 IPv6150
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv4 IPv6102
AS9002RETN LimitedUnclassifiedIPv4 IPv659
AS1836green.ch AGResidentialIPv4 IPv619
AS33891Core-Backbone GmbHHostingIPv417
AS42708Glesys Sweden ABUnclassifiedIPv4 IPv616
AS50304Blix Solutions ASUnclassifiedIPv4 IPv616

All 18 upstreams →

Transit

Downstream networks

inferred

Networks for which AS43996 was observed as the last hop before the origin, meaning it appears to provide them transit.

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

All 18

Every AS seen directly next to AS43996 in a routing path, in either direction.

ASNetworkTypeFamiliesPaths seen
AS3356Level 3 Parent, LLCTransitIPv4 IPv6211
AS6461Zayo BandwidthTransitIPv4 IPv6210
AS6939Hurricane Electric LLCTransitIPv4 IPv6173
AS3320Deutsche Telekom AGMobileIPv4 IPv6150
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv4 IPv6102
AS9002RETN LimitedUnclassifiedIPv4 IPv659
AS1836green.ch AGResidentialIPv4 IPv619
AS33891Core-Backbone GmbHHostingIPv417
AS42708Glesys Sweden ABUnclassifiedIPv4 IPv616
AS50304Blix Solutions ASUnclassifiedIPv4 IPv616

All 18 adjacent →

Provenance

Where this comes from

Derived from routing tables collected at 2026-11-09 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.03M route entries. These are observations from those vantage points, not a complete or authoritative view of the internet.

Inferred from path position, not from any declaration by either party. A network appearing here is carrying these routes; whether that is a paid transit arrangement, a backup, or something else is not something routing data can tell you. Adjacency is not the same as peering. Being next to each other in a path covers paid transit, settlement-free peering and customer connections alike, and routing data cannot distinguish them. Treat this as "these networks exchange routes", nothing more specific.

Cross-check against RIPEstat or BGP.tools, which observe from a different and larger set of vantage points.