asn.dev

Observed topology

AS263309 LaraNet Telecomunicacoes e Servicos EIRALI

Unclassified LACNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS263309: 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
AS28598DB3 SERVICOS DE TELECOMUNICACOES S.AResidentialIPv460
AS269558B S V TELECOMUNICACOES E SERVICOS LTDAResidentialIPv458
AS271746GPONNET FIBRA OPTICA EIRELIUnclassifiedIPv457
AS269194ST1 INTERNETResidentialIPv450
AS6939Hurricane Electric LLCTransitIPv49
AS24482SG.GSHostingIPv41

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS1Level 3 Parent, LLCUnclassifiedIPv460

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS1Level 3 Parent, LLCUnclassifiedIPv460
AS28598DB3 SERVICOS DE TELECOMUNICACOES S.AResidentialIPv460
AS53173Sobral Telecomunicacoes LtdaResidentialIPv460
AS269558B S V TELECOMUNICACOES E SERVICOS LTDAResidentialIPv458
AS271746GPONNET FIBRA OPTICA EIRELIUnclassifiedIPv457
AS269194ST1 INTERNETResidentialIPv450
AS6939Hurricane Electric LLCTransitIPv49
AS24482SG.GSHostingIPv41

Provenance

Where this comes from

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