asn.dev

Observed topology

AS265434 DELTA FIBRA

Residential LACNIC

Upstreams 4 carry this network
Downstreams 4 this network carries
Adjacent (IPv4) 8
Adjacent (IPv6) 8
Upstream graph Who carries AS265434, and who carries them, drawn as a map up to the transit-free core. 4 exchanges Where AS265434 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS3356Level 3 Parent, LLCTransitIPv4 IPv6151
AS24482SG.GSHostingIPv4 IPv66
AS37721Virtual-Technologies-Solutions-SAResidentialIPv4 IPv66
AS35280F5 Networks SARLHostingIPv4 IPv65

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS271453NETWORKSUnclassifiedIPv4 IPv6153
AS268314DA SILVA LOPES TELECOMUNICACOESUnclassifiedIPv4 IPv693
AS272662NETWORKS LTDAUnclassifiedIPv633
AS269226CONNECT INFORMATICA E TELECOM LTDA MEUnclassifiedIPv4 IPv611

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS3356Level 3 Parent, LLCTransitIPv4 IPv6485
AS271453NETWORKSUnclassifiedIPv4 IPv6153
AS268314DA SILVA LOPES TELECOMUNICACOESUnclassifiedIPv4 IPv693
AS272662NETWORKS LTDAUnclassifiedIPv4 IPv693
AS24482SG.GSHostingIPv4 IPv615
AS37721Virtual-Technologies-Solutions-SAResidentialIPv4 IPv613
AS269226CONNECT INFORMATICA E TELECOM LTDA MEUnclassifiedIPv4 IPv611
AS35280F5 Networks SARLHostingIPv4 IPv65

Provenance

Where this comes from

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