asn.dev

Observed topology

AS267219 Netware Telecomunicacoes e Informatica EIRELI

Residential LACNIC Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS267219: 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
AS61588DIGITAL PROVEDOR DE ACESSO A INTERNET LTDAResidentialIPv4 IPv6237
AS16735ALGAR TELECOM S/AUnclassifiedIPv4 IPv693
AS61622VIA MS SOLUCOES DIGITAISUnclassifiedIPv4 IPv619

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS269261NETMAXXI TELECOMUNICACOES E INFORMATICA LTDA EPPUnclassifiedIPv4 IPv6583

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS269261NETMAXXI TELECOMUNICACOES E INFORMATICA LTDA EPPUnclassifiedIPv4 IPv6583
AS61588DIGITAL PROVEDOR DE ACESSO A INTERNET LTDAResidentialIPv4 IPv6552
AS61622VIA MS SOLUCOES DIGITAISUnclassifiedIPv4 IPv6287
AS16735ALGAR TELECOM S/AUnclassifiedIPv4 IPv693

Provenance

Where this comes from

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