asn.dev

Observed topology

AS266101 AS266101 - MARTINS.NET SERVICOS DE TELECOMUNICACOES LTDA

Residential LACNIC Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS266101: 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
AS271253LINK BRASIL TELECOMUNICACOES LTDAUnclassifiedIPv4 IPv6229
AS270706LAN TELECOM INTERNET BANDA LARGA LTDAResidentialIPv4108
AS274839A SANTOS SERVICOS DE TELECOMUNICACAO EIRELIUnclassifiedIPv4 IPv6104
AS1031PEER 1031 LLCUnclassifiedIPv416

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS270706LAN TELECOM INTERNET BANDA LARGA LTDAResidentialIPv4345
AS274839A SANTOS SERVICOS DE TELECOMUNICACAO EIRELIUnclassifiedIPv63

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS271253LINK BRASIL TELECOMUNICACOES LTDAUnclassifiedIPv4 IPv6663
AS270706LAN TELECOM INTERNET BANDA LARGA LTDAResidentialIPv4513
AS274839A SANTOS SERVICOS DE TELECOMUNICACAO EIRELIUnclassifiedIPv4 IPv6277
AS61832DB3 SERVICOS DE TELECOMUNICACOES S.AUnclassifiedIPv4 IPv693
AS1031PEER 1031 LLCUnclassifiedIPv467

Provenance

Where this comes from

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