asn.dev

Observed topology

AS23074 PETROLEO BRASILEIRO S.A. - PETROBRAS

Unclassified LACNIC Enterprise

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS23074: 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
AS61610ELEA DATA CENTERSUnclassifiedIPv4474
AS8757NSFOCUS, Inc.UnclassifiedIPv4 IPv6387
AS3356Level 3 Parent, LLCTransitIPv4 IPv6310
AS52468UFINET PANAMA S.A.UnclassifiedIPv4 IPv6277
AS6939Hurricane Electric LLCTransitIPv4 IPv6193
AS24482SG.GSHostingIPv4 IPv620
AS37721Virtual Technologies & SolutionsResidentialIPv45

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS61721PETROLEO BRASILEIRO S.A. - PETROBRASUnclassifiedIPv4 IPv693

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS61610ELEA DATA CENTERSUnclassifiedIPv4 IPv6508
AS8757NSFOCUS, Inc.UnclassifiedIPv4 IPv6387
AS3356Level 3 Parent, LLCTransitIPv4 IPv6310
AS52468UFINET PANAMA S.A.UnclassifiedIPv4 IPv6306
AS6939Hurricane Electric LLCTransitIPv4 IPv6220
AS61721PETROLEO BRASILEIRO S.A. - PETROBRASUnclassifiedIPv4 IPv693
AS24482SG.GSHostingIPv4 IPv622
AS37721Virtual Technologies & SolutionsResidentialIPv45
AS22381SAMM TECNOLOGIA E TELECOMUNICACOES S.AUnclassifiedIPv61

Provenance

Where this comes from

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