Resolved
This incident has been resolved.
Posted Dec 17, 2025 - 02:47 UTC
Monitoring
Network performance across Fly.io has returned to normal. This incident primarily impacted machines in the SJC and EWR regions.
Metrics are largely caught up, but users may still see a slight delay in reporting as the cluster finishes catching up.
Posted Dec 17, 2025 - 02:27 UTC
Update
A change has been made and metrics on fly-metrics.net are backfilling. Users may still see a slight delay or gaps in new metrics being reported as the backfill completes.
We continue to see higher than usual latency and packetloss across the network. We are continuing to investigate.
Posted Dec 17, 2025 - 02:12 UTC
Investigating
We are currently investigating increased latency and packet loss across multiple regions. Customers may see additional latency on requests at this time.
Relatedly, prometheus metrics reported via fly-metrics.net is currently degraded. Users may see delays or gaps in metrics at this time. We are working to address both issues.
Posted Dec 17, 2025 - 01:46 UTC
This incident affected: Regional Availability (AMS - Amsterdam, Netherlands, ARN - Stockholm, Sweden, BOM - Mumbai, India, CDG - Paris, France, DFW - Dallas, Texas (US), EWR - Secaucus, NJ (US), FRA - Frankfurt, Germany, GRU - Sao Paulo, Brazil, IAD - Ashburn, Virginia (US), JNB - Johannesburg, South Africa, LAX - Los Angeles, California (US), LHR - London, United Kingdom, NRT - Tokyo, Japan, ORD - Chicago, Illinois (US), SIN - Singapore, SJC - San Jose, California (US), SYD - Sydney, Australia, YYZ - Toronto, Canada) and Metrics.