asn.dev

Observed topology

AS270585 AS270585 - Fly Conecta Internet LTDA

Unclassified APNIC Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS270585: 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
AS271253LINK BRASIL TELECOMUNICACOES LTDAUnclassifiedIPv4 IPv6585
AS3356Level 3 Parent, LLCTransitIPv4157
AS268624Gamers Club LtdaUnclassifiedIPv4 IPv6157
AS53062GGNET TELECOMUNICACOES LTDAUnclassifiedIPv4 IPv667
AS272193SPnetFibra Provedor Networking LtdaUnclassifiedIPv439
AS274384VELIZ INTERNET E SERVICOS LTDAUnclassifiedIPv4 IPv637
AS1031PEER 1031 LLCUnclassifiedIPv433

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS274384VELIZ INTERNET E SERVICOS LTDAUnclassifiedIPv617

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS271253LINK BRASIL TELECOMUNICACOES LTDAUnclassifiedIPv4 IPv6604
AS3356Level 3 Parent, LLCTransitIPv4157
AS268624Gamers Club LtdaUnclassifiedIPv4 IPv6157
AS53062GGNET TELECOMUNICACOES LTDAUnclassifiedIPv4 IPv667
AS274384VELIZ INTERNET E SERVICOS LTDAUnclassifiedIPv4 IPv656
AS272193SPnetFibra Provedor Networking LtdaUnclassifiedIPv439
AS1031PEER 1031 LLCUnclassifiedIPv433

Provenance

Where this comes from

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