asn.dev

Observed topology

AS44056 TRYTECH-AS

Unclassified ARIN

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

Transit

Upstream networks

All 16

Networks observed carrying traffic for AS44056: 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
AS20485Joint Stock Company TransTeleComUnclassifiedIPv4 IPv61,085
AS28917Fiord Networks, UABUnclassifiedIPv4 IPv6465
AS31133PJSC MegaFonMobileIPv4 IPv6431
AS20764CJSC RASCOMUnclassifiedIPv4163
AS3216PJSC "Vimpelcom"MobileIPv4 IPv6156
AS8641LLC "Nauka-Svyaz"UnclassifiedIPv4122
AS6939Hurricane Electric LLCTransitIPv4106
AS1299Arelion Sweden ABTransitIPv465
AS37721Virtual Technologies & SolutionsResidentialIPv418
AS24482SG.GSHostingIPv417

All 16 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS56676OOO Modern Communication SystemsUnclassifiedIPv4187
AS57629LLC IVI.RUHostingIPv633

Adjacency

Adjacent networks

All 18

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

ASNetworkTypeFamiliesPaths seen
AS20485Joint Stock Company TransTeleComUnclassifiedIPv4 IPv61,100
AS28917Fiord Networks, UABUnclassifiedIPv4 IPv6510
AS31133PJSC MegaFonMobileIPv4 IPv6431
AS20764CJSC RASCOMUnclassifiedIPv4269
AS56676OOO Modern Communication SystemsUnclassifiedIPv4187
AS3216PJSC "Vimpelcom"MobileIPv4 IPv6167
AS8641LLC "Nauka-Svyaz"UnclassifiedIPv4122
AS6939Hurricane Electric LLCTransitIPv4106
AS1299Arelion Sweden ABTransitIPv4102
AS57629LLC IVI.RUHostingIPv633

All 18 adjacent →

Provenance

Where this comes from

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