asn.dev

Observed topology

AS273814 AS273814 - Renato silva almeida e cia

Unclassified LACNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS273814: 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 LLCTransitIPv632
AS53180INFORTEL COMUNICACOES LTDAResidentialIPv617
AS263903INFORBARRA TELECOMUnclassifiedIPv616
AS24482SG.GSHostingIPv63
AS35280F5 Networks SARLHostingIPv62
AS37721Virtual Technologies & SolutionsResidentialIPv62

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS268874IT FacilitiesUnclassifiedIPv458
AS269144SILVANET PROVEDOR DE INTERNET LTDAUnclassifiedIPv458

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS263903INFORBARRA TELECOMUnclassifiedIPv4 IPv687
AS268874IT FacilitiesUnclassifiedIPv458
AS269144SILVANET PROVEDOR DE INTERNET LTDAUnclassifiedIPv458
AS53180INFORTEL COMUNICACOES LTDAResidentialIPv4 IPv652
AS6939Hurricane Electric LLCTransitIPv4 IPv641
AS24482SG.GSHostingIPv4 IPv64
AS35280F5 Networks SARLHostingIPv62
AS37721Virtual Technologies & SolutionsResidentialIPv62

Provenance

Where this comes from

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