asn.dev

Observed topology

AS263457 AS263457 - Alpinet Informatica Ltda

Hosting LACNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS263457: 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
AS52468UFINET PANAMA S.A.UnclassifiedIPv4 IPv6218
AS273747TECH IN SOLUCOES LTDAUnclassifiedIPv4128
AS61637RADIOBRAS TELECOM LTDA MEUnclassifiedIPv461
AS267543DAM Solutions Tecnologia LtdaUnclassifiedIPv461
AS274842MonteNet TelecomunicacoesUnclassifiedIPv459
AS6939Hurricane Electric LLCTransitIPv4 IPv625
AS24482SG.GSHostingIPv4 IPv62
AS53013UFINET BRASIL S.A.HostingIPv41

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS264931Net Galileu Servicos de Telecomunicacao LTDA MEUnclassifiedIPv461

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS52468UFINET PANAMA S.A.UnclassifiedIPv4 IPv6218
AS273747TECH IN SOLUCOES LTDAUnclassifiedIPv4128
AS61637RADIOBRAS TELECOM LTDA MEUnclassifiedIPv461
AS264931Net Galileu Servicos de Telecomunicacao LTDA MEUnclassifiedIPv461
AS267543DAM Solutions Tecnologia LtdaUnclassifiedIPv461
AS28352NETSPEED LTDAResidentialIPv460
AS274842MonteNet TelecomunicacoesUnclassifiedIPv459
AS6939Hurricane Electric LLCTransitIPv4 IPv625
AS24482SG.GSHostingIPv4 IPv62
AS53013UFINET BRASIL S.A.HostingIPv42

Provenance

Where this comes from

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