asn.dev

Observed topology

AS268321 SM Passos Kayser Sistemas de Comunicacoes ME

Unclassified LACNIC Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS268321: 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
AS267613ELETRONET S.A.UnclassifiedIPv4 IPv6242
AS28283Adylnet TelecomResidentialIPv4 IPv6164
AS28146MHNET TELECOMResidentialIPv486
AS53062GGNET TELECOMUNICACOES LTDAUnclassifiedIPv42

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS269271SERGIO BATISTA CARDOZO MEUnclassifiedIPv4189
AS262727AtualNet Provedor de Internet LtdaResidentialIPv463
AS270283MIX NET INFORMATICA LTDA. MEUnclassifiedIPv462
AS273386RE9SUA INTERNET SERVICOS DE TELECOM LTDAUnclassifiedIPv422
AS270409MARCIO ISAIAS DA SILVA EIRELIUnclassifiedIPv44

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS28283Adylnet TelecomResidentialIPv4 IPv6317
AS267613ELETRONET S.A.UnclassifiedIPv4 IPv6242
AS269271SERGIO BATISTA CARDOZO MEUnclassifiedIPv4189
AS53062GGNET TELECOMUNICACOES LTDAUnclassifiedIPv4186
AS28146MHNET TELECOMResidentialIPv489
AS262727AtualNet Provedor de Internet LtdaResidentialIPv463
AS270283MIX NET INFORMATICA LTDA. MEUnclassifiedIPv462
AS273386RE9SUA INTERNET SERVICOS DE TELECOM LTDAUnclassifiedIPv422
AS270409MARCIO ISAIAS DA SILVA EIRELIUnclassifiedIPv44

Provenance

Where this comes from

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