asn.dev

Observed topology

AS51310 MATRONIX-AS

Unclassified RIPE

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

Transit

Upstream networks

All 17

Networks observed carrying traffic for AS51310: 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
AS174Cogent Communications, LLCTransitIPv4178
AS6453TATA COMMUNICATIONS (AMERICA) INCTransitIPv483
AS6939Hurricane Electric LLCTransitIPv456
AS1299Arelion Sweden ABTransitIPv427
AS34549meerfarbig GmbH & Co. KGHostingIPv424
AS1836green.ch AGResidentialIPv48
AS6797GlobalConnect ABUnclassifiedIPv48
AS12779IT.Gate S.p.A.UnclassifiedIPv48
AS12859BIT BVHostingIPv48
AS20485Joint Stock Company TransTeleComUnclassifiedIPv48

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS198857NOWOGROD.NET SP. Z O.O.ResidentialIPv426

Adjacency

Adjacent networks

All 20

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

ASNetworkTypeFamiliesPaths seen
AS174Cogent Communications, LLCTransitIPv4204
AS6453TATA COMMUNICATIONS (AMERICA) INCTransitIPv483
AS6939Hurricane Electric LLCTransitIPv456
AS34549meerfarbig GmbH & Co. KGHostingIPv430
AS1299Arelion Sweden ABTransitIPv427
AS198857NOWOGROD.NET SP. Z O.O.ResidentialIPv426
AS51465M3.NET Sp. zooHostingIPv412
AS20485Joint Stock Company TransTeleComUnclassifiedIPv410
AS37100SEACOM LimitedUnclassifiedIPv410
AS1836green.ch AGResidentialIPv48

Provenance

Where this comes from

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