asn.dev

Observed topology

AS8399 SEWAN-

Unclassified RIPE

Upstreams 33 carry this network
Downstreams 0 this network carries
Adjacent (IPv4) 26
Adjacent (IPv6) 23
Upstream graph Who carries AS8399, and who carries them, drawn as a map up to the transit-free core. 8 exchanges Where AS8399 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

All 33

Networks observed carrying traffic for AS8399: 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 IPv6521
AS6939Hurricane Electric LLCTransitIPv4 IPv6260
AS2914NTT America, Inc.TransitIPv4203
AS174Cogent Communications, LLCTransitIPv4 IPv6173
AS3257GTT Communications Inc.TransitIPv4 IPv6142
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv6103
AS33891Core-Backbone GmbHHostingIPv437
AS24482SG.GSHostingIPv4 IPv636
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv635
AS35699Adamo Telecom Iberia S.A.UnclassifiedIPv4 IPv633

All 33 upstreams →

Transit

Downstream networks

inferred

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

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

All 33

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

ASNetworkTypeFamiliesPaths seen
AS1299Arelion Sweden ABTransitIPv4 IPv6521
AS6939Hurricane Electric LLCTransitIPv4 IPv6260
AS2914NTT America, Inc.TransitIPv4203
AS174Cogent Communications, LLCTransitIPv4 IPv6173
AS3257GTT Communications Inc.TransitIPv4 IPv6142
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv6103
AS33891Core-Backbone GmbHHostingIPv437
AS24482SG.GSHostingIPv4 IPv636
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv635
AS35699Adamo Telecom Iberia S.A.UnclassifiedIPv4 IPv633

All 33 adjacent →

Provenance

Where this comes from

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