asn.dev

Observed topology

AS26479 SDC-AS

Residential ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS26479: 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
AS174Cogent Communications, LLCTransitIPv4 IPv6748
AS2914NTT America, Inc.TransitIPv4 IPv6721
AS6939Hurricane Electric LLCTransitIPv4 IPv6311

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS17310Point Broadband Fiber Holding, LLCUnclassifiedIPv4643
AS62798Point Broadband Fiber Holding, LLCUnclassifiedIPv4232
AS10882Clarity Connect IncUnclassifiedIPv458
AS33335Heaviside Hosting LLCUnclassifiedIPv458

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS174Cogent Communications, LLCTransitIPv4 IPv61,251
AS2914NTT America, Inc.TransitIPv4 IPv61,223
AS17310Point Broadband Fiber Holding, LLCUnclassifiedIPv4817
AS6939Hurricane Electric LLCTransitIPv4 IPv6490
AS62798Point Broadband Fiber Holding, LLCUnclassifiedIPv4232
AS10882Clarity Connect IncUnclassifiedIPv458
AS33335Heaviside Hosting LLCUnclassifiedIPv458
AS20115Charter Communications LLCResidentialIPv419

Provenance

Where this comes from

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