Determinate Systems, Inc. | Status

Updates

• Jun 1, 2026 2:22 PM UTC

  Since roughly 6:30 PM UTC on 30 May 2026, the artifact caching error has been fixed.

  Resolved
• May 30, 2026 6:54 PM UTC (1 day, 19 hours, and 28 minutes earlier)

  Since roughly 2:00 AM UTC on 29 May 2026 up until roughly 6:30 PM UTC on 30 May 2026, due to a caching error, our artifact host may have responded with JSON objects for any requests that used the /stable/ routes, instead of the expected binary artifacts.

  If you upgraded Determinate Nix via determinate-nixd upgrade in this time period, you may have fetched an invalid determinate-nixd binary.
  You can see if you are affected by attempting to run determinate-nixd status.
  If you are affected, you will see an error like:

  /usr/local/bin/determinate-nixd: line 1: artifact_url:https://bare-domain.us-east-2.swim.install.determinate.systems/determinate-nixd/tag/v3.21.0/macOS: No such file or directory
  

  You can fix this with the following sequence of commands:

  # if you're on macOS:
  curl https://install.determinate.systems/determinate-nixd/tag/v3.21.0/macOS -o determinate-nixd
  # if you're on aarch64-linux:
  curl https://install.determinate.systems/determinate-nixd/tag/v3.21.0/aarch64-linux -o determinate-nixd
  # if you're on x86_64-linux:
  curl https://install.determinate.systems/determinate-nixd/tag/v3.21.0/x86_64-linux -o determinate-nixd
  
  chmod 555 determinate-nixd
  sudo chown 0:0 determinate-nixd
  sudo mv determinate-nixd /usr/local/bin/determinate-nixd
  

  You should now be able to run determinate-nixd status successfully.

  If you have any further questions or concerns, don't hesitate to reach out to us at support@determinate.systems

  Identified