asn.dev

Observed topology

AS262668 AS262668 - Mar Provedor de Internet Ltda

Unclassified LACNIC Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS262668: 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
AS6939Hurricane Electric LLCTransitIPv4 IPv6344
AS52871TASCOM TELECOMUNICACOES LTDAResidentialIPv4 IPv6232
AS52873Softdados TelecomunicacoesUnclassifiedIPv4232
AS52720WEBFOCO TELECOMUNICACOES LTDAUnclassifiedIPv426

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS263291SAVNET TELECOMUNICACOES LTDAUnclassifiedIPv4 IPv6446
AS52717Teleuno Provedor LtdaUnclassifiedIPv4318
AS267476TT Peixoto Provedor de Internet LTDA MEUnclassifiedIPv433

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS52871TASCOM TELECOMUNICACOES LTDAResidentialIPv4 IPv6668
AS6939Hurricane Electric LLCTransitIPv4 IPv6478
AS263291SAVNET TELECOMUNICACOES LTDAUnclassifiedIPv4 IPv6446
AS52873Softdados TelecomunicacoesUnclassifiedIPv4348
AS52717Teleuno Provedor LtdaUnclassifiedIPv4318
AS52720WEBFOCO TELECOMUNICACOES LTDAUnclassifiedIPv4137
AS267476TT Peixoto Provedor de Internet LTDA MEUnclassifiedIPv433

Provenance

Where this comes from

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