Observed topology

AS26395 JOHNSON-CONTROLS - Johnson Controls Inc

Unclassified ARIN

Upstreams 17 carry this network

Downstreams 0 this network carries

Adjacent (IPv4) 17

Adjacent (IPv6) 0

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

Transit

Upstream networks

All 17

Networks observed carrying traffic for AS26395: 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
AS8220	COLT Technology Services Group Limited	Hosting	IPv4	711
AS701	Verizon Business	Residential	IPv4	157
AS702	Verizon Business	Unclassified	IPv4	86
AS15450	Alhambra Systems SA	Unclassified	IPv4	68
AS16735	ALGAR TELECOM S/A	Unclassified	IPv4	60
AS7018	AT&T Enterprises, LLC	Residential	IPv4	59
AS8151	UNINET	Mobile	IPv4	59
AS7303	Telecom Argentina S.A.	Mobile	IPv4	57
AS8903	LYNTIA NETWORKS S.A.	Unclassified	IPv4	54
AS4768	One New Zealand Group Limited	Residential	IPv4	38

All 17 upstreams →

Transit

Downstream networks

inferred

Networks for which AS26395 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 17

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

AS	Network	Type	Families	Paths seen
AS8220	COLT Technology Services Group Limited	Hosting	IPv4	711
AS701	Verizon Business	Residential	IPv4	157
AS702	Verizon Business	Unclassified	IPv4	86
AS15450	Alhambra Systems SA	Unclassified	IPv4	68
AS16735	ALGAR TELECOM S/A	Unclassified	IPv4	60
AS7018	AT&T Enterprises, LLC	Residential	IPv4	59
AS8151	UNINET	Mobile	IPv4	59
AS7303	Telecom Argentina S.A.	Mobile	IPv4	57
AS8903	LYNTIA NETWORKS S.A.	Unclassified	IPv4	54
AS4768	One New Zealand Group Limited	Residential	IPv4	38

All 17 adjacent →

Provenance

Where this comes from

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