asn.dev

Observed topology

AS263574 ETECC FIBRA OPTICA TELECOM LTDA

Residential AFRINIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS263574: 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 IPv6303
AS13786Seabras 1 USA, LLCUnclassifiedIPv4 IPv685
AS24482SG.GSHostingIPv417
AS35280F5 Networks SARLHostingIPv411
AS37721Virtual Technologies & SolutionsResidentialIPv411

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS265059TV CABO SAO PAULO LTDAUnclassifiedIPv4180
AS272252BRANET FIBRAUnclassifiedIPv6128
AS262388Via Rede Sul Servico de Informatica LtdaUnclassifiedIPv4 IPv694

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS3356Level 3 Parent, LLCTransitIPv4 IPv6542
AS13786Seabras 1 USA, LLCUnclassifiedIPv4 IPv6204
AS272252BRANET FIBRAUnclassifiedIPv4 IPv6181
AS265059TV CABO SAO PAULO LTDAUnclassifiedIPv4180
AS262388Via Rede Sul Servico de Informatica LtdaUnclassifiedIPv4 IPv694
AS6939Hurricane Electric LLCTransitIPv687
AS24482SG.GSHostingIPv4 IPv627
AS35280F5 Networks SARLHostingIPv411
AS37721Virtual Technologies & SolutionsResidentialIPv411

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.