asn.dev

Observed topology

AS36734 PAXIO-SFBA

Residential ARIN Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS36734: 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
AS6461Zayo BandwidthTransitIPv4 IPv6328
AS3257GTT Communications Inc.TransitIPv4 IPv6254
AS3491PCCW Global (HK) Ltd.TransitIPv4 IPv6175
AS6939Hurricane Electric LLCTransitIPv490
AS6424EDGOO NETWORKS UNIPESSOAL LDAHostingIPv412
AS24482SG.GSHostingIPv412
AS31713Gateway CommunicationsUnclassifiedIPv42

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS6994FastmetricsUnclassifiedIPv460
AS27528Eikon Therapeutics, Inc.UnclassifiedIPv460
AS398572Monolithic Power Systems,IncUnclassifiedIPv459
AS53641Tomales Bay LAN, LLCUnclassifiedIPv458
AS7235LanMinds, Inc.UnclassifiedIPv456
AS396997Blockstream USA CorporationUnclassifiedIPv427

Adjacency

Adjacent networks

All 14

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

ASNetworkTypeFamiliesPaths seen
AS6461Zayo BandwidthTransitIPv4 IPv6424
AS3257GTT Communications Inc.TransitIPv4 IPv6395
AS3491PCCW Global (HK) Ltd.TransitIPv4 IPv6266
AS6939Hurricane Electric LLCTransitIPv4121
AS6994FastmetricsUnclassifiedIPv471
AS27528Eikon Therapeutics, Inc.UnclassifiedIPv460
AS398572Monolithic Power Systems,IncUnclassifiedIPv459
AS53641Tomales Bay LAN, LLCUnclassifiedIPv458
AS7235LanMinds, Inc.UnclassifiedIPv456
AS46375Sonic Telecom LLCUnclassifiedIPv435

All 14 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.