Observed topology

AS16789 YARDI - YARDI SYSTEMS, INC

Unclassified ARIN

Upstreams 12 carry this network

Downstreams 0 this network carries

Adjacent (IPv4) 12

Adjacent (IPv6) 0

Upstream graph Who carries AS16789, and who carries them, drawn as a map up to the transit-free core. 0 exchanges Where AS16789 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

All 12

Networks observed carrying traffic for AS16789: 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.

AS	Network	Type	Families	Paths seen
AS6461	Zayo Bandwidth	Transit	IPv4	399
AS3356	Level 3 Parent, LLC	Transit	IPv4	225
AS174	Cogent Communications, LLC	Transit	IPv4	109
AS22773	Cox Communications Inc.	Residential	IPv4	77
AS15802	Emirates Integrated Telecommunications Company PJSC	Unclassified	IPv4	62
AS6939	Hurricane Electric LLC	Transit	IPv4	53
AS2914	NTT America, Inc.	Transit	IPv4	46
AS577	Bell Canada	Mobile	IPv4	43
AS42156	GNX B.V.	Unclassified	IPv4	41
AS5650	Frontier Communications of America, Inc.	Residential	IPv4	40

All 12 upstreams →

Transit

Downstream networks

inferred

Networks for which AS16789 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 AS16789 in a routing path, in either direction.

AS	Network	Type	Families	Paths seen
AS6461	Zayo Bandwidth	Transit	IPv4	399
AS3356	Level 3 Parent, LLC	Transit	IPv4	225
AS174	Cogent Communications, LLC	Transit	IPv4	109
AS22773	Cox Communications Inc.	Residential	IPv4	77
AS15802	Emirates Integrated Telecommunications Company PJSC	Unclassified	IPv4	62
AS6939	Hurricane Electric LLC	Transit	IPv4	53
AS2914	NTT America, Inc.	Transit	IPv4	46
AS577	Bell Canada	Mobile	IPv4	43
AS42156	GNX B.V.	Unclassified	IPv4	41
AS5650	Frontier Communications of America, Inc.	Residential	IPv4	40

All 12 adjacent →

Provenance

Where this comes from

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