Observed topology

AS265448 AS265448 - NETWORK INFORMATICA LTDA. - ME

Unclassified ARIN

Upstreams 2 carry this network

Downstreams 1 this network carries

Adjacent (IPv4) 5

Adjacent (IPv6) 2

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS265448: 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
AS28201	Companhia Itabirana Telecomunicacoes Ltda	Residential	IPv4 IPv6	219
AS264127	EMITEL - Empresa de Informatica e Telecom. LTDA	Residential	IPv4 IPv6	158

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS263420	ACX TELECOM LTDA.	Unclassified	IPv4	200

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS28201	Companhia Itabirana Telecomunicacoes Ltda	Residential	IPv4 IPv6	322
AS263420	ACX TELECOM LTDA.	Unclassified	IPv4	200
AS264127	EMITEL - Empresa de Informatica e Telecom. LTDA	Residential	IPv4 IPv6	158
AS52741	MC Telecom	Unclassified	IPv4	64
AS263099	STIW Sistema de Telecom. Inf e Wireless LTDA	Residential	IPv4	33

Provenance

Where this comes from

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