asn.dev

Observed topology

AS47747 TMK-NET-AS

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS47747: 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
AS20764CJSC RASCOMUnclassifiedIPv4 IPv6175
AS57304JSC "RetnNet"UnclassifiedIPv4 IPv6111
AS29226JSC MastertelUnclassifiedIPv4108
AS6939Hurricane Electric LLCTransitIPv414
AS9002RETN LimitedUnclassifiedIPv4 IPv611
AS24482SG.GSHostingIPv44
AS37721Virtual Technologies & SolutionsResidentialIPv44
AS47989Mosinfocom LlcResidentialIPv44
AS34927iFog GmbHHostingIPv41

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS12836TELECOM-2 LLCUnclassifiedIPv4122
AS200401Kazakov Aleksey AlexandrovichUnclassifiedIPv4122
AS47989Mosinfocom LlcResidentialIPv46

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS20764CJSC RASCOMUnclassifiedIPv4 IPv6303
AS29226JSC MastertelUnclassifiedIPv4162
AS57304JSC "RetnNet"UnclassifiedIPv4 IPv6143
AS12836TELECOM-2 LLCUnclassifiedIPv4122
AS200401Kazakov Aleksey AlexandrovichUnclassifiedIPv4122
AS6939Hurricane Electric LLCTransitIPv438
AS9002RETN LimitedUnclassifiedIPv4 IPv617
AS47989Mosinfocom LlcResidentialIPv412
AS24482SG.GSHostingIPv48
AS37721Virtual Technologies & SolutionsResidentialIPv48

All 11 adjacent →

Provenance

Where this comes from

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