Observed topology

AS269244 DEAN MURILO GONCALVES OLIVEIRA - ME

Unclassified ARIN

Upstreams 5 carry this network

Downstreams 1 this network carries

Adjacent (IPv4) 5

Adjacent (IPv6) 2

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS269244: 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
AS61832	DB3 SERVICOS DE TELECOMUNICACOES S.A	Unclassified	IPv4	174
AS52974	Henet Telecomunicacoes Ltda	Residential	IPv4	120
AS52999	START NETWORKS S/A	Unclassified	IPv4	43
AS61758	TOP NET SERVICOS LTDA	Residential	IPv4	20
AS28368	SOBRALNET SERVICOS E TELECOMUNICACOES LTDA - ME	Residential	IPv4	6

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS272763	C & O INFORMATICA LTDA - ME	Unclassified	IPv6	231

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS52974	Henet Telecomunicacoes Ltda	Residential	IPv4 IPv6	351
AS272763	C & O INFORMATICA LTDA - ME	Unclassified	IPv6	231
AS61832	DB3 SERVICOS DE TELECOMUNICACOES S.A	Unclassified	IPv4	174
AS52999	START NETWORKS S/A	Unclassified	IPv4	43
AS61758	TOP NET SERVICOS LTDA	Residential	IPv4	20
AS28368	SOBRALNET SERVICOS E TELECOMUNICACOES LTDA - ME	Residential	IPv4	6

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.