Compare the status, incidents stats and history between Cloud 66 and Fly.io
Every service has different practices when updating its status page, so compare these stats with a grain of salt. E.g., one service can be more aggressive when updating its status page than other so that they will have more incidents, but it doesn't mean it is worse than the other.
We are aware of problems when scaling/creating Kubernetes clusters. This appears to be caused by new rate limits imposed by docker hub. The team are working on a solution.
We are currently investigating a number of stuck deployments.
We are aware of issues with our CustomConfig git repositories. This issue impacts direct git access to the CustomConfig git repository. Direct access to CustomConfig pages via the web dashboard and...
We are investigating failures when trying to build using the default Depot builders. The recommended workaround is to use `--depot=false` with `fly deploy`. The error from Depot builders is `Err...
We are investigating reports that connecting to newly created machines via SSH (`fly ssh console`) may fail.
We're addressing elevated network latency and saturation affecting the FRA region. Apps with machines in this region might experience longer response times and possible timeouts (502 errors).
14-day free trial · No credit card required · No code required