asn.dev

Observed topology

AS270344 AS270344 - GA Telecom

Residential RIPE Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS270344: 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
AS267669JKS INTERNET BANDA LARGAResidentialIPv4 IPv6448

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS263320Sansara TelecomUnclassifiedIPv4 IPv6305
AS28138WN INTERNETUnclassifiedIPv460
AS28590Directnet Prestacao de Servicos Ltda.UnclassifiedIPv460
AS265432Opty Internet LtdaUnclassifiedIPv4 IPv658
AS266506PONTO COM PROVEDOR DE INTERNETUnclassifiedIPv4 IPv633
AS275308LANAN10UnclassifiedIPv632
AS270596Rafael Olegario Silva De Lima Servico De ComunicacUnclassifiedIPv618

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS267669JKS INTERNET BANDA LARGAResidentialIPv4 IPv61,033
AS263320Sansara TelecomUnclassifiedIPv4 IPv6305
AS28138WN INTERNETUnclassifiedIPv460
AS28590Directnet Prestacao de Servicos Ltda.UnclassifiedIPv460
AS265432Opty Internet LtdaUnclassifiedIPv4 IPv658
AS266506PONTO COM PROVEDOR DE INTERNETUnclassifiedIPv4 IPv652
AS275308LANAN10UnclassifiedIPv632
AS270596Rafael Olegario Silva De Lima Servico De ComunicacUnclassifiedIPv618

Provenance

Where this comes from

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