asn.dev

Observed topology

AS262567 AS262567 - TELECOM FOZ

Residential LACNIC Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS262567: 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 IPv6586
AS6939Hurricane Electric LLCTransitIPv4 IPv6103
AS14840BR.Digital TelecomUnclassifiedIPv4 IPv642
AS24482SG.GSHostingIPv4 IPv69
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv67

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS266673FLYTEC TELECOM SOCIEDAD ANONIMAUnclassifiedIPv4 IPv6485
AS264631RED PARAGUAYA DE TELECOMUNICACIONES SAUnclassifiedIPv4 IPv6269
AS263404TELECOM FOZUnclassifiedIPv4177

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS3356Level 3 Parent, LLCTransitIPv4 IPv61,082
AS266673FLYTEC TELECOM SOCIEDAD ANONIMAUnclassifiedIPv4 IPv6662
AS14840BR.Digital TelecomUnclassifiedIPv4 IPv6340
AS6939Hurricane Electric LLCTransitIPv4 IPv6320
AS264631RED PARAGUAYA DE TELECOMUNICACIONES SAUnclassifiedIPv4 IPv6269
AS263404TELECOM FOZUnclassifiedIPv4177
AS264409Huge Solucoes Corporativas LtdaUnclassifiedIPv458
AS24482SG.GSHostingIPv4 IPv630
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv621
AS35280F5 Networks SARLHostingIPv44

Provenance

Where this comes from

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