Observed topology

AS62077 DTI-DC-PEERING

Unclassified RIPE

Upstreams 6 carry this network

Downstreams 2 this network carries

Adjacent (IPv4) 8

Adjacent (IPv6) 0

Upstream graph Who carries AS62077, and who carries them, drawn as a map up to the transit-free core. 0 exchanges Where AS62077 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS62077: 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
AS15924	Vodafone Net Iletisim Hizmetler AS	Unclassified	IPv4	156
AS59796	StormWall s.r.o.	Unclassified	IPv4	58
AS34984	Superonline Iletisim Hizmetleri A.S.	Mobile	IPv4	38
AS62095	DT Iletisim Hizmetleri A.S.	Unclassified	IPv4	27
AS12735	TurkNet Iletisim Hizmetleri A.S.	Unclassified	IPv4	24
AS43298	Storm Networks LLC	Unclassified	IPv4	1

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS50540	DT Iletisim Hizmetleri A.S.	Unclassified	IPv4	61
AS60442	DT Teknoloji Anonim Sirketi	Unclassified	IPv4	59

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS15924	Vodafone Net Iletisim Hizmetler AS	Unclassified	IPv4	217
AS34984	Superonline Iletisim Hizmetleri A.S.	Mobile	IPv4	97
AS50540	DT Iletisim Hizmetleri A.S.	Unclassified	IPv4	61
AS60442	DT Teknoloji Anonim Sirketi	Unclassified	IPv4	59
AS59796	StormWall s.r.o.	Unclassified	IPv4	58
AS62095	DT Iletisim Hizmetleri A.S.	Unclassified	IPv4	27
AS12735	TurkNet Iletisim Hizmetleri A.S.	Unclassified	IPv4	24
AS43298	Storm Networks LLC	Unclassified	IPv4	1

Provenance

Where this comes from

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