asn.dev

Observed topology

AS272163 LBC CAVALCANTE PARAISO FIBRA LTDA

Residential LACNIC Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS272163: 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 LLCTransitIPv664
AS268890ASTERNET SERVICOS DE COMUNICACAO MULTIMIDIA LTDAUnclassifiedIPv656
AS52468UFINET PANAMA S.A.UnclassifiedIPv634
AS24482SG.GSHostingIPv64

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS271335GATEWAY ENTERPRISE CORPORATION LTDA MEUnclassifiedIPv460

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS268890ASTERNET SERVICOS DE COMUNICACAO MULTIMIDIA LTDAUnclassifiedIPv4 IPv6103
AS6939Hurricane Electric LLCTransitIPv4 IPv674
AS271335GATEWAY ENTERPRISE CORPORATION LTDA MEUnclassifiedIPv460
AS52468UFINET PANAMA S.A.UnclassifiedIPv4 IPv636
AS24482SG.GSHostingIPv4 IPv65

Provenance

Where this comes from

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