asn.dev

Observed topology

AS28886 RETN-LV RETN Limited

Unclassified RIPE

Upstreams 3 carry this network
Downstreams 7 this network carries
Adjacent (IPv4) 11
Adjacent (IPv6) 3
Upstream graph Who carries AS28886, and who carries them, drawn as a map up to the transit-free core. 2 exchanges Where AS28886 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS28886: 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
AS12578SIA TetResidentialIPv4 IPv645
AS9002RETN LimitedUnclassifiedIPv4 IPv632
AS6939Hurricane Electric LLCTransitIPv4 IPv617

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS203866Versija SIAUnclassifiedIPv4120
AS398452 Cloud Ltd.HostingIPv492
AS207066SOK, SIAUnclassifiedIPv423
AS51338SIA Latvijas Propana gazeUnclassifiedIPv411
AS41726SIA "B2 Impact"UnclassifiedIPv49
AS206804Realcloud OUUnclassifiedIPv44
AS210886AS Magnetiq BankUnclassifiedIPv44

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS12578SIA TetResidentialIPv4 IPv6239
AS9002RETN LimitedUnclassifiedIPv4 IPv6152
AS398452 Cloud Ltd.HostingIPv4121
AS203866Versija SIAUnclassifiedIPv4120
AS207066SOK, SIAUnclassifiedIPv423
AS15721C.T.CO. Ltd.UnclassifiedIPv422
AS6939Hurricane Electric LLCTransitIPv4 IPv617
AS51338SIA Latvijas Propana gazeUnclassifiedIPv411
AS41726SIA "B2 Impact"UnclassifiedIPv49
AS206804Realcloud OUUnclassifiedIPv44

All 11 adjacent →

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.