asn.dev

Observed topology

AS28634 Life Tecnologia Ltda.

Residential ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS28634: 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
AS4230CLARO S.A.ResidentialIPv4 IPv6335
AS52468UFINET PANAMA S.A.UnclassifiedIPv489
AS6939Hurricane Electric LLCTransitIPv614
AS24482SG.GSHostingIPv413
AS35280F5 Networks SARLHostingIPv47
AS37721Virtual Technologies & SolutionsResidentialIPv47
AS273478Sage NetworksUnclassifiedIPv4 IPv62

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS266969Shimabukuro & Zanguettin Ltda MEUnclassifiedIPv4 IPv690
AS265273FUNDACAO DE ENS. EURIPIDES SOARES DA ROCHAUnclassifiedIPv442

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS4230CLARO S.A.ResidentialIPv4 IPv6503
AS266969Shimabukuro & Zanguettin Ltda MEUnclassifiedIPv4 IPv6143
AS52468UFINET PANAMA S.A.UnclassifiedIPv489
AS265273FUNDACAO DE ENS. EURIPIDES SOARES DA ROCHAUnclassifiedIPv442
AS6939Hurricane Electric LLCTransitIPv628
AS24482SG.GSHostingIPv416
AS35280F5 Networks SARLHostingIPv47
AS37721Virtual Technologies & SolutionsResidentialIPv47
AS273478Sage NetworksUnclassifiedIPv4 IPv62

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.