Observed topology

AS5518 TET_LV SIA Tet

Residential RIPE

Upstreams 2 carry this network

Downstreams 22 this network carries

Adjacent (IPv4) 24

Adjacent (IPv6) 4

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS5518: 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
AS1299	Arelion Sweden AB	Transit	IPv4 IPv6	1,165
AS12578	SIA Tet	Residential	IPv4 IPv6	97

Transit

Downstream networks

All 22

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

AS	Network	Type	Families	Paths seen
AS34001	SIA LIVAS NET	Unclassified	IPv4 IPv6	261
AS47499	SIA ILVA Ltd.	Unclassified	IPv4	174
AS51894	Mikrotikls SIA	Unclassified	IPv4 IPv6	145
AS25107	AS "Industra Bank"	Unclassified	IPv4	58
AS35809	SIA "DIVI Grupa"	Unclassified	IPv4	58
AS211424	SIA "LSK Studios"	Unclassified	IPv4	58
AS2877	LSC SIA	Unclassified	IPv4	57
AS15827	SIA "Biznesa augstskola Turiba"	Unclassified	IPv4	57
AS44483	Elektrons K SIA	Unclassified	IPv4	57
AS197616	Optrix SIA	Unclassified	IPv4	49

All 22 downstreams →

Adjacency

Adjacent networks

All 24

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

AS	Network	Type	Families	Paths seen
AS1299	Arelion Sweden AB	Transit	IPv4 IPv6	2,414
AS34001	SIA LIVAS NET	Unclassified	IPv4 IPv6	261
AS47499	SIA ILVA Ltd.	Unclassified	IPv4	174
AS51894	Mikrotikls SIA	Unclassified	IPv4 IPv6	145
AS12578	SIA Tet	Residential	IPv4 IPv6	98
AS35407	Santa Monica Networks SIA	Residential	IPv4	68
AS25107	AS "Industra Bank"	Unclassified	IPv4	58
AS35809	SIA "DIVI Grupa"	Unclassified	IPv4	58
AS211424	SIA "LSK Studios"	Unclassified	IPv4	58
AS2877	LSC SIA	Unclassified	IPv4	57

All 24 adjacent →

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.