asn.dev

Observed topology

AS262765 Net Facil Sistemas Eletronicos Ltda ME

Unclassified APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS262765: 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
AS16735ALGAR TELECOM S/AUnclassifiedIPv4 IPv63,217
AS2914NTT America, Inc.TransitIPv4 IPv6304
AS24482SG.GSHostingIPv4 IPv638
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv638
AS22381SAMM TECNOLOGIA E TELECOMUNICACOES S.AUnclassifiedIPv4 IPv620
AS35280F5 Networks SARLHostingIPv412

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS262797PROVALE SCM LTDAUnclassifiedIPv4 IPv62,794
AS263568Guardian Brasil Vidros Planos Ltda.UnclassifiedIPv4177
AS262515FUNDACAO JOAO PAULO IIUnclassifiedIPv483

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS16735ALGAR TELECOM S/AUnclassifiedIPv4 IPv64,353
AS262797PROVALE SCM LTDAUnclassifiedIPv4 IPv62,794
AS2914NTT America, Inc.TransitIPv4 IPv62,111
AS263568Guardian Brasil Vidros Planos Ltda.UnclassifiedIPv4177
AS24482SG.GSHostingIPv4 IPv694
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv693
AS262515FUNDACAO JOAO PAULO IIUnclassifiedIPv483
AS22381SAMM TECNOLOGIA E TELECOMUNICACOES S.AUnclassifiedIPv4 IPv620
AS35280F5 Networks SARLHostingIPv412

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.