Status Tracker v0.24
Dec 16, 14:58 PST
Resolved – This incident has been resolved.
Dec 16, 14:54 PST
Monitoring – A fix has been deployed and the Fine-tuning API endpoints are no longer returning 500 responses.
Dec 16, 14:47 PST
Update – We are continuing to work on a fix for this issue.
Dec 16, 14:47 PST
Identified – Fine-tuning API endpoints (`/v1/fine_tuning/jobs/*`) are returning high rates of 500 responses. The issue has been identified and a fix is being rolled out.
Dec 16, 18:28 UTC
Resolved – This incident has been resolved.
Dec 16, 15:45 UTC
Monitoring – A fix has been implemented and new production domains will not have a problem. We’re currently working on applying the fix to existing domains. Please continue to follow our status page for updates on this issue.
Dec 16, 15:11 UTC
Identified – We are skipping the domain assignment erroneously for deployments that are intended to be production.
Dec 16, 17:23 UTC
Resolved – This incident has been resolved.
Dec 16, 14:42 UTC
Monitoring – A fix has been implemented and we are monitoring the results.
Dec 16, 13:21 UTC
Update – Our engineers have identified the root cause of the issue and some connectivity has improved. We are now working on resolving the issue fully.
Dec 16, 11:20 UTC
Identified – We have identified a Supavisor connectivity issue in ap-southeast-1. This issue is affecting Supavisor and our Storage functionality. Engineers are working on resolving the issue.
Dec 16, 11:09 UTC
Investigating – We are currently investigating this issue.
Dec 16, 15:30 UTC
Resolved – Our team has identified the issue in Schedule API between 15:30 UTC and 17:00 UTC. We saw performance degradation and 5XX errors in response. Faulty deployment has been reverted quickly in the USA region and rapid recovery is seen. We are monitoring the system for a full recovery right now. The Schedule API is up and running again without any data loss.