asn.dev

Observed topology

AS271608 plus internet telecom

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS271608: 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
AS273431ANIL LINK TELECOMUNICACOES LTDAUnclassifiedIPv4 IPv693
AS269194ST1 INTERNETResidentialIPv4 IPv676
AS262462Aranet PlayUnclassifiedIPv460
AS265269MEGA TELE INFORMATICAUnclassifiedIPv4 IPv650
AS263362REDE SPEEDNET TELECOM LTDAResidentialIPv4 IPv644
AS269530ACCESSNET TELECOMUNICACOES EIRELIResidentialIPv4 IPv619

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS265500ALMEIRIM TELECOM LTDA - MEUnclassifiedIPv4238
AS267023B. DOS S. VIEIRA NETO LTDAUnclassifiedIPv4180
AS266584Conect- Provedor de Internet Ltda EPPUnclassifiedIPv474

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS262462Aranet PlayUnclassifiedIPv4552
AS265500ALMEIRIM TELECOM LTDA - MEUnclassifiedIPv4238
AS267023B. DOS S. VIEIRA NETO LTDAUnclassifiedIPv4180
AS273431ANIL LINK TELECOMUNICACOES LTDAUnclassifiedIPv4 IPv693
AS269194ST1 INTERNETResidentialIPv4 IPv676
AS266584Conect- Provedor de Internet Ltda EPPUnclassifiedIPv474
AS265269MEGA TELE INFORMATICAUnclassifiedIPv4 IPv650
AS263362REDE SPEEDNET TELECOM LTDAResidentialIPv4 IPv644
AS269530ACCESSNET TELECOMUNICACOES EIRELIResidentialIPv4 IPv619

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.