Determinate Systems, Inc. | Status

Updates

• May 29, 2026 1:02 PM UTC

  The migration continues to look healthy.

  Resolved
• May 29, 2026 1:51 AM UTC (11 hours and 10 minutes earlier)

  We have moved install.determinate.systems from our previous legacy vendor and consolidated it into our primary AWS estate.

  For background, the vast majority of traffic to install.determinate.systems uses SRV record resolution to look up a collection of backends that we maintain independently for redundancy. That way, those clients can intelligently try multiple backends until it succeeds. You can try this out yourself here:

  dig @ns-751.awsdns-29.net _detsys_ids._tcp.install.determinate.systems srv
  

  Several months ago, we used this SRV mechanism to move about 90% of traffic to the install.determinate.systems service to other subdomain deployments in our AWS estate, but left the root install.determinate.systems on the legacy vendor since it was a higher risk migration.

  However, given today's (and other recent) performance and availability issues we reprioritized the migration of the root service to AWS. That's what we completed today. This change mostly impacts a relatively small subset of clients to that domain, but unfortunately the most obvious one -- Nix itself.

  Substitutions are now enabled as well, and behavior should be back to normal.

  Monitoring
• May 28, 2026 10:42 PM UTC (3 hours and 9 minutes earlier)

  For the moment, we have disabled substitution via install.determinate.systems -- all NAR and .narinfo requests will return 404s.

  Investigating
• May 28, 2026 10:41 PM UTC (1 minute earlier)

  We're aware of an issue where using the install.determinate.systems cache proxy is exceedingly slow and are investigating.

  Investigating