asn.dev

Observed topology

AS44056 TRYTECH-AS Trytek LLC

Unclassified ARIN

Upstreams 17 carry this network
Downstreams 4 this network carries
Adjacent (IPv4) 20
Adjacent (IPv6) 6
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 17

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,071
AS31133PJSC MegaFonMobileIPv4 IPv6610
AS28917Fiord Networks, UABUnclassifiedIPv4 IPv6461
AS3216PJSC "Vimpelcom"MobileIPv4 IPv6177
AS20764CJSC RASCOMUnclassifiedIPv4124
AS8641LLC "Nauka-Svyaz"UnclassifiedIPv4 IPv693
AS6939Hurricane Electric LLCTransitIPv480
AS1299Arelion Sweden ABTransitIPv440
AS37721Virtual Technologies & SolutionsResidentialIPv418
AS24482SG.GSHostingIPv417

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
AS34771Megaseti Ltd.UnclassifiedIPv433
AS57629LLC IVI.RUHostingIPv632
AS41560UGMK-Telecom LLCUnclassifiedIPv41

Adjacency

Adjacent networks

All 21

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

ASNetworkTypeFamiliesPaths seen
AS20485Joint Stock Company TransTeleComUnclassifiedIPv4 IPv61,102
AS31133PJSC MegaFonMobileIPv4 IPv6610
AS28917Fiord Networks, UABUnclassifiedIPv4 IPv6519
AS3216PJSC "Vimpelcom"MobileIPv4 IPv6229
AS20764CJSC RASCOMUnclassifiedIPv4204
AS56676OOO Modern Communication SystemsUnclassifiedIPv4187
AS8641LLC "Nauka-Svyaz"UnclassifiedIPv4 IPv693
AS6939Hurricane Electric LLCTransitIPv482
AS1299Arelion Sweden ABTransitIPv464
AS34771Megaseti Ltd.UnclassifiedIPv433

Provenance

Where this comes from

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