asn.dev

Observed topology

AS44050 PIN-AS

Residential RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS44050: 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
AS50509Transroute Telecom LTDUnclassifiedIPv4 IPv61,499
AS24482SG.GSHostingIPv4 IPv6102
AS37721Virtual Technologies & SolutionsResidentialIPv4100
AS8732JSC ComcorUnclassifiedIPv479
AS25091IP-Max SAUnclassifiedIPv479
AS34927iFog GmbHHostingIPv479

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS25073LTD "KOMIN"UnclassifiedIPv4471
AS44068Petersburg Internet Network ltd.ResidentialIPv4 IPv6232
AS207853"NPO Unimach" LLCUnclassifiedIPv4 IPv694
AS34866Master IT LtdUnclassifiedIPv465
AS47528Piter-IX Co. Ltd.UnclassifiedIPv465
AS31503Master IT Ltd.UnclassifiedIPv445
AS207822"NPK Morsvyazavtomatica" LLCUnclassifiedIPv4 IPv66
AS214356Vyaznikov Maxim NikolaevichUnclassifiedIPv41

Adjacency

Adjacent networks

All 14

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

ASNetworkTypeFamiliesPaths seen
AS50509Transroute Telecom LTDUnclassifiedIPv4 IPv62,435
AS25073LTD "KOMIN"UnclassifiedIPv4471
AS44068Petersburg Internet Network ltd.ResidentialIPv4 IPv6232
AS24482SG.GSHostingIPv4 IPv6121
AS37721Virtual Technologies & SolutionsResidentialIPv4116
AS207853"NPO Unimach" LLCUnclassifiedIPv4 IPv694
AS25091IP-Max SAUnclassifiedIPv483
AS34927iFog GmbHHostingIPv483
AS8732JSC ComcorUnclassifiedIPv479
AS34866Master IT LtdUnclassifiedIPv465

All 14 adjacent →

Provenance

Where this comes from

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