asn.dev

Observed topology

AS267197 AS267197 - CAMOA SERVICOS TELECOM LTDA.

Unclassified LACNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS267197: 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
AS265482NET EXPRESS BRASIL LTDA - MEResidentialIPv4 IPv674
AS3356Level 3 Parent, LLCTransitIPv4 IPv673
AS24482SG.GSHostingIPv4 IPv66
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv65
AS35280F5 Networks SARLHostingIPv4 IPv64
AS265310RETIS - REDES, TI E SEGURANCA LTDA - MEUnclassifiedIPv42

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS269407STILLO NET PROVEDOR LTDA MEUnclassifiedIPv4 IPv6124

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS269407STILLO NET PROVEDOR LTDA MEUnclassifiedIPv4 IPv6124
AS3356Level 3 Parent, LLCTransitIPv4 IPv6113
AS265482NET EXPRESS BRASIL LTDA - MEResidentialIPv4 IPv684
AS265310RETIS - REDES, TI E SEGURANCA LTDA - MEUnclassifiedIPv4 IPv635
AS6939Hurricane Electric LLCTransitIPv434
AS24482SG.GSHostingIPv4 IPv69
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv67
AS35280F5 Networks SARLHostingIPv4 IPv66

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.