asn.dev

Observed topology

AS36692 CISCO-UMBRELLA

Hosting RIPE Content

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

Transit

Upstream networks

All 75

Networks observed carrying traffic for AS36692: 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
AS3356Level 3 Parent, LLCTransitIPv4 IPv610,209
AS2914NTT America, Inc.TransitIPv4 IPv67,584
AS6939Hurricane Electric LLCTransitIPv4 IPv65,015
AS3257GTT Communications Inc.TransitIPv4 IPv64,665
AS25605Cisco OpenDNS, LLCHostingIPv4 IPv63,126
AS701Verizon BusinessResidentialIPv41,441
AS1299Arelion Sweden ABTransitIPv4 IPv61,416
AS55836Reliance Jio Infocomm LimitedMobileIPv4 IPv61,145
AS4637Telstra GlobalUnclassifiedIPv4 IPv61,136
AS6453TATA COMMUNICATIONS (AMERICA) INCTransitIPv4 IPv6783

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS25605Cisco OpenDNS, LLCHostingIPv4190
AS13445Cisco Webex LLCHostingIPv479

Adjacency

Adjacent networks

All 76

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

ASNetworkTypeFamiliesPaths seen
AS3356Level 3 Parent, LLCTransitIPv4 IPv613,387
AS2914NTT America, Inc.TransitIPv4 IPv68,169
AS25605Cisco OpenDNS, LLCHostingIPv4 IPv66,858
AS6939Hurricane Electric LLCTransitIPv4 IPv65,015
AS3257GTT Communications Inc.TransitIPv4 IPv64,665
AS701Verizon BusinessResidentialIPv4 IPv61,751
AS1299Arelion Sweden ABTransitIPv4 IPv61,416
AS4637Telstra GlobalUnclassifiedIPv4 IPv61,146
AS55836Reliance Jio Infocomm LimitedMobileIPv4 IPv61,145
AS30607Cisco OpenDNS, LLCUnclassifiedIPv4 IPv61,036

Provenance

Where this comes from

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