asn.dev

Observed topology

AS208959 SG-SLASHN

Unclassified RIPE

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

Transit

Upstream networks

All 26

Networks observed carrying traffic for AS208959: 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
AS13335Cloudflare, Inc.HostingIPv4455
AS1299Arelion Sweden ABTransitIPv4290
AS2914NTT America, Inc.TransitIPv4110
AS199524G-Core Labs S.A.HostingIPv458
AS4637Telstra GlobalUnclassifiedIPv454
AS3257GTT Communications Inc.TransitIPv438
AS174Cogent Communications, LLCTransitIPv414
AS50673Serverius Holding B.V.UnclassifiedIPv48
AS24482SG.GSHostingIPv47
AS293ESnetUnclassifiedIPv44

All 26 upstreams →

Transit

Downstream networks

inferred

Networks for which AS208959 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 26

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

ASNetworkTypeFamiliesPaths seen
AS13335Cloudflare, Inc.HostingIPv4455
AS1299Arelion Sweden ABTransitIPv4290
AS2914NTT America, Inc.TransitIPv4110
AS199524G-Core Labs S.A.HostingIPv458
AS4637Telstra GlobalUnclassifiedIPv454
AS3257GTT Communications Inc.TransitIPv438
AS174Cogent Communications, LLCTransitIPv414
AS50673Serverius Holding B.V.UnclassifiedIPv48
AS24482SG.GSHostingIPv47
AS293ESnetUnclassifiedIPv44

All 26 adjacent →

Provenance

Where this comes from

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