asn.dev

Observed topology

AS27775 AS27775 - Telecommunicationcompany Suriname - TeleSur

Residential LACNIC Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS27775: 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
AS5511Orange S.A.TransitIPv4 IPv611,466
AS23520Columbus Networks USA, Inc.ResidentialIPv4 IPv68,830

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS263799CARIBBEAN COMMUNICATION SERVICESHostingIPv4 IPv6202
AS272136SURINAME INTERNET EXCHANGE (SUR-IX)HostingIPv4 IPv6155
AS265822PARBONET N.V.ResidentialIPv4 IPv689
AS14789Cloudflare, Inc.UnclassifiedIPv459
AS210897Teleperformance Netherlands B.VUnclassifiedIPv459

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS5511Orange S.A.TransitIPv4 IPv611,911
AS23520Columbus Networks USA, Inc.ResidentialIPv4 IPv69,039
AS263799CARIBBEAN COMMUNICATION SERVICESHostingIPv4 IPv6266
AS272136SURINAME INTERNET EXCHANGE (SUR-IX)HostingIPv4 IPv6213
AS265822PARBONET N.V.ResidentialIPv4 IPv689
AS14789Cloudflare, Inc.UnclassifiedIPv459
AS210897Teleperformance Netherlands B.VUnclassifiedIPv459
AS13335Cloudflare, Inc.HostingIPv632

Provenance

Where this comes from

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