asn.dev

Observed topology

AS272161 RED FIBRA TELECOMUNICACAES LTDA

Unclassified APNIC Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS272161: 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 LLCTransitIPv6113
AS1031PEER 1031 LLCUnclassifiedIPv631
AS52468UFINET PANAMA S.A.UnclassifiedIPv621
AS272719ICONTECH FIBER SERVICOS DE INTERNET LTDAResidentialIPv618
AS24482SG.GSHostingIPv67
AS35280F5 Networks SARLHostingIPv64

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS269283Ismael Leonardo da SilvaUnclassifiedIPv463
AS269654J&J Net Telecomunicacoes LTDAUnclassifiedIPv463

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv6113
AS272719ICONTECH FIBER SERVICOS DE INTERNET LTDAResidentialIPv4 IPv6110
AS52468UFINET PANAMA S.A.UnclassifiedIPv4 IPv6108
AS269283Ismael Leonardo da SilvaUnclassifiedIPv463
AS269654J&J Net Telecomunicacoes LTDAUnclassifiedIPv463
AS1031PEER 1031 LLCUnclassifiedIPv4 IPv635
AS24482SG.GSHostingIPv4 IPv68
AS35280F5 Networks SARLHostingIPv64
AS3303Swisscom (Schweiz) AGResidentialIPv41
AS33891Core-Backbone GmbHHostingIPv41

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.