asn.dev

Observed topology

AS10879 UHC - Unitedhealthcare

Hosting ARIN

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

Transit

Upstream networks

All 12

Networks observed carrying traffic for AS10879: 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, LLCTransitIPv44,361
AS701Verizon BusinessResidentialIPv4349
AS7018AT&T Enterprises, LLCResidentialIPv4248
AS9498BHARTI Airtel Ltd.MobileIPv4207
AS15830Equinix (EMEA) Acquisition Enterprises B.V.HostingIPv4120
AS9299Philippine Long Distance Telephone CompanyUnclassifiedIPv499
AS13335Cloudflare, Inc.HostingIPv465
AS64289Macarne.comUnclassifiedIPv447
AS4755TATA Communications formerly VSNL is Leading ISPHostingIPv434
AS22773Cox Communications Inc.ResidentialIPv432

All 12 upstreams →

Transit

Downstream networks

inferred

Networks for which AS10879 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 12

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

ASNetworkTypeFamiliesPaths seen
AS3356Level 3 Parent, LLCTransitIPv44,361
AS701Verizon BusinessResidentialIPv4349
AS7018AT&T Enterprises, LLCResidentialIPv4248
AS9498BHARTI Airtel Ltd.MobileIPv4207
AS15830Equinix (EMEA) Acquisition Enterprises B.V.HostingIPv4120
AS9299Philippine Long Distance Telephone CompanyUnclassifiedIPv499
AS13335Cloudflare, Inc.HostingIPv465
AS64289Macarne.comUnclassifiedIPv447
AS4755TATA Communications formerly VSNL is Leading ISPHostingIPv434
AS22773Cox Communications Inc.ResidentialIPv432

All 12 adjacent →

Provenance

Where this comes from

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