asn.dev

Observed topology

AS263471 Intervel Informatica Ltda

Unclassified LACNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS263471: 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 LLCTransitIPv4 IPv6177
AS28260ALTA REDE CORPORATE NETWORK TELECOM LTDA - EPPUnclassifiedIPv4 IPv6109
AS24482SG.GSHostingIPv4 IPv613
AS35280F5 Networks SARLHostingIPv4 IPv610
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv610
AS28204Keraxweb Servicos de Int. e Internet LtdaUnclassifiedIPv4 IPv63

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS267286CONECT INTERNET PROVIDER LTDAUnclassifiedIPv4 IPv6125
AS28204Keraxweb Servicos de Int. e Internet LtdaUnclassifiedIPv455

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS28260ALTA REDE CORPORATE NETWORK TELECOM LTDA - EPPUnclassifiedIPv4 IPv6222
AS6939Hurricane Electric LLCTransitIPv4 IPv6203
AS267286CONECT INTERNET PROVIDER LTDAUnclassifiedIPv4 IPv6125
AS28204Keraxweb Servicos de Int. e Internet LtdaUnclassifiedIPv4 IPv693
AS24482SG.GSHostingIPv4 IPv615
AS35280F5 Networks SARLHostingIPv4 IPv612
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv612

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.