asn.dev

Observed topology

AS268019 AS268019 - FIBRA PRIME SERVICOS DE TELECOMUNICACOES LTDA

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS268019: 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
AS22381SAMM TECNOLOGIA E TELECOMUNICACOES S.AUnclassifiedIPv4 IPv6189
AS268976Weclix Telecom S/AUnclassifiedIPv4 IPv6147
AS262282MARIA LUCIANA MACHADO E CIA LTDA-MEUnclassifiedIPv461
AS61775AW FibraResidentialIPv4 IPv641
AS16735ALGAR TELECOM S/AUnclassifiedIPv4 IPv636

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS275737GO-NET TELECOM LTDAUnclassifiedIPv4 IPv6155
AS61775AW FibraResidentialIPv4128
AS264214GUAPTEL TELECOM LTDA - MEUnclassifiedIPv4 IPv696

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS268976Weclix Telecom S/AUnclassifiedIPv4 IPv6373
AS22381SAMM TECNOLOGIA E TELECOMUNICACOES S.AUnclassifiedIPv4 IPv6299
AS61775AW FibraResidentialIPv4 IPv6169
AS275737GO-NET TELECOM LTDAUnclassifiedIPv4 IPv6155
AS264214GUAPTEL TELECOM LTDA - MEUnclassifiedIPv4 IPv696
AS16735ALGAR TELECOM S/AUnclassifiedIPv4 IPv679
AS262282MARIA LUCIANA MACHADO E CIA LTDA-MEUnclassifiedIPv461

Provenance

Where this comes from

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