asn.dev

Observed topology

AS53334 TUT-AS

Unclassified APNIC NSP

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

Transit

Upstream networks

All 35

Networks observed carrying traffic for AS53334: 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.TransitIPv4 IPv62,081
AS6939Hurricane Electric LLCTransitIPv4 IPv6208
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv4 IPv6194
AS1299Arelion Sweden ABTransitIPv4 IPv6190
AS174Cogent Communications, LLCTransitIPv4 IPv654
AS17378TierPoint, LLCHostingIPv4 IPv638
AS19122eStruxture Data Centers Inc.HostingIPv4 IPv622
AS14907Wikimedia Foundation Inc.HostingIPv4 IPv615
AS24482SG.GSHostingIPv4 IPv614
AS37100SEACOM LimitedUnclassifiedIPv414

All 35 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS29755Southwest Dispatch CenterUnclassifiedIPv459
AS394483Doyle Security Systems, Inc.UnclassifiedIPv45

Adjacency

Adjacent networks

All 37

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

ASNetworkTypeFamiliesPaths seen
AS2914NTT America, Inc.TransitIPv4 IPv62,114
AS6939Hurricane Electric LLCTransitIPv4 IPv6217
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv4 IPv6215
AS1299Arelion Sweden ABTransitIPv4 IPv6190
AS29755Southwest Dispatch CenterUnclassifiedIPv459
AS174Cogent Communications, LLCTransitIPv4 IPv654
AS17378TierPoint, LLCHostingIPv4 IPv638
AS19122eStruxture Data Centers Inc.HostingIPv4 IPv622
AS14907Wikimedia Foundation Inc.HostingIPv4 IPv616
AS24482SG.GSHostingIPv4 IPv614

All 37 adjacent →

Provenance

Where this comes from

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