Observed topology

AS273730 GILMAR F DE ALMEIDA

Unclassified LACNIC

Upstreams 1 carry this network

Downstreams 5 this network carries

Adjacent (IPv4) 6

Adjacent (IPv6) 1

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS273730: 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
AS266583	TELXE DO BRASIL TELECOMUNICACOES LTDA	Residential	IPv4 IPv6	149

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS265270	Nova Solucoes em Tecnologia	Unclassified	IPv4	174
AS271493	SPEED NET PEDRA	Unclassified	IPv4	174
AS275752	INTERLIGPRO TELECOMUNICACOES DO BRASIL LTDA	Unclassified	IPv4	141
AS271161	ALCANTARA SERVICOS DE TELECOMUNICACOES - EIRELI	Unclassified	IPv4	116
AS262754	FLIX FIBRA	Unclassified	IPv4	40

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS266583	TELXE DO BRASIL TELECOMUNICACOES LTDA	Residential	IPv4 IPv6	794
AS265270	Nova Solucoes em Tecnologia	Unclassified	IPv4	174
AS271493	SPEED NET PEDRA	Unclassified	IPv4	174
AS275752	INTERLIGPRO TELECOMUNICACOES DO BRASIL LTDA	Unclassified	IPv4	141
AS271161	ALCANTARA SERVICOS DE TELECOMUNICACOES - EIRELI	Unclassified	IPv4	116
AS262754	FLIX FIBRA	Unclassified	IPv4	40

Provenance

Where this comes from

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