asn.dev

Observed topology

AS262708 AS262708 - G R Servicos de Comunicacao Multimidia Ltda. ME

Residential LACNIC Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS262708: 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 LLCTransitIPv4181
AS271253LINK BRASIL TELECOMUNICACOES LTDAUnclassifiedIPv4135
AS52863UPX TECNOLOGIA LTDAUnclassifiedIPv451
AS24482SG.GSHostingIPv415
AS37721Virtual Technologies & SolutionsResidentialIPv412
AS35280F5 Networks SARLHostingIPv411
AS1031PEER 1031 LLCUnclassifiedIPv49

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS273503G P Servicos LtdaUnclassifiedIPv666

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv6213
AS271253LINK BRASIL TELECOMUNICACOES LTDAUnclassifiedIPv4 IPv6165
AS273503G P Servicos LtdaUnclassifiedIPv666
AS52863UPX TECNOLOGIA LTDAUnclassifiedIPv451
AS24482SG.GSHostingIPv4 IPv617
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv614
AS35280F5 Networks SARLHostingIPv411
AS1031PEER 1031 LLCUnclassifiedIPv49

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.