asn.dev

Observed topology

AS262408 AS262408 - CEPAIN TELECOM

Residential APNIC Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS262408: 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
AS28146MHNET TELECOMResidentialIPv4 IPv6538
AS52680BLZNET SERVICOS DE INTERNET LTDA - MEUnclassifiedIPv4 IPv6109
AS24482SG.GSHostingIPv412
AS35280F5 Networks SARLHostingIPv412
AS37721Virtual Technologies & SolutionsResidentialIPv412

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS268977CEPAIN C2 TELECOMUnclassifiedIPv4195
AS262911BAU E DORL LTDAUnclassifiedIPv4 IPv6106

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS28146MHNET TELECOMResidentialIPv4 IPv6806
AS268977CEPAIN C2 TELECOMUnclassifiedIPv4195
AS52680BLZNET SERVICOS DE INTERNET LTDA - MEUnclassifiedIPv4 IPv6130
AS262911BAU E DORL LTDAUnclassifiedIPv4 IPv6106
AS24482SG.GSHostingIPv416
AS35280F5 Networks SARLHostingIPv416
AS37721Virtual Technologies & SolutionsResidentialIPv416

Provenance

Where this comes from

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