Observed topology

AS18608 PALADYNE-SYSTEMS-INC

Unclassified ARIN

Upstreams 8 carry this network

Downstreams 0 this network carries

Adjacent (IPv4) 8

Adjacent (IPv6) 0

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS18608: 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
AS13789	Unitas Global	Unclassified	IPv4	116
AS10913	Unitas Global	Hosting	IPv4	110
AS4515	PCCW IMS Ltd (PCCW Business Internet Access)	Unclassified	IPv4	87
AS8220	COLT Technology Services Group Limited	Hosting	IPv4	80
AS174	Cogent Communications, LLC	Transit	IPv4	42
AS10103	HK Broadband Network Ltd.	Residential	IPv4	29
AS2914	NTT America, Inc.	Transit	IPv4	2
AS3257	GTT Communications Inc.	Transit	IPv4	2

Transit

Downstream networks

inferred

Networks for which AS18608 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

observed

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

AS	Network	Type	Families	Paths seen
AS13789	Unitas Global	Unclassified	IPv4	116
AS10913	Unitas Global	Hosting	IPv4	110
AS4515	PCCW IMS Ltd (PCCW Business Internet Access)	Unclassified	IPv4	87
AS8220	COLT Technology Services Group Limited	Hosting	IPv4	80
AS174	Cogent Communications, LLC	Transit	IPv4	42
AS10103	HK Broadband Network Ltd.	Residential	IPv4	29
AS2914	NTT America, Inc.	Transit	IPv4	2
AS3257	GTT Communications Inc.	Transit	IPv4	2

Provenance

Where this comes from

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