Observed topology

AS269307 LIVENET SERVICOS DE COMUNICACAO MULTMIDIA LTDA ME

Unclassified LACNIC Cable/DSL/ISP

Upstreams 3 carry this network

Downstreams 2 this network carries

Adjacent (IPv4) 5

Adjacent (IPv6) 4

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS269307: 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
AS3356	Level 3 Parent, LLC	Transit	IPv4 IPv6	141
AS6939	Hurricane Electric LLC	Transit	IPv4 IPv6	124
AS265061	MIRIANE ARAUJO LIMA DE OLIVEIRA - ME	Unclassified	IPv4 IPv6	45

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS271092	WORLDNET SERVICOS DE TELECOMUNICACAO LTDA	Unclassified	IPv4 IPv6	219
AS269280	INARA SILVA COSTA MOREIRA SERVICOS DE MULTIMIDIA	Unclassified	IPv4	91

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS3356	Level 3 Parent, LLC	Transit	IPv4 IPv6	286
AS271092	WORLDNET SERVICOS DE TELECOMUNICACAO LTDA	Unclassified	IPv4 IPv6	219
AS6939	Hurricane Electric LLC	Transit	IPv4 IPv6	176
AS265061	MIRIANE ARAUJO LIMA DE OLIVEIRA - ME	Unclassified	IPv4 IPv6	158
AS269280	INARA SILVA COSTA MOREIRA SERVICOS DE MULTIMIDIA	Unclassified	IPv4	91

Provenance

Where this comes from

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