asn.dev

Observed topology

AS21734 TRADINGTECH-TTNET

Unclassified ARIN

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

Transit

Upstream networks

All 17

Networks observed carrying traffic for AS21734: 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
AS4637Telstra GlobalUnclassifiedIPv4215
AS6461Zayo BandwidthTransitIPv4177
AS13789Unitas GlobalUnclassifiedIPv4112
AS19024Unitas GlobalHostingIPv4112
AS49915Megaport (UK) LimitedUnclassifiedIPv4112
AS15570PACKETFABRIC (UK) LTDUnclassifiedIPv4110
AS48910PACKETFABRIC (UK) LTDUnclassifiedIPv4110
AS17408AboveNet Communications TaiwanUnclassifiedIPv465
AS3549Level 3 Parent, LLCTransitIPv457
AS4826Vocus Connect International BackboneUnclassifiedIPv453

Transit

Downstream networks

inferred

Networks for which AS21734 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 17

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

ASNetworkTypeFamiliesPaths seen
AS4637Telstra GlobalUnclassifiedIPv4215
AS6461Zayo BandwidthTransitIPv4177
AS13789Unitas GlobalUnclassifiedIPv4112
AS19024Unitas GlobalHostingIPv4112
AS49915Megaport (UK) LimitedUnclassifiedIPv4112
AS15570PACKETFABRIC (UK) LTDUnclassifiedIPv4110
AS48910PACKETFABRIC (UK) LTDUnclassifiedIPv4110
AS17408AboveNet Communications TaiwanUnclassifiedIPv465
AS3549Level 3 Parent, LLCTransitIPv457
AS4826Vocus Connect International BackboneUnclassifiedIPv453

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-21 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.