asn.dev

Observed topology

AS262973 Max Telecomunicacoes Ltda

Unclassified LACNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS262973: 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
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv4 IPv6409
AS263482Megalink Servicos LtdaResidentialIPv4 IPv6175
AS53180INFORTEL COMUNICACOES LTDAResidentialIPv4 IPv638
AS24482SG.GSHostingIPv4 IPv615
AS35280F5 Networks SARLHostingIPv413
AS37721Virtual Technologies & SolutionsResidentialIPv413

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS270791DNBA INTERNET FIBRA & SERVICOS LIMITADAUnclassifiedIPv4 IPv6254
AS273511Saldanha.Net TelecomUnclassifiedIPv4 IPv6160

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv4 IPv6673
AS263482Megalink Servicos LtdaResidentialIPv4 IPv6301
AS270791DNBA INTERNET FIBRA & SERVICOS LIMITADAUnclassifiedIPv4 IPv6254
AS273511Saldanha.Net TelecomUnclassifiedIPv4 IPv6160
AS53180INFORTEL COMUNICACOES LTDAResidentialIPv4 IPv662
AS24482SG.GSHostingIPv4 IPv615
AS35280F5 Networks SARLHostingIPv413
AS37721Virtual Technologies & SolutionsResidentialIPv413

Provenance

Where this comes from

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