asn.dev

Observed topology

AS27887 WIND Telecom S.A.

Unclassified APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS27887: 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
AS174Cogent Communications, LLCTransitIPv4 IPv61,283
AS12956TELEFONICA GLOBAL SOLUTIONS SLTransitIPv4815
AS32270LD Telecommunications, Inc.HostingIPv4 IPv6209
AS3303Swisscom (Schweiz) AGResidentialIPv423
AS24482SG.GSHostingIPv423
AS6939Hurricane Electric LLCTransitIPv61

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS262178Pontificia Universidad Catolica Madre y Maestra (PUCMM)UnclassifiedIPv4 IPv6165
AS266709Oficina Presidencial de la Tecnologias de Informacion y ComunicacionUnclassifiedIPv44
AS262931Servicios De Ti Dominicana Sc,SasUnclassifiedIPv43

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS174Cogent Communications, LLCTransitIPv4 IPv61,434
AS12956TELEFONICA GLOBAL SOLUTIONS SLTransitIPv4815
AS32270LD Telecommunications, Inc.HostingIPv4 IPv6209
AS262178Pontificia Universidad Catolica Madre y Maestra (PUCMM)UnclassifiedIPv4 IPv6165
AS24482SG.GSHostingIPv435
AS3303Swisscom (Schweiz) AGResidentialIPv432
AS266709Oficina Presidencial de la Tecnologias de Informacion y ComunicacionUnclassifiedIPv44
AS262931Servicios De Ti Dominicana Sc,SasUnclassifiedIPv43
AS6939Hurricane Electric LLCTransitIPv61

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.