Determinate Systems, Inc. | Status

Updates

• Aug 18, 2025 2:56 PM UTC

  We have not seen any further 504s.

  Resolved
• Aug 8, 2025 11:59 PM UTC (1 week, 2 days, 14 hours, and 57 minutes earlier)

  We optimized a recursive graph traversal, so affected customers should no longer be seeing any 504 errors.

  Monitoring
• Aug 6, 2025 9:26 PM UTC (2 days, 2 hours, and 32 minutes earlier)

  Only a subset of FlakeHub users who are using the fh resolve / fh fetch commands with store paths that have a large number of references are affected.

  We are working on implementing a robust solution.

  If you are experiencing this, feel free to reach out to support@determinate.systems

  Identified
• Aug 6, 2025 7:01 PM UTC (2 hours and 25 minutes earlier)

  We believe we have identified the cause, and are working on a mitigation.

  Identified
• Aug 6, 2025 5:45 PM UTC (1 hour and 16 minutes earlier)

  FlakeHub Cache has started occasionally returning 504s again, despite our earlier mitigation.

  Investigating
• Aug 5, 2025 11:19 PM UTC (18 hours and 26 minutes earlier)

  FlakeHub has not returned any 504s since.

  Resolved
• Aug 5, 2025 8:52 PM UTC (2 hours and 26 minutes earlier)

  We have scaled out FlakeHub Cache infrastructure further to account for a new workload. We're continuing to monitor.

  Monitoring
• Aug 5, 2025 8:02 PM UTC (49 minutes earlier)

  We're investigating an occasional issue with FlakeHub Cache requests failing with 504 errors.

  Investigating