asn.dev

Observed topology

AS202196 BOOKING-BV

Unclassified RIPE

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

Transit

Upstream networks

All 32

Networks observed carrying traffic for AS202196: 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 IPv6744
AS6461Zayo BandwidthTransitIPv4 IPv6582
AS4637Telstra GlobalUnclassifiedIPv4 IPv6339
AS1299Arelion Sweden ABTransitIPv4 IPv6309
AS6939Hurricane Electric LLCTransitIPv4 IPv6290
AS174Cogent Communications, LLCTransitIPv4 IPv6261
AS7473Singapore Telecommunications LtdUnclassifiedIPv4 IPv6174
AS58453China Mobile International LimitedUnclassifiedIPv4 IPv6152
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv4 IPv6125
AS23005SWITCH, LTDUnclassifiedIPv4 IPv6122

Transit

Downstream networks

inferred

Networks for which AS202196 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 32

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

ASNetworkTypeFamiliesPaths seen
AS3356Level 3 Parent, LLCTransitIPv4 IPv6744
AS6461Zayo BandwidthTransitIPv4 IPv6582
AS4637Telstra GlobalUnclassifiedIPv4 IPv6339
AS1299Arelion Sweden ABTransitIPv4 IPv6309
AS6939Hurricane Electric LLCTransitIPv4 IPv6290
AS174Cogent Communications, LLCTransitIPv4 IPv6261
AS7473Singapore Telecommunications LtdUnclassifiedIPv4 IPv6174
AS58453China Mobile International LimitedUnclassifiedIPv4 IPv6152
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv4 IPv6125
AS23005SWITCH, LTDUnclassifiedIPv4 IPv6122

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-21 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.14M 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.