asn.dev

Observed topology

AS267158 AS267158 - MG NET TELECOMUNICACOES LTDA ME

Residential RIPE Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS267158: 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
AS270735COMPUTIZE NETWORK TELECOMUNICACOES LTDAHostingIPv4 IPv6279
AS52468UFINET PANAMA S.A.UnclassifiedIPv4 IPv675
AS6939Hurricane Electric LLCTransitIPv668
AS24482SG.GSHostingIPv65
AS28202MASTER S/AUnclassifiedIPv43

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS52715SCORPION TELECOMUNICACAO RIBEIRAO PRETO LTDA - MEUnclassifiedIPv4244
AS266603NEXT FIBRAUnclassifiedIPv4166

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS270735COMPUTIZE NETWORK TELECOMUNICACOES LTDAHostingIPv4 IPv6279
AS52468UFINET PANAMA S.A.UnclassifiedIPv4 IPv6275
AS52715SCORPION TELECOMUNICACAO RIBEIRAO PRETO LTDA - MEUnclassifiedIPv4244
AS6939Hurricane Electric LLCTransitIPv4 IPv6199
AS266603NEXT FIBRAUnclassifiedIPv4166
AS273478Sage NetworksUnclassifiedIPv454
AS24482SG.GSHostingIPv4 IPv616
AS35280F5 Networks SARLHostingIPv47
AS37721Virtual Technologies & SolutionsResidentialIPv47
AS28202MASTER S/AUnclassifiedIPv43

Provenance

Where this comes from

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