Observed topology

AS51373 TELKONEKT-AS TELKONEKT Autonomous System

Unclassified RIPE

Upstreams 3 carry this network

Downstreams 4 this network carries

Adjacent (IPv4) 8

Adjacent (IPv6) 2

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS51373: 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
AS29535	Orange Polska Spolka Akcyjna	Unclassified	IPv4	585
AS20804	Exatel S.A.	Unclassified	IPv4 IPv6	313
AS24482	SG.GS	Hosting	IPv4	13

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS203210	"SZYBKI-NET S. BAJOR L. SIWIK Z. WIECZOREK" SPOLKA JAWNA	Residential	IPv4	357
AS34530	Asseco Cloud Sp. z o. o.	Unclassified	IPv4 IPv6	129
AS41149	VESCOM SPOLKA Z OGRANICZONA ODPOWIEDZIALNOSCIA SPOLKA KOMANDYTOWA	Unclassified	IPv4	60
AS43492	"Electronics Box" Magierski, Majewski, Magierski spolka jawna	Unclassified	IPv4	50

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS29535	Orange Polska Spolka Akcyjna	Unclassified	IPv4	851
AS20804	Exatel S.A.	Unclassified	IPv4 IPv6	634
AS203210	"SZYBKI-NET S. BAJOR L. SIWIK Z. WIECZOREK" SPOLKA JAWNA	Residential	IPv4	357
AS34530	Asseco Cloud Sp. z o. o.	Unclassified	IPv4 IPv6	129
AS41149	VESCOM SPOLKA Z OGRANICZONA ODPOWIEDZIALNOSCIA SPOLKA KOMANDYTOWA	Unclassified	IPv4	60
AS43492	"Electronics Box" Magierski, Majewski, Magierski spolka jawna	Unclassified	IPv4	50
AS24482	SG.GS	Hosting	IPv4	15
AS6939	Hurricane Electric LLC	Transit	IPv4	7

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.