Observed topology

AS206557 ELTELE Eltele AS

Unclassified ARIN

Upstreams 3 carry this network

Downstreams 4 this network carries

Adjacent (IPv4) 7

Adjacent (IPv6) 4

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS206557: 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
AS2116	GLOBALCONNECT AS	Residential	IPv4 IPv6	169
AS29695	Lyse Tele AS	Unclassified	IPv4 IPv6	129
AS6667	Elisa Oyj	Residential	IPv4 IPv6	94

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS205190	AKSA HJEM AS	Unclassified	IPv4 IPv6	90
AS204503	INFRANORD SA	Unclassified	IPv4	60
AS208835	InfraNord Fiber AS	Unclassified	IPv4	60
AS210615	Alta kommune	Unclassified	IPv4	2

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS2116	GLOBALCONNECT AS	Residential	IPv4 IPv6	250
AS6667	Elisa Oyj	Residential	IPv4 IPv6	185
AS29695	Lyse Tele AS	Unclassified	IPv4 IPv6	169
AS205190	AKSA HJEM AS	Unclassified	IPv4 IPv6	90
AS204503	INFRANORD SA	Unclassified	IPv4	60
AS208835	InfraNord Fiber AS	Unclassified	IPv4	60
AS210615	Alta kommune	Unclassified	IPv4	2

Provenance

Where this comes from

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