Fly.io Status

Resolved: This incident has been resolved. It was caused by a recent flyctl update and only apps deployed with flyctl version v0.3.227 were affected. We have deployed a server-side workaround.

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

Identified: We will be rolling out a fix shortly

Identified: We have identified an issue affecting newly-allocated Anycast ingress IPv6 addresses for some apps and are working to deploy a fix. These apps may experience timeouts when connecting over IPv6 (which some clients default to).

Investigating: We are currently investigating issues with some apps on IPv6.

Resolved: This incident has been resolved.

Monitoring: Our metrics show that machines API has mostly recovered. We're still working through a small number of degraded Managed Postgres clusters.

Monitoring: We have identified and implemented a fix for the root cause of this incident and are monitoring the results. Machines API should be seeing recovery.

On the Managed Postgres side, New MPG creates should be working. A small number of clusters remain degraded, or are experiencing connectivity issues. We are continuing to restore these as quickly as possible.

Identified: We are continuing to work on a fix for this issue. Users will still see elevated error rates creating new apps, machines, and MPG clusters, as well as other API operations. Users may also see newly created machines remaining in a created state for an extended period before starting.

Identified: We are continuing to work on a fix for this issue.

Identified: We are continuing to see elevated errors with creating new apps, new MPG clusters, and setting secrets. A small number of MPG clusters continue to see connectivity errors. We are continuing to work on these issues.

Identified: We continue to see increased error rates creating new apps and MPG clusters, as well as with setting secrets. We are continuing to work to resolve these issues.

A small number of MPG clusters are still experiencing connectivity issues. We are working to restore these to a healthy state as quickly as possible.

Identified: We have identified some continuing issues with creating new apps and secrets and are working to resolve them.

Identified: Our monitoring indicates that machines API, flyctl and dashboard access should have recovered. Some Managed Postgres clusters may still be affected -- Rest assured that your cluster's data is intact while we are working to recover them to a working state.

Identified: We have identified and implemented a fix for the API outage. Some Managed Postgres clusters may be affected as a secondary effect and we are currently working to restore them.

Investigating: We are investigating an increase in errors that affects numerous API endpoints including the Machines API, flyctl and dashboard.

Resolved: This incident has been resolved.

Monitoring: Our metrics show that machines API has mostly recovered. We're still working through a small number of degraded Managed Postgres clusters.

Monitoring: We have identified and implemented a fix for the root cause of this incident and are monitoring the results. Machines API should be seeing recovery.

On the Managed Postgres side, New MPG creates should be working. A small number of clusters remain degraded, or are experiencing connectivity issues. We are continuing to restore these as quickly as possible.

Identified: We are continuing to work on a fix for this issue. Users will still see elevated error rates creating new apps, machines, and MPG clusters, as well as other API operations. Users may also see newly created machines remaining in a created state for an extended period before starting.

Identified: We are continuing to work on a fix for this issue.

Identified: We are continuing to see elevated errors with creating new apps, new MPG clusters, and setting secrets. A small number of MPG clusters continue to see connectivity errors. We are continuing to work on these issues.

Identified: We continue to see increased error rates creating new apps and MPG clusters, as well as with setting secrets. We are continuing to work to resolve these issues.

A small number of MPG clusters are still experiencing connectivity issues. We are working to restore these to a healthy state as quickly as possible.

Identified: We have identified some continuing issues with creating new apps and secrets and are working to resolve them.

Identified: Our monitoring indicates that machines API, flyctl and dashboard access should have recovered. Some Managed Postgres clusters may still be affected -- Rest assured that your cluster's data is intact while we are working to recover them to a working state.

Identified: We have identified and implemented a fix for the API outage. Some Managed Postgres clusters may be affected as a secondary effect and we are currently working to restore them.

Investigating: We are investigating an increase in errors that affects numerous API endpoints including the Machines API, flyctl and dashboard.

Resolved: This incident has been resolved.

Monitoring: We are continuing to monitor for any further issues.

Monitoring: A fix has been implemented and we are monitoring the results

Investigating: We are currently investigating an issue with machines api and app deploy

Resolved: This incident has been resolved.

Monitoring: The issue appears to be resolved. We’re monitoring further to be certain.

Investigating: We’re investigating network issues in the fra region

Resolved: This incident has been resolved.

Monitoring: A mitigation is in place and IPv4 and IPv6 connectivity has returned to normal. We are continuing to monitor.

Investigating: We are continuing to investigate this issue.

Investigating: We are investigating alerts and reports of unstable networking (dropped packets, closed connections) in our IAD region. This impacts both user applications and Managed Postgres clusters as well as some API operations.

Resolved: This incident has been resolved.

Investigating: A mitigation has been implemented restoring normal network connectivity. We are still working with our upstream providers to address the root cause.

Investigating: We are observing IPv4 and IPv6 network instability in IAD affecting user Apps, as well as Managed Postgres clusters and some API operations. We are working with our upstream network infrastructure providers to resolve the issue.

Resolved: This incident has been resolved.

Monitoring: Traffic appears to have resolved. We will continue to monitor network performance and reroute as needed.

Investigating: We are investigating partially degraded routing between Sydney and some regions in Europe and North America.

Resolved: This incident has been resolved.

Monitoring: Our metrics show that machines API has mostly recovered. We're still working through a small number of degraded Managed Postgres clusters.

Monitoring: We have identified and implemented a fix for the root cause of this incident and are monitoring the results. Machines API should be seeing recovery.

On the Managed Postgres side, New MPG creates should be working. A small number of clusters remain degraded, or are experiencing connectivity issues. We are continuing to restore these as quickly as possible.

Identified: We are continuing to work on a fix for this issue. Users will still see elevated error rates creating new apps, machines, and MPG clusters, as well as other API operations. Users may also see newly created machines remaining in a created state for an extended period before starting.

Identified: We are continuing to work on a fix for this issue.

Identified: We are continuing to see elevated errors with creating new apps, new MPG clusters, and setting secrets. A small number of MPG clusters continue to see connectivity errors. We are continuing to work on these issues.

Identified: We continue to see increased error rates creating new apps and MPG clusters, as well as with setting secrets. We are continuing to work to resolve these issues.

A small number of MPG clusters are still experiencing connectivity issues. We are working to restore these to a healthy state as quickly as possible.

Identified: We have identified some continuing issues with creating new apps and secrets and are working to resolve them.

Identified: Our monitoring indicates that machines API, flyctl and dashboard access should have recovered. Some Managed Postgres clusters may still be affected -- Rest assured that your cluster's data is intact while we are working to recover them to a working state.

Identified: We have identified and implemented a fix for the API outage. Some Managed Postgres clusters may be affected as a secondary effect and we are currently working to restore them.

Investigating: We are investigating an increase in errors that affects numerous API endpoints including the Machines API, flyctl and dashboard.

Resolved: This incident has been resolved.

Monitoring: A fix for this issue has been deployed by Depot, we are re-enabling Depot builders and monitoring for any problems.

Investigating: Deploys and image builds can fail in the "Waiting for Depot builder" step. We are investigating why Depot builders are not coming up, and have switched all builds to use Fly native builders temporarily. If you're still stuck in "Waiting for Depot builder", stop and restart your deploy, or use fly deploy --depot=false.

Resolved: This incident has been resolved.

Monitoring: A mitigation is in place and IPv4 and IPv6 connectivity has returned to normal. We are continuing to monitor.

Investigating: We are continuing to investigate this issue.

Investigating: We are investigating alerts and reports of unstable networking (dropped packets, closed connections) in our IAD region. This impacts both user applications and Managed Postgres clusters as well as some API operations.

Resolved: This incident has been resolved.

Investigating: A mitigation has been implemented restoring normal network connectivity. We are still working with our upstream providers to address the root cause.

Investigating: We are observing IPv4 and IPv6 network instability in IAD affecting user Apps, as well as Managed Postgres clusters and some API operations. We are working with our upstream network infrastructure providers to resolve the issue.

Resolved: This incident has been resolved.

Monitoring: A fix for this issue has been deployed by Depot, we are re-enabling Depot builders and monitoring for any problems.

Investigating: Deploys and image builds can fail in the "Waiting for Depot builder" step. We are investigating why Depot builders are not coming up, and have switched all builds to use Fly native builders temporarily. If you're still stuck in "Waiting for Depot builder", stop and restart your deploy, or use fly deploy --depot=false.

Resolved: This incident has been resolved.

Monitoring: Our metrics show that machines API has mostly recovered. We're still working through a small number of degraded Managed Postgres clusters.

Monitoring: We have identified and implemented a fix for the root cause of this incident and are monitoring the results. Machines API should be seeing recovery.

On the Managed Postgres side, New MPG creates should be working. A small number of clusters remain degraded, or are experiencing connectivity issues. We are continuing to restore these as quickly as possible.

Identified: We are continuing to work on a fix for this issue. Users will still see elevated error rates creating new apps, machines, and MPG clusters, as well as other API operations. Users may also see newly created machines remaining in a created state for an extended period before starting.

Identified: We are continuing to work on a fix for this issue.

Identified: We are continuing to see elevated errors with creating new apps, new MPG clusters, and setting secrets. A small number of MPG clusters continue to see connectivity errors. We are continuing to work on these issues.

Identified: We continue to see increased error rates creating new apps and MPG clusters, as well as with setting secrets. We are continuing to work to resolve these issues.

A small number of MPG clusters are still experiencing connectivity issues. We are working to restore these to a healthy state as quickly as possible.

Identified: We have identified some continuing issues with creating new apps and secrets and are working to resolve them.

Identified: Our monitoring indicates that machines API, flyctl and dashboard access should have recovered. Some Managed Postgres clusters may still be affected -- Rest assured that your cluster's data is intact while we are working to recover them to a working state.

Identified: We have identified and implemented a fix for the API outage. Some Managed Postgres clusters may be affected as a secondary effect and we are currently working to restore them.

Investigating: We are investigating an increase in errors that affects numerous API endpoints including the Machines API, flyctl and dashboard.

Resolved: This incident has been resolved.

Monitoring: Our metrics show that machines API has mostly recovered. We're still working through a small number of degraded Managed Postgres clusters.

Monitoring: We have identified and implemented a fix for the root cause of this incident and are monitoring the results. Machines API should be seeing recovery.

On the Managed Postgres side, New MPG creates should be working. A small number of clusters remain degraded, or are experiencing connectivity issues. We are continuing to restore these as quickly as possible.

Identified: We are continuing to work on a fix for this issue. Users will still see elevated error rates creating new apps, machines, and MPG clusters, as well as other API operations. Users may also see newly created machines remaining in a created state for an extended period before starting.

Identified: We are continuing to work on a fix for this issue.

Identified: We are continuing to see elevated errors with creating new apps, new MPG clusters, and setting secrets. A small number of MPG clusters continue to see connectivity errors. We are continuing to work on these issues.

Identified: We continue to see increased error rates creating new apps and MPG clusters, as well as with setting secrets. We are continuing to work to resolve these issues.

A small number of MPG clusters are still experiencing connectivity issues. We are working to restore these to a healthy state as quickly as possible.

Identified: We have identified some continuing issues with creating new apps and secrets and are working to resolve them.

Identified: Our monitoring indicates that machines API, flyctl and dashboard access should have recovered. Some Managed Postgres clusters may still be affected -- Rest assured that your cluster's data is intact while we are working to recover them to a working state.

Identified: We have identified and implemented a fix for the API outage. Some Managed Postgres clusters may be affected as a secondary effect and we are currently working to restore them.

Investigating: We are investigating an increase in errors that affects numerous API endpoints including the Machines API, flyctl and dashboard.

Resolved: This incident has been resolved.

Investigating: A mitigation has been implemented restoring normal network connectivity. We are still working with our upstream providers to address the root cause.

Investigating: We are observing IPv4 and IPv6 network instability in IAD affecting user Apps, as well as Managed Postgres clusters and some API operations. We are working with our upstream network infrastructure providers to resolve the issue.

Resolved: This incident has been resolved.

Monitoring: Our metrics show that machines API has mostly recovered. We're still working through a small number of degraded Managed Postgres clusters.

Monitoring: We have identified and implemented a fix for the root cause of this incident and are monitoring the results. Machines API should be seeing recovery.

On the Managed Postgres side, New MPG creates should be working. A small number of clusters remain degraded, or are experiencing connectivity issues. We are continuing to restore these as quickly as possible.

Identified: We are continuing to work on a fix for this issue. Users will still see elevated error rates creating new apps, machines, and MPG clusters, as well as other API operations. Users may also see newly created machines remaining in a created state for an extended period before starting.

Identified: We are continuing to work on a fix for this issue.

Identified: We are continuing to see elevated errors with creating new apps, new MPG clusters, and setting secrets. A small number of MPG clusters continue to see connectivity errors. We are continuing to work on these issues.

Identified: We continue to see increased error rates creating new apps and MPG clusters, as well as with setting secrets. We are continuing to work to resolve these issues.

A small number of MPG clusters are still experiencing connectivity issues. We are working to restore these to a healthy state as quickly as possible.

Identified: We have identified some continuing issues with creating new apps and secrets and are working to resolve them.

Identified: Our monitoring indicates that machines API, flyctl and dashboard access should have recovered. Some Managed Postgres clusters may still be affected -- Rest assured that your cluster's data is intact while we are working to recover them to a working state.

Identified: We have identified and implemented a fix for the API outage. Some Managed Postgres clusters may be affected as a secondary effect and we are currently working to restore them.

Investigating: We are investigating an increase in errors that affects numerous API endpoints including the Machines API, flyctl and dashboard.

Resolved: This incident has been resolved.

Monitoring: Our metrics show that machines API has mostly recovered. We're still working through a small number of degraded Managed Postgres clusters.

Monitoring: We have identified and implemented a fix for the root cause of this incident and are monitoring the results. Machines API should be seeing recovery.

On the Managed Postgres side, New MPG creates should be working. A small number of clusters remain degraded, or are experiencing connectivity issues. We are continuing to restore these as quickly as possible.

Identified: We are continuing to work on a fix for this issue. Users will still see elevated error rates creating new apps, machines, and MPG clusters, as well as other API operations. Users may also see newly created machines remaining in a created state for an extended period before starting.

Identified: We are continuing to work on a fix for this issue.

Identified: We are continuing to see elevated errors with creating new apps, new MPG clusters, and setting secrets. A small number of MPG clusters continue to see connectivity errors. We are continuing to work on these issues.

Identified: We continue to see increased error rates creating new apps and MPG clusters, as well as with setting secrets. We are continuing to work to resolve these issues.

A small number of MPG clusters are still experiencing connectivity issues. We are working to restore these to a healthy state as quickly as possible.

Identified: We have identified some continuing issues with creating new apps and secrets and are working to resolve them.

Identified: Our monitoring indicates that machines API, flyctl and dashboard access should have recovered. Some Managed Postgres clusters may still be affected -- Rest assured that your cluster's data is intact while we are working to recover them to a working state.

Identified: We have identified and implemented a fix for the API outage. Some Managed Postgres clusters may be affected as a secondary effect and we are currently working to restore them.

Investigating: We are investigating an increase in errors that affects numerous API endpoints including the Machines API, flyctl and dashboard.

Resolved: This incident has been resolved.

Monitoring: Our metrics show that machines API has mostly recovered. We're still working through a small number of degraded Managed Postgres clusters.

Monitoring: We have identified and implemented a fix for the root cause of this incident and are monitoring the results. Machines API should be seeing recovery.

On the Managed Postgres side, New MPG creates should be working. A small number of clusters remain degraded, or are experiencing connectivity issues. We are continuing to restore these as quickly as possible.

Identified: We are continuing to work on a fix for this issue. Users will still see elevated error rates creating new apps, machines, and MPG clusters, as well as other API operations. Users may also see newly created machines remaining in a created state for an extended period before starting.

Identified: We are continuing to work on a fix for this issue.

Identified: We are continuing to see elevated errors with creating new apps, new MPG clusters, and setting secrets. A small number of MPG clusters continue to see connectivity errors. We are continuing to work on these issues.

Identified: We continue to see increased error rates creating new apps and MPG clusters, as well as with setting secrets. We are continuing to work to resolve these issues.

A small number of MPG clusters are still experiencing connectivity issues. We are working to restore these to a healthy state as quickly as possible.

Identified: We have identified some continuing issues with creating new apps and secrets and are working to resolve them.

Identified: Our monitoring indicates that machines API, flyctl and dashboard access should have recovered. Some Managed Postgres clusters may still be affected -- Rest assured that your cluster's data is intact while we are working to recover them to a working state.

Identified: We have identified and implemented a fix for the API outage. Some Managed Postgres clusters may be affected as a secondary effect and we are currently working to restore them.

Investigating: We are investigating an increase in errors that affects numerous API endpoints including the Machines API, flyctl and dashboard.

Resolved: This incident has been resolved.

Monitoring: Our metrics show that machines API has mostly recovered. We're still working through a small number of degraded Managed Postgres clusters.

Monitoring: We have identified and implemented a fix for the root cause of this incident and are monitoring the results. Machines API should be seeing recovery.

On the Managed Postgres side, New MPG creates should be working. A small number of clusters remain degraded, or are experiencing connectivity issues. We are continuing to restore these as quickly as possible.

Identified: We are continuing to work on a fix for this issue. Users will still see elevated error rates creating new apps, machines, and MPG clusters, as well as other API operations. Users may also see newly created machines remaining in a created state for an extended period before starting.

Identified: We are continuing to work on a fix for this issue.

Identified: We are continuing to see elevated errors with creating new apps, new MPG clusters, and setting secrets. A small number of MPG clusters continue to see connectivity errors. We are continuing to work on these issues.

Identified: We continue to see increased error rates creating new apps and MPG clusters, as well as with setting secrets. We are continuing to work to resolve these issues.

A small number of MPG clusters are still experiencing connectivity issues. We are working to restore these to a healthy state as quickly as possible.

Identified: We have identified some continuing issues with creating new apps and secrets and are working to resolve them.

Identified: Our monitoring indicates that machines API, flyctl and dashboard access should have recovered. Some Managed Postgres clusters may still be affected -- Rest assured that your cluster's data is intact while we are working to recover them to a working state.

Identified: We have identified and implemented a fix for the API outage. Some Managed Postgres clusters may be affected as a secondary effect and we are currently working to restore them.

Investigating: We are investigating an increase in errors that affects numerous API endpoints including the Machines API, flyctl and dashboard.