asn.dev

Observed topology

AS714 APPLE-ENGINEERING

Hosting ARIN

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

Transit

Upstream networks

All 85

Networks observed carrying traffic for AS714: 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,842
AS6939Hurricane Electric LLCTransitIPv4 IPv68,102
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv66,187
AS1299Arelion Sweden ABTransitIPv4 IPv65,811
AS9498BHARTI Airtel Ltd.MobileIPv4 IPv64,027
AS577Bell CanadaMobileIPv4 IPv63,400
AS9002RETN LimitedUnclassifiedIPv4 IPv63,269
AS7018AT&T Enterprises, LLCResidentialIPv4 IPv63,140
AS22652Videotron LteeResidentialIPv4 IPv63,084
AS2914NTT America, Inc.TransitIPv42,662

All 85 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS6185Apple Inc.HostingIPv4 IPv64,710
AS4755TATA Communications formerly VSNL is Leading ISPHostingIPv48

Adjacency

Adjacent networks

All 90

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

ASNetworkTypeFamiliesPaths seen
AS3356Level 3 Parent, LLCTransitIPv4 IPv611,615
AS6939Hurricane Electric LLCTransitIPv4 IPv68,751
AS1299Arelion Sweden ABTransitIPv4 IPv66,375
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv66,310
AS6185Apple Inc.HostingIPv4 IPv64,710
AS9498BHARTI Airtel Ltd.MobileIPv4 IPv64,134
AS577Bell CanadaMobileIPv4 IPv63,484
AS9002RETN LimitedUnclassifiedIPv4 IPv63,389
AS7018AT&T Enterprises, LLCResidentialIPv4 IPv63,223
AS22652Videotron LteeResidentialIPv4 IPv63,158

All 90 adjacent →

Provenance

Where this comes from

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