Observed topology

AS28745 SUTTK-AS

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.

AS	Network	Type	Families	Paths seen
AS20485	Joint Stock Company TransTeleCom	Unclassified	IPv4 IPv6	3,188

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS44172	Courier Plus Ltd.	Unclassified	IPv4	819
AS51690	Applied Technologies, Ltd.	Unclassified	IPv4	240
AS31470	JSC Chelyabinsk Electric-Metallurgical Kombinat	Unclassified	IPv4	114
AS15774	Limited Liability Company "TTK-Svyaz"	Unclassified	IPv4	62
AS207128	Streamlet Ltd.	Unclassified	IPv4	60
AS21023	Joint Stock Company Ural Industrial Bank	Unclassified	IPv4	12
AS8369	Intersvyaz-2 JSC	Residential	IPv4	1

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS20485	Joint Stock Company TransTeleCom	Unclassified	IPv4 IPv6	4,512
AS44172	Courier Plus Ltd.	Unclassified	IPv4	835
AS51690	Applied Technologies, Ltd.	Unclassified	IPv4	240
AS31470	JSC Chelyabinsk Electric-Metallurgical Kombinat	Unclassified	IPv4	114
AS15774	Limited Liability Company "TTK-Svyaz"	Unclassified	IPv4	62
AS207128	Streamlet Ltd.	Unclassified	IPv4	60
AS21023	Joint Stock Company Ural Industrial Bank	Unclassified	IPv4	12
AS8369	Intersvyaz-2 JSC	Residential	IPv4	1

Provenance

Where this comes from

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