asn.dev

Observed topology

AS47809 EAST-AS Private Enterprise Matsak Ivan Anatolievich

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS47809: 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 LLCUnclassifiedIPv458
AS41039Timer, LLCUnclassifiedIPv42
AS12773Meshnet ltd.UnclassifiedIPv41
AS24482SG.GSHostingIPv41
AS37721Virtual Technologies & SolutionsResidentialIPv41

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS50780EAST-NET LtdUnclassifiedIPv4584
AS59478LLC IP SERVICEUnclassifiedIPv4419

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS50780EAST-NET LtdUnclassifiedIPv4584
AS44539Redi LLCUnclassifiedIPv4525
AS59478LLC IP SERVICEUnclassifiedIPv4419
AS12773Meshnet ltd.UnclassifiedIPv4307
AS41039Timer, LLCUnclassifiedIPv4185
AS24482SG.GSHostingIPv414
AS37721Virtual Technologies & SolutionsResidentialIPv414
AS8732JSC ComcorUnclassifiedIPv47
AS25091IP-Max SAUnclassifiedIPv47
AS34927iFog GmbHHostingIPv47

Provenance

Where this comes from

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