System Status

This incident has been resolved.

A fix has been implemented and we are monitoring builds. Standard flyctl builds should be working again for customers in all regions.

We have identified an issue with deploying via Depot for users connecting through our SYD and JNB regions. Affected customers in these regions can deploy successfully using the --depot=false or --buildkit arguments to flyctl.

We are investigating reports of Depot builds failing for some customers. Affected customers can deploy successfully using the --depot=false or --buildkit arguments to flyctl.

This incident has been resolved.

Private networking between Fly Machines is resolved, and most outbound connections are healthy. We're continuing to monitor the network, and some issues will still be expected from clients physically located in US West until upstream transit issues are resolved.

We are investigating upstream network issues from US West Coast (SJC, LAX). Apps hosted in US West regions may experience higher latency or packet loss, and requests from clients physically located in US West may experience higher latency.

This incident has been resolved.

Error rates have decreased. We are continuing to monitor the API health.

We're aware of a problem affecting a subset of Sprites users. We are investigating the source of the issue.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We're updating the affected region list to also include SJC since this seems to be a wider upstream issue in US West Coast.

We have put in some temporary mitigations along with our providers. However since the root cause of this issue lies within a bigger upstream transit provider, you may continue to see some elevated latency and connection issues in/around affected regions. We're still working closely with them to resolve the root cause.

We have observed an upstream network issue in LAX. Connections to some destinations may see elevated latency and packet loss. We're working with our upstream to resolve this issue.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We are investigating an issue with the background job runner for our API. Actions that require a background job, such as creating apps, assigning IP addresses, or creating/renewing certificates, may fail at this time.