asn.dev

Observed topology

AS22764 FLUOR-CORP

Unclassified ARIN

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

Transit

Upstream networks

All 19

Networks observed carrying traffic for AS22764: 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, LLCTransitIPv4491
AS15830Equinix (EMEA) Acquisition Enterprises B.V.HostingIPv4173
AS174Cogent Communications, LLCTransitIPv4127
AS12025Iron Mountain Data CenterUnclassifiedIPv490
AS7474SingTel Optus Pty LtdUnclassifiedIPv451
AS55410Vodafone Idea LtdMobileIPv451
AS3549Level 3 Parent, LLCTransitIPv448
AS37100SEACOM LimitedUnclassifiedIPv447
AS9299Philippine Long Distance Telephone CompanyUnclassifiedIPv446
AS852TELUS Communications Inc.ResidentialIPv434

Transit

Downstream networks

inferred

Networks for which AS22764 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 19

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

ASNetworkTypeFamiliesPaths seen
AS3356Level 3 Parent, LLCTransitIPv4491
AS15830Equinix (EMEA) Acquisition Enterprises B.V.HostingIPv4173
AS174Cogent Communications, LLCTransitIPv4127
AS12025Iron Mountain Data CenterUnclassifiedIPv490
AS7474SingTel Optus Pty LtdUnclassifiedIPv451
AS55410Vodafone Idea LtdMobileIPv451
AS3549Level 3 Parent, LLCTransitIPv448
AS37100SEACOM LimitedUnclassifiedIPv447
AS9299Philippine Long Distance Telephone CompanyUnclassifiedIPv446
AS852TELUS Communications Inc.ResidentialIPv434

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.