Observed topology

AS36290 THECABLE-STKITTS-01 - The Cable of St. Kitts

Unclassified ARIN Cable/DSL/ISP

Upstreams 3 carry this network

Downstreams 2 this network carries

Adjacent (IPv4) 5

Adjacent (IPv6) 0

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS36290: 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
AS63351	Southern Caribbean Fiber	Unclassified	IPv4	352
AS23520	Columbus Networks USA, Inc.	Residential	IPv4	72
AS3549	Level 3 Parent, LLC	Transit	IPv4	32

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS396416	The Government of Saint Kitts and Nevis	Hosting	IPv4	57
AS397382	Eastern Caribbean Central Bank	Unclassified	IPv4	2

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS63351	Southern Caribbean Fiber	Unclassified	IPv4	467
AS396416	The Government of Saint Kitts and Nevis	Hosting	IPv4	115
AS23520	Columbus Networks USA, Inc.	Residential	IPv4	93
AS3549	Level 3 Parent, LLC	Transit	IPv4	45
AS397382	Eastern Caribbean Central Bank	Unclassified	IPv4	2

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.