asn.dev

Observed topology

AS200478 TABOOLA-AS Taboola.com ltd

Unclassified RIPE

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

Transit

Upstream networks

All 28

Networks observed carrying traffic for AS200478: 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
AS1299Arelion Sweden ABTransitIPv4 IPv6172
AS174Cogent Communications, LLCTransitIPv4 IPv6134
AS6461Zayo BandwidthTransitIPv4115
AS6939Hurricane Electric LLCTransitIPv471
AS2914NTT America, Inc.TransitIPv464
AS12400Partner Communications Ltd.UnclassifiedIPv441
AS8551Bezeq International Ltd.UnclassifiedIPv422
AS24482SG.GSHostingIPv48
AS293ESnetUnclassifiedIPv42
AS17639Converge ICT Solutions Inc.UnclassifiedIPv42

Transit

Downstream networks

inferred

Networks for which AS200478 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 28

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

ASNetworkTypeFamiliesPaths seen
AS1299Arelion Sweden ABTransitIPv4 IPv6172
AS174Cogent Communications, LLCTransitIPv4 IPv6134
AS6461Zayo BandwidthTransitIPv4115
AS6939Hurricane Electric LLCTransitIPv471
AS2914NTT America, Inc.TransitIPv464
AS12400Partner Communications Ltd.UnclassifiedIPv441
AS8551Bezeq International Ltd.UnclassifiedIPv422
AS24482SG.GSHostingIPv48
AS293ESnetUnclassifiedIPv42
AS17639Converge ICT Solutions Inc.UnclassifiedIPv42

Provenance

Where this comes from

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