asn.dev

Observed topology

AS13896 8X8-FUZE

Unclassified ARIN NSP

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

Transit

Upstream networks

All 28

Networks observed carrying traffic for AS13896: 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
AS2914NTT America, Inc.TransitIPv4424
AS3356Level 3 Parent, LLCTransitIPv4380
AS6939Hurricane Electric LLCTransitIPv4174
AS34549meerfarbig GmbH & Co. KGHostingIPv469
AS49915Megaport (UK) LimitedUnclassifiedIPv457
AS7473Singapore Telecommunications LtdUnclassifiedIPv451
AS24482SG.GSHostingIPv424
AS37100SEACOM LimitedUnclassifiedIPv424
AS37721Virtual Technologies & SolutionsResidentialIPv424
AS48362Stadtwerke FeldkirchResidentialIPv423

All 28 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS1985548X8 UK LimitedHostingIPv44

Adjacency

Adjacent networks

All 29

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

ASNetworkTypeFamiliesPaths seen
AS2914NTT America, Inc.TransitIPv4427
AS3356Level 3 Parent, LLCTransitIPv4380
AS6939Hurricane Electric LLCTransitIPv4174
AS34549meerfarbig GmbH & Co. KGHostingIPv469
AS49915Megaport (UK) LimitedUnclassifiedIPv457
AS7473Singapore Telecommunications LtdUnclassifiedIPv451
AS24482SG.GSHostingIPv424
AS37100SEACOM LimitedUnclassifiedIPv424
AS37721Virtual Technologies & SolutionsResidentialIPv424
AS48362Stadtwerke FeldkirchResidentialIPv423

All 29 adjacent →

Provenance

Where this comes from

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