asn.dev

Observed topology

AS272451 REDE BRASIL TELECOM DE TELECOMUNICACOES EIRELI

Unclassified APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS272451: 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 LLCTransitIPv650
AS61832DB3 SERVICOS DE TELECOMUNICACOES S.AUnclassifiedIPv612
AS265036BMJnet TelecomResidentialIPv64
AS24482SG.GSHostingIPv63
AS35280F5 Networks SARLHostingIPv62
AS37721Virtual Technologies & SolutionsResidentialIPv62

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS271705MEGA VIRTUA SERVICOS DE INTERNET LTDAUnclassifiedIPv460
AS268162Natural Solucoes Internet e Sistemas LtdaUnclassifiedIPv459

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS61832DB3 SERVICOS DE TELECOMUNICACOES S.AUnclassifiedIPv4 IPv671
AS265036BMJnet TelecomResidentialIPv4 IPv662
AS271705MEGA VIRTUA SERVICOS DE INTERNET LTDAUnclassifiedIPv460
AS268162Natural Solucoes Internet e Sistemas LtdaUnclassifiedIPv459
AS6939Hurricane Electric LLCTransitIPv650
AS24482SG.GSHostingIPv63
AS28368SOBRALNET SERVICOS E TELECOMUNICACOES LTDA - MEResidentialIPv42
AS35280F5 Networks SARLHostingIPv62
AS37721Virtual Technologies & SolutionsResidentialIPv62

Provenance

Where this comes from

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