asn.dev

Observed topology

AS5639 Telecommunication Services of Trinidad and Tobago

Residential APNIC

Upstreams 2 carry this network
Downstreams 3 this network carries
Adjacent (IPv4) 5
Adjacent (IPv6) 3
Upstream graph Who carries AS5639, and who carries them, drawn as a map up to the transit-free core. 1 exchange Where AS5639 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS5639: 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
AS23520Columbus Networks USA, Inc.ResidentialIPv4 IPv66,030
AS174Cogent Communications, LLCTransitIPv4 IPv62,298

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS27924AMPLIA COMMUNICATIONS LTD.ResidentialIPv4 IPv61,021
AS28067The University of the West IndiesSt Augustine CampUnclassifiedIPv4232
AS26317Lisa Communications LtdUnclassifiedIPv492

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS23520Columbus Networks USA, Inc.ResidentialIPv4 IPv67,331
AS174Cogent Communications, LLCTransitIPv4 IPv62,348
AS27924AMPLIA COMMUNICATIONS LTD.ResidentialIPv4 IPv61,027
AS28067The University of the West IndiesSt Augustine CampUnclassifiedIPv4232
AS26317Lisa Communications LtdUnclassifiedIPv492

Provenance

Where this comes from

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