asn.dev

Observed topology

AS50144 UNIMATRIX-AS

Unclassified RIPE

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

Transit

Upstream networks

All 39

Networks observed carrying traffic for AS50144: 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
AS6939Hurricane Electric LLCTransitIPv4 IPv6123
AS2914NTT America, Inc.TransitIPv4 IPv676
AS3356Level 3 Parent, LLCTransitIPv4 IPv656
AS1299Arelion Sweden ABTransitIPv4 IPv653
AS7195EDGEUNO S.A.SUnclassifiedIPv4 IPv628
AS174Cogent Communications, LLCTransitIPv4 IPv626
AS5511Orange S.A.TransitIPv4 IPv622
AS6453TATA COMMUNICATIONS (AMERICA) INCTransitIPv4 IPv617
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv614
AS3320Deutsche Telekom AGMobileIPv4 IPv612

All 39 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS34655JWE S.a r.l.HostingIPv4 IPv61,246

Adjacency

Adjacent networks

All 44

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

ASNetworkTypeFamiliesPaths seen
AS34655JWE S.a r.l.HostingIPv4 IPv61,246
AS2914NTT America, Inc.TransitIPv4 IPv6323
AS6939Hurricane Electric LLCTransitIPv4 IPv6254
AS1299Arelion Sweden ABTransitIPv4 IPv6204
AS3356Level 3 Parent, LLCTransitIPv4 IPv691
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv690
AS7195EDGEUNO S.A.SUnclassifiedIPv4 IPv678
AS50304Blix Solutions ASUnclassifiedIPv4 IPv662
AS174Cogent Communications, LLCTransitIPv4 IPv650
AS1273IDDQD-ASBusinessIPv448

All 44 adjacent →

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-26 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.