asn.dev

Observed topology

AS269420 AS269420 - IST INFORMATICA E TELECOMUNICAO 991DF EIRELI - ME

Unclassified LACNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS269420: 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 IPv6189
AS269182PLUGAR TELECOMUnclassifiedIPv4 IPv630

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS271277JS CERQUEIRAUnclassifiedIPv4 IPv6206
AS266565STAR LINE TELECOMUNICACOES LTDAResidentialIPv41

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS265482NET EXPRESS BRASIL LTDA - MEResidentialIPv4 IPv6424
AS271277JS CERQUEIRAUnclassifiedIPv4 IPv6206
AS269182PLUGAR TELECOMUnclassifiedIPv4 IPv634
AS275641EDGE TELECOM LTDAUnclassifiedIPv419
AS61621Norte.Net Telecomunicacoes LtdaUnclassifiedIPv413
AS266565STAR LINE TELECOMUNICACOES LTDAResidentialIPv41

Provenance

Where this comes from

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