asn.dev

Observed topology

AS268897 AS268897 - SUPRI NET SERVICOS E COMERCIO LTDA - ME

Unclassified LACNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS268897: 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
AS265038TELFO SERVICO DE TELECOMUNICACOES LTDAResidentialIPv4 IPv6184
AS28126BRISANET SERVICOS DE TELECOMUNICACOES S.AResidentialIPv4 IPv694
AS268196LINKNET SOLUCOES EM TELECOMUNICACOES LTDAUnclassifiedIPv4 IPv692
AS6939Hurricane Electric LLCTransitIPv664
AS28598DB3 SERVICOS DE TELECOMUNICACOES S.AResidentialIPv4 IPv660

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS270317SUPRIFIBRA SOLUCOES TECNOLOGICA LTDAUnclassifiedIPv4 IPv6143
AS271308FRANCISCO EDSON LIMA BRASILEIROUnclassifiedIPv4 IPv692

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS265038TELFO SERVICO DE TELECOMUNICACOES LTDAResidentialIPv4 IPv6303
AS28598DB3 SERVICOS DE TELECOMUNICACOES S.AResidentialIPv4 IPv6179
AS270317SUPRIFIBRA SOLUCOES TECNOLOGICA LTDAUnclassifiedIPv4 IPv6143
AS28126BRISANET SERVICOS DE TELECOMUNICACOES S.AResidentialIPv4 IPv697
AS268196LINKNET SOLUCOES EM TELECOMUNICACOES LTDAUnclassifiedIPv4 IPv692
AS271308FRANCISCO EDSON LIMA BRASILEIROUnclassifiedIPv4 IPv692
AS6939Hurricane Electric LLCTransitIPv664

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.