asn.dev

Observed topology

AS270600 BL PROVEDOR DE ACESSO A INTERNET LTDA

Residential APNIC Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS270600: 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
AS6939Hurricane Electric LLCTransitIPv4 IPv6328
AS13786Seabras 1 USA, LLCUnclassifiedIPv4 IPv6243
AS52468UFINET PANAMA S.A.UnclassifiedIPv436
AS24482SG.GSHostingIPv4 IPv68
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv68
AS35280F5 Networks SARLHostingIPv44

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS262301NETMIG TELECOM EIRELIUnclassifiedIPv4 IPv6105
AS263440WAVE UP TELECOM BRASIL LTDA - MEUnclassifiedIPv4 IPv693

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS13786Seabras 1 USA, LLCUnclassifiedIPv4 IPv6355
AS6939Hurricane Electric LLCTransitIPv4 IPv6354
AS262301NETMIG TELECOM EIRELIUnclassifiedIPv4 IPv6105
AS263440WAVE UP TELECOM BRASIL LTDA - MEUnclassifiedIPv4 IPv693
AS52468UFINET PANAMA S.A.UnclassifiedIPv482
AS24482SG.GSHostingIPv4 IPv620
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv69
AS35280F5 Networks SARLHostingIPv44
AS267613ELETRONET S.A.UnclassifiedIPv41

Provenance

Where this comes from

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