Observed topology

AS273624 SOUSA & RAMOS PRESTADORA DE SERVICOS LTDA

Unclassified LACNIC

Upstreams 4 carry this network

Downstreams 3 this network carries

Adjacent (IPv4) 7

Adjacent (IPv6) 3

Upstream graph Who carries AS273624, and who carries them, drawn as a map up to the transit-free core. 0 exchanges Where AS273624 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS273624: 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.

AS	Network	Type	Families	Paths seen
AS263558	RD TELECOM LTDA -ME	Residential	IPv4 IPv6	164
AS270724	CLIENT.CO SERVICOS E TELECOMUNICACOES LTDA	Unclassified	IPv4 IPv6	37
AS16735	ALGAR TELECOM S/A	Unclassified	IPv4 IPv6	11
AS266167	CELERIX TECNOLOGIA DE TELECOMUNICACOES LTDA	Unclassified	IPv4	1

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS263627	Wnetsistem Comercio e Servicos de Informatica Ltda	Unclassified	IPv4	275
AS268506	LEON TELECOM LTDA	Unclassified	IPv4	21
AS271019	GIGA NET INFORMATICA LTDA	Unclassified	IPv4	16

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS263558	RD TELECOM LTDA -ME	Residential	IPv4 IPv6	429
AS263627	Wnetsistem Comercio e Servicos de Informatica Ltda	Unclassified	IPv4	275
AS266167	CELERIX TECNOLOGIA DE TELECOMUNICACOES LTDA	Unclassified	IPv4	48
AS270724	CLIENT.CO SERVICOS E TELECOMUNICACOES LTDA	Unclassified	IPv4 IPv6	37
AS268506	LEON TELECOM LTDA	Unclassified	IPv4	21
AS271019	GIGA NET INFORMATICA LTDA	Unclassified	IPv4	16
AS16735	ALGAR TELECOM S/A	Unclassified	IPv4 IPv6	11

Provenance

Where this comes from

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