asn.dev

Observed topology

AS267207 AS267207 - RFTecnologia Teleinformatica Ltda-ME

Unclassified APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS267207: 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
AS265937Alianca TecnoinfoLtdaResidentialIPv4 IPv6138
AS16735ALGAR TELECOM S/AUnclassifiedIPv4 IPv660
AS11432Telium Telecomunicacoes LtdaHostingIPv420

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS263491RamalVirtual Telecomunicacoes LtdaUnclassifiedIPv4 IPv6460
AS270319LYTUX SERV EM TELECOM REDES E TREINAMENTOS LTDAUnclassifiedIPv461

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS263491RamalVirtual Telecomunicacoes LtdaUnclassifiedIPv4 IPv6460
AS265937Alianca TecnoinfoLtdaResidentialIPv4 IPv6338
AS16735ALGAR TELECOM S/AUnclassifiedIPv4 IPv6336
AS11432Telium Telecomunicacoes LtdaHostingIPv4 IPv665
AS270319LYTUX SERV EM TELECOM REDES E TREINAMENTOS LTDAUnclassifiedIPv461

Provenance

Where this comes from

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