asn.dev

Observed topology

AS28745 SUTTK-AS Joint Stock Company TransTeleCom

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS28745: 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
AS20485Joint Stock Company TransTeleComUnclassifiedIPv4 IPv63,082

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS44172Courier Plus Ltd.UnclassifiedIPv4939
AS51690Applied Technologies, Ltd.UnclassifiedIPv4232
AS31470JSC Chelyabinsk Electric-Metallurgical KombinatUnclassifiedIPv4108
AS15774Limited Liability Company "TTK-Svyaz"UnclassifiedIPv460
AS207128Streamlet Ltd.UnclassifiedIPv457
AS21023Joint Stock Company Ural Industrial BankUnclassifiedIPv411
AS8369Intersvyaz-2 JSCResidentialIPv48

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS20485Joint Stock Company TransTeleComUnclassifiedIPv4 IPv64,510
AS44172Courier Plus Ltd.UnclassifiedIPv4952
AS51690Applied Technologies, Ltd.UnclassifiedIPv4232
AS31470JSC Chelyabinsk Electric-Metallurgical KombinatUnclassifiedIPv4108
AS15774Limited Liability Company "TTK-Svyaz"UnclassifiedIPv460
AS207128Streamlet Ltd.UnclassifiedIPv457
AS21023Joint Stock Company Ural Industrial BankUnclassifiedIPv411
AS8369Intersvyaz-2 JSCResidentialIPv48

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.