asn.dev

Observed topology

AS262940 Silva & Goncalves Informatica Ltda

Residential LACNIC Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS262940: 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
AS271253LINK BRASIL TELECOMUNICACOES LTDAUnclassifiedIPv4 IPv6228
AS263478DUFIBRANET TELECOM LTDAResidentialIPv4157
AS263444Open X Tecnologia LtdaUnclassifiedIPv4 IPv649
AS1031PEER 1031 LLCUnclassifiedIPv422
AS24482SG.GSHostingIPv4 IPv68

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS269630Jose Carlos Santana Junior-MEUnclassifiedIPv4 IPv649
AS53182lazernet.com.br ltda meUnclassifiedIPv4 IPv647

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS271253LINK BRASIL TELECOMUNICACOES LTDAUnclassifiedIPv4 IPv6228
AS263478DUFIBRANET TELECOM LTDAResidentialIPv4179
AS263444Open X Tecnologia LtdaUnclassifiedIPv4 IPv6123
AS269630Jose Carlos Santana Junior-MEUnclassifiedIPv4 IPv649
AS53182lazernet.com.br ltda meUnclassifiedIPv4 IPv647
AS1031PEER 1031 LLCUnclassifiedIPv422
AS24482SG.GSHostingIPv4 IPv68

Provenance

Where this comes from

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