asn.dev

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.

ASNetworkTypeFamiliesPaths seen
AS1299Arelion Sweden ABTransitIPv4 IPv61,207
AS12578SIA TetResidentialIPv4 IPv699

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.

ASNetworkTypeFamiliesPaths seen
AS34001SIA LIVAS NETUnclassifiedIPv4 IPv6272
AS47499SIA ILVA Ltd.UnclassifiedIPv4180
AS51894Mikrotikls SIAUnclassifiedIPv4 IPv6152
AS2877LSC SIAUnclassifiedIPv460
AS15827SIA "Biznesa augstskola Turiba"UnclassifiedIPv460
AS25107AS "Industra Bank"UnclassifiedIPv460
AS35809SIA "DIVI Grupa"UnclassifiedIPv460
AS44483Elektrons K SIAUnclassifiedIPv460
AS211424SIA "LSK Studios"UnclassifiedIPv460
AS197616Optrix SIAUnclassifiedIPv452

Adjacency

Adjacent networks

All 24

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

ASNetworkTypeFamiliesPaths seen
AS1299Arelion Sweden ABTransitIPv4 IPv62,505
AS34001SIA LIVAS NETUnclassifiedIPv4 IPv6272
AS47499SIA ILVA Ltd.UnclassifiedIPv4180
AS51894Mikrotikls SIAUnclassifiedIPv4 IPv6152
AS12578SIA TetResidentialIPv4 IPv6100
AS35407Santa Monica Networks SIAResidentialIPv468
AS2877LSC SIAUnclassifiedIPv460
AS15827SIA "Biznesa augstskola Turiba"UnclassifiedIPv460
AS25107AS "Industra Bank"UnclassifiedIPv460
AS35809SIA "DIVI Grupa"UnclassifiedIPv460

Provenance

Where this comes from

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