asn.dev

Observed topology

AS265188 Grupo WCM net

Unclassified LACNIC NSP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS265188: 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
AS1031PEER 1031 LLCUnclassifiedIPv4 IPv6159
AS6939Hurricane Electric LLCTransitIPv4 IPv6158
AS52468UFINET PANAMA S.A.UnclassifiedIPv4 IPv664
AS13786Seabras 1 USA, LLCUnclassifiedIPv410
AS24482SG.GSHostingIPv4 IPv610
AS35280F5 Networks SARLHostingIPv68
AS37721Virtual Technologies & SolutionsResidentialIPv68
AS33891Core-Backbone GmbHHostingIPv4 IPv65
AS3303Swisscom (Schweiz) AGResidentialIPv42

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS268478WebMais InternetUnclassifiedIPv4 IPv6387

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS268478WebMais InternetUnclassifiedIPv4 IPv6387
AS1031PEER 1031 LLCUnclassifiedIPv4 IPv6264
AS265234N-MULTIMIDIA TELECOMUNICACOES LTDA - MEResidentialIPv4227
AS6939Hurricane Electric LLCTransitIPv4 IPv6208
AS52468UFINET PANAMA S.A.UnclassifiedIPv4 IPv6135
AS24482SG.GSHostingIPv4 IPv614
AS13786Seabras 1 USA, LLCUnclassifiedIPv412
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv611
AS35280F5 Networks SARLHostingIPv4 IPv610
AS33891Core-Backbone GmbHHostingIPv4 IPv68

All 11 adjacent →

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.