asn.dev

Observed topology

AS268738 AS268738 - M3 Net Fibra LTDA - ME

Residential LACNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS268738: 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
AS266044Nicnet S.A.UnclassifiedIPv4 IPv6654
AS6939Hurricane Electric LLCTransitIPv4 IPv6208
AS270735COMPUTIZE NETWORK TELECOMUNICACOES LTDAHostingIPv655
AS24482SG.GSHostingIPv4 IPv619
AS10429TELEFONICA BRASIL S.AResidentialIPv412
AS35280F5 Networks SARLHostingIPv62
AS37721Virtual Technologies & SolutionsResidentialIPv62

Transit

Downstream networks

inferred

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

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS266044Nicnet S.A.UnclassifiedIPv4 IPv6654
AS6939Hurricane Electric LLCTransitIPv4 IPv6208
AS270735COMPUTIZE NETWORK TELECOMUNICACOES LTDAHostingIPv655
AS24482SG.GSHostingIPv4 IPv619
AS10429TELEFONICA BRASIL S.AResidentialIPv412
AS35280F5 Networks SARLHostingIPv62
AS37721Virtual Technologies & SolutionsResidentialIPv62

Provenance

Where this comes from

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