asn.dev

Observed topology

AS268080 AS268080 - JMA PROVEDOR DE INTERNET LTDA - ME

Unclassified ARIN

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

Transit

Upstream networks

All 11

Networks observed carrying traffic for AS268080: 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 LLCTransitIPv4 IPv694
AS14840BR.Digital TelecomUnclassifiedIPv4 IPv689
AS268696Tuddo Telecom Ltda.UnclassifiedIPv4 IPv682
AS273639UTRA NETUnclassifiedIPv453
AS267613ELETRONET S.A.UnclassifiedIPv648
AS262725RG SILVEIRA LTDAResidentialIPv412
AS266550WTD TELECOMUnclassifiedIPv48
AS24482SG.GSHostingIPv4 IPv66
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv66
AS61832DB3 SERVICOS DE TELECOMUNICACOES S.AUnclassifiedIPv43

All 11 upstreams →

Transit

Downstream networks

inferred

Networks for which AS268080 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

All 11

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv694
AS14840BR.Digital TelecomUnclassifiedIPv4 IPv689
AS268696Tuddo Telecom Ltda.UnclassifiedIPv4 IPv682
AS273639UTRA NETUnclassifiedIPv453
AS267613ELETRONET S.A.UnclassifiedIPv648
AS262725RG SILVEIRA LTDAResidentialIPv412
AS266550WTD TELECOMUnclassifiedIPv48
AS24482SG.GSHostingIPv4 IPv66
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv66
AS61832DB3 SERVICOS DE TELECOMUNICACOES S.AUnclassifiedIPv43

All 11 adjacent →

Provenance

Where this comes from

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