asn.dev

Observed topology

AS208592 AS-AVESTONET KAZTRANSCOM

Unclassified RIPE Network Services

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS208592: 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
AS205103Telegraph42 Management GmbHUnclassifiedIPv4384

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS24722LLC Babilon-TUnclassifiedIPv4 IPv64,122
AS34557Tacom LLCUnclassifiedIPv4 IPv61,234
AS57972Angelnet LimitedUnclassifiedIPv464
AS60101Dushanbe City Bank CJSCUnclassifiedIPv464
AS202331Dushanbe City Bank CJSCUnclassifiedIPv464
AS213631LLC "KOINOT INNOVATION AND TECHNOLOGY"UnclassifiedIPv464
AS215095Seganj LLCUnclassifiedIPv464
AS199793Bank Eskhata OJSCUnclassifiedIPv460
AS8847CJSC "Telecomm Technology"UnclassifiedIPv47

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS205103Telegraph42 Management GmbHUnclassifiedIPv4 IPv66,616
AS24722LLC Babilon-TUnclassifiedIPv4 IPv64,640
AS34557Tacom LLCUnclassifiedIPv4 IPv61,234
AS51346Opened Joint Stock Company "Tojiktelecom"UnclassifiedIPv493
AS57972Angelnet LimitedUnclassifiedIPv464
AS60101Dushanbe City Bank CJSCUnclassifiedIPv464
AS202331Dushanbe City Bank CJSCUnclassifiedIPv464
AS213631LLC "KOINOT INNOVATION AND TECHNOLOGY"UnclassifiedIPv464
AS215095Seganj LLCUnclassifiedIPv464
AS199793Bank Eskhata OJSCUnclassifiedIPv460

All 11 adjacent →

Provenance

Where this comes from

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