Fly.io Status

Resolved: This incident has been resolved. Networking in SJC has remained stable over the past two hours.

This was caused by a dark fiber maintenance, which had a larger-than-anticipated impact. As a result, some transport capacity was lost, leading to packet loss to and from our servers.

Investigating: We are continuing to investigate this issue.

Investigating: We are currently investigating networking issues in SJC. Customers may see higher latency and elevated packet loss connecting to machines in this region.

Resolved: This incident has been resolved.

Identified: The issue has been identified and a fix is currently being implemented.

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.

Identified: We have identified an issue causing degraded private networking performance in Ashburn, Virginia, US (IAD). We are currently working to resolve this issue. Public networking is unaffected.

Resolved: This incident has been resolved. Networking in IAD has remained stable over the past two hours.

This was caused by a routing issue with an upstream networking provider that impacted connectivity to some hosts in IAD. We applied a change to work around the bad routing, and the underlying issue that caused this in the first place has been identified and fixed.

Monitoring: A fix has been applied to all impacted IAD hosts and networking performance in the region has returned to normal.

Fly Managed Postgres clusters in IAD should all now be reachable, as well as Phoenix.new IDEs and preview sites.

We are continuing to closely monitor networking performance in the region to ensure stability and full recovery.

Identified: We are continuing to work on implementing the fix to the impacted hosts in IAD.

Identified: The issue has been identified and a fix is being implemented.

Investigating: We are continuing to investigate this issue. Connectivity between a number of hosts in the IAD region is degraded.

Customers will see inbound and outbound issues connecting to and from machines on impacted hosts.

Some Fly Managed Postgres clusters are impacted by this, users may see additional latency or failures connecting to clusters in IAD.

Some users will see 500 errors accessing Phoenix.new IDEs and preview sites at this time.

Investigating: We are currently investigating networking issues in IAD. Customers may see higher latency and elevated packet loss connecting to machines in this region.

Resolved: This incident has been resolved.

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

Investigating: We are currently experiencing a temporary network outage in Miami, USA and are actively working with our upstreams to resolve this issue.

Resolved: This incident has been resolved.

Monitoring: Both regions are stable and appear to have fully recovered. We'll continue to monitor for the next hour.

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

Monitoring: Both regions appear to be recovering. We'll continue to monitor closely.

Investigating: We are continuing to investigate this issue.

Investigating: We are currently investigating this issue.

Resolved: This incident has been resolved.

Monitoring: Both regions are stable and appear to have fully recovered. We'll continue to monitor for the next hour.

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

Monitoring: Both regions appear to be recovering. We'll continue to monitor closely.

Investigating: We are continuing to investigate this issue.

Investigating: We are currently investigating this issue.

Resolved: This incident has been resolved. Networking in SJC has remained stable over the past two hours.

This was caused by a dark fiber maintenance, which had a larger-than-anticipated impact. As a result, some transport capacity was lost, leading to packet loss to and from our servers.

Investigating: We are continuing to investigate this issue.

Investigating: We are currently investigating networking issues in SJC. Customers may see higher latency and elevated packet loss connecting to machines in this region.

Resolved: This incident has been resolved. Networking in IAD has remained stable over the past two hours.

This was caused by a routing issue with an upstream networking provider that impacted connectivity to some hosts in IAD. We applied a change to work around the bad routing, and the underlying issue that caused this in the first place has been identified and fixed.

Monitoring: A fix has been applied to all impacted IAD hosts and networking performance in the region has returned to normal.

Fly Managed Postgres clusters in IAD should all now be reachable, as well as Phoenix.new IDEs and preview sites.

We are continuing to closely monitor networking performance in the region to ensure stability and full recovery.

Identified: We are continuing to work on implementing the fix to the impacted hosts in IAD.

Identified: The issue has been identified and a fix is being implemented.

Investigating: We are continuing to investigate this issue. Connectivity between a number of hosts in the IAD region is degraded.

Customers will see inbound and outbound issues connecting to and from machines on impacted hosts.

Some Fly Managed Postgres clusters are impacted by this, users may see additional latency or failures connecting to clusters in IAD.

Some users will see 500 errors accessing Phoenix.new IDEs and preview sites at this time.

Investigating: We are currently investigating networking issues in IAD. Customers may see higher latency and elevated packet loss connecting to machines in this region.

Resolved: This incident has been resolved. Networking in IAD has remained stable over the past two hours.

This was caused by a routing issue with an upstream networking provider that impacted connectivity to some hosts in IAD. We applied a change to work around the bad routing, and the underlying issue that caused this in the first place has been identified and fixed.

Monitoring: A fix has been applied to all impacted IAD hosts and networking performance in the region has returned to normal.

Fly Managed Postgres clusters in IAD should all now be reachable, as well as Phoenix.new IDEs and preview sites.

We are continuing to closely monitor networking performance in the region to ensure stability and full recovery.

Identified: We are continuing to work on implementing the fix to the impacted hosts in IAD.

Identified: The issue has been identified and a fix is being implemented.

Investigating: We are continuing to investigate this issue. Connectivity between a number of hosts in the IAD region is degraded.

Customers will see inbound and outbound issues connecting to and from machines on impacted hosts.

Some Fly Managed Postgres clusters are impacted by this, users may see additional latency or failures connecting to clusters in IAD.

Some users will see 500 errors accessing Phoenix.new IDEs and preview sites at this time.

Investigating: We are currently investigating networking issues in IAD. Customers may see higher latency and elevated packet loss connecting to machines in this region.