asn.dev

Observed topology

AS267378 AS267378 - CWMC TELECOM LTDA ME

Unclassified ARIN Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS267378: 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
AS52468UFINET PANAMA S.A.UnclassifiedIPv4 IPv6670
AS6939Hurricane Electric LLCTransitIPv6269
AS24482SG.GSHostingIPv623
AS35280F5 Networks SARLHostingIPv614
AS37721Virtual Technologies & SolutionsResidentialIPv614

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS269348REDES METROUnclassifiedIPv4 IPv6350
AS269496SaturnoTech FibraUnclassifiedIPv4 IPv6110
AS272159Beatriz Falcao de Souza MEUnclassifiedIPv619

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS52468UFINET PANAMA S.A.UnclassifiedIPv4 IPv61,117
AS269348REDES METROUnclassifiedIPv4 IPv6350
AS6939Hurricane Electric LLCTransitIPv6301
AS269496SaturnoTech FibraUnclassifiedIPv4 IPv6110
AS24482SG.GSHostingIPv4 IPv626
AS272159Beatriz Falcao de Souza MEUnclassifiedIPv4 IPv626
AS35280F5 Networks SARLHostingIPv616
AS37721Virtual Technologies & SolutionsResidentialIPv616

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.