asn.dev

Observed topology

AS12365 SARKOR-AS Sarkor Telecom - Uztelecom, Upstream

Hosting RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS12365: 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
AS28910"Uzbektelekom" Joint Stock CompanyUnclassifiedIPv4 IPv61,351

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS43647"SERVERCORE CIS" FE LLCUnclassifiedIPv41,839
AS58330DP AlNetUnclassifiedIPv4322
AS213870UZUM MARKET FE LLCUnclassifiedIPv4248
AS61106PS Cloud Services LLCUnclassifiedIPv4122
AS21859Zenlayer IncHostingIPv4 IPv699
AS208831Afzal Cloud Technologies LLCUnclassifiedIPv462

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS28910"Uzbektelekom" Joint Stock CompanyUnclassifiedIPv4 IPv64,303
AS43647"SERVERCORE CIS" FE LLCUnclassifiedIPv41,839
AS21859Zenlayer IncHostingIPv4 IPv6359
AS58330DP AlNetUnclassifiedIPv4322
AS213870UZUM MARKET FE LLCUnclassifiedIPv4248
AS61106PS Cloud Services LLCUnclassifiedIPv4122
AS208831Afzal Cloud Technologies LLCUnclassifiedIPv462

Provenance

Where this comes from

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