asn.dev

Observed topology

AS270639 EGTECH SOLUCOES EM TELECOMUNICACOES

Unclassified LACNIC Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS270639: 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
AS266931RE Servicos de Comunicacao MultimidiaUnclassifiedIPv4 IPv660
AS6939Hurricane Electric LLCTransitIPv4 IPv628
AS24482SG.GSHostingIPv4 IPv62
AS52468UFINET PANAMA S.A.UnclassifiedIPv4 IPv62
AS37721Virtual Technologies & SolutionsResidentialIPv61

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS271359SS FIBER TELECOM EIRELIUnclassifiedIPv4 IPv692

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS262342WZNET TELECOM LTDAUnclassifiedIPv4 IPv692
AS271359SS FIBER TELECOM EIRELIUnclassifiedIPv4 IPv692
AS266931RE Servicos de Comunicacao MultimidiaUnclassifiedIPv4 IPv660
AS6939Hurricane Electric LLCTransitIPv4 IPv628
AS24482SG.GSHostingIPv4 IPv62
AS52468UFINET PANAMA S.A.UnclassifiedIPv4 IPv62
AS37721Virtual Technologies & SolutionsResidentialIPv61

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-29 10:00 UTC by route-views2,rrc00, as seen from 76 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.