asn.dev

Observed topology

AS268817 AS268817 - Acelera Telecom

Unclassified LACNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS268817: 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
AS6161467 TELECOM LTDAResidentialIPv4 IPv6118
AS53062GGNET TELECOMUNICACOES LTDAUnclassifiedIPv4 IPv6103
AS263966WORLD WIFI TELECOMUNICACOES LTDA - MEResidentialIPv4 IPv692
AS270340NETCOM TELECOMUNICACOES LTDAResidentialIPv4 IPv689
AS269286Marcelo da Silva Brasil MEUnclassifiedIPv4 IPv636
AS268459CLICK & NAVEGUE TELECOMUNICACOES LTDA-MEResidentialIPv41

Transit

Downstream networks

inferred

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

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS6161467 TELECOM LTDAResidentialIPv4 IPv6118
AS53062GGNET TELECOMUNICACOES LTDAUnclassifiedIPv4 IPv6103
AS263966WORLD WIFI TELECOMUNICACOES LTDA - MEResidentialIPv4 IPv692
AS270340NETCOM TELECOMUNICACOES LTDAResidentialIPv4 IPv689
AS269286Marcelo da Silva Brasil MEUnclassifiedIPv4 IPv636
AS268459CLICK & NAVEGUE TELECOMUNICACOES LTDA-MEResidentialIPv41

Provenance

Where this comes from

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