asn.dev

Observed topology

AS273355 System Computadores LTDA

Residential APNIC Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS273355: 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 LLCTransitIPv666
AS24482SG.GSHostingIPv63
AS61832DB3 SERVICOS DE TELECOMUNICACOES S.AUnclassifiedIPv62
AS265144MCD INFORMATICA E TELECOMUNICACOES LTDA - MEUnclassifiedIPv62
AS35280F5 Networks SARLHostingIPv61
AS37721Virtual Technologies & SolutionsResidentialIPv61

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS28590Directnet Prestacao de Servicos Ltda.UnclassifiedIPv463

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv666
AS28590Directnet Prestacao de Servicos Ltda.UnclassifiedIPv463
AS61832DB3 SERVICOS DE TELECOMUNICACOES S.AUnclassifiedIPv4 IPv629
AS28198SEMPRE TELECOMUNICACOES LTDAResidentialIPv425
AS265144MCD INFORMATICA E TELECOMUNICACOES LTDA - MEUnclassifiedIPv4 IPv612
AS24482SG.GSHostingIPv4 IPv64
AS35280F5 Networks SARLHostingIPv61
AS37721Virtual Technologies & SolutionsResidentialIPv61

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.