asn.dev

Observed topology

AS209554 ISIF-AS

Residential RIPE

Upstreams 6 carry this network
Downstreams 3 this network carries
Adjacent (IPv4) 4
Adjacent (IPv6) 10
Upstream graph Who carries AS209554, and who carries them, drawn as a map up to the transit-free core. 1 exchange Where AS209554 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS209554: 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
AS4743ISIF LIMITEDUnclassifiedIPv4 IPv61,350
AS49304SAKURA LINK LIMITEDUnclassifiedIPv4 IPv61,016
AS3204xTom OUHostingIPv674
AS7720Skywolf Technology LLCUnclassifiedIPv632
AS199854Jens ThiesUnclassifiedIPv62
AS401753BIXCE IncUnclassifiedIPv62

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS214731ETO Networks LimitedUnclassifiedIPv6140
AS154162ISIF LIMITEDUnclassifiedIPv4 IPv696
AS204921zhenyun sunUnclassifiedIPv635

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS4743ISIF LIMITEDUnclassifiedIPv4 IPv62,018
AS49304SAKURA LINK LIMITEDUnclassifiedIPv4 IPv61,017
AS27345SPICA Industry LLCUnclassifiedIPv4 IPv6396
AS214731ETO Networks LimitedUnclassifiedIPv6140
AS154162ISIF LIMITEDUnclassifiedIPv4 IPv696
AS3204xTom OUHostingIPv674
AS204921zhenyun sunUnclassifiedIPv635
AS7720Skywolf Technology LLCUnclassifiedIPv632
AS199854Jens ThiesUnclassifiedIPv62
AS401753BIXCE IncUnclassifiedIPv62

Provenance

Where this comes from

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