asn.dev

Observed topology

AS12773 MM-AS Meshnet ltd.

Unclassified RIPE NSP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS12773: 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
AS44539Redi LLCUnclassifiedIPv4448
AS24482SG.GSHostingIPv47
AS37721Virtual Technologies & SolutionsResidentialIPv47

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS25141Teleradiocompany Soniko-Svyaz LtdUnclassifiedIPv4264
AS49757Igor UspenskyyUnclassifiedIPv4264
AS60839Vid Media Ltd.UnclassifiedIPv4264
AS57005PE Homich Nataliya G.UnclassifiedIPv4144
AS34786OOO NPO IntermetUnclassifiedIPv482
AS31113Artkomm LLCUnclassifiedIPv466
AS44710TRK Sirius LTDUnclassifiedIPv466
AS52213LLC DONETSK FIBER-OPTICAL NETWORKUnclassifiedIPv433
AS44884Regional Online Systems Ltd.UnclassifiedIPv426
AS47809Private Enterprise Matsak Ivan AnatolievichUnclassifiedIPv41

Adjacency

Adjacent networks

All 17

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

ASNetworkTypeFamiliesPaths seen
AS44539Redi LLCUnclassifiedIPv41,946
AS47809Private Enterprise Matsak Ivan AnatolievichUnclassifiedIPv4316
AS25141Teleradiocompany Soniko-Svyaz LtdUnclassifiedIPv4264
AS49757Igor UspenskyyUnclassifiedIPv4264
AS60839Vid Media Ltd.UnclassifiedIPv4264
AS57005PE Homich Nataliya G.UnclassifiedIPv4144
AS211692Level-Donetsk Ltd.UnclassifiedIPv4136
AS34786OOO NPO IntermetUnclassifiedIPv494
AS6939Hurricane Electric LLCTransitIPv478
AS31113Artkomm LLCUnclassifiedIPv466

Provenance

Where this comes from

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