asn.dev

Observed topology

AS51409 SIPSYNERGY

Unclassified RIPE NSP

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

Transit

Upstream networks

All 19

Networks observed carrying traffic for AS51409: 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
AS13335Cloudflare, Inc.HostingIPv4260
AS174Cogent Communications, LLCTransitIPv4145
AS2914NTT America, Inc.TransitIPv4127
AS6939Hurricane Electric LLCTransitIPv464
AS34549meerfarbig GmbH & Co. KGHostingIPv424
AS50304Blix Solutions ASUnclassifiedIPv416
AS3216PJSC "Vimpelcom"MobileIPv48
AS3741Dimension DataUnclassifiedIPv48
AS4657StarHub LtdResidentialIPv48
AS12552GlobalConnect ABUnclassifiedIPv48

Transit

Downstream networks

inferred

Networks for which AS51409 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 19

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

ASNetworkTypeFamiliesPaths seen
AS13335Cloudflare, Inc.HostingIPv4260
AS174Cogent Communications, LLCTransitIPv4145
AS2914NTT America, Inc.TransitIPv4127
AS6939Hurricane Electric LLCTransitIPv464
AS34549meerfarbig GmbH & Co. KGHostingIPv424
AS50304Blix Solutions ASUnclassifiedIPv416
AS3216PJSC "Vimpelcom"MobileIPv48
AS3741Dimension DataUnclassifiedIPv48
AS4657StarHub LtdResidentialIPv48
AS12552GlobalConnect ABUnclassifiedIPv48

Provenance

Where this comes from

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