Showing 5 of 27 incidents on Public
Resolved
Oct 16, 2026, 03:24 PM EDT
Status: identified
The fly-metrics.net hosted grafana and log search instance is currently unreachable as a result of . It will return once the host it is on is out of maintenance, approximately 20 minutes.
Logs and Metrics shipped to other sources using things like Fly Telemetry or the Fly Log shipper continue to be available, only the hosted Grafana viewer is unavailable at this time.
Duration: 1h 15mVendor update 3 days ago
Incident community checkThis incident
Resolved
Oct 17, 2026, 01:15 AM EDT
Status: identified
We will be imminently applying rolling restarts across all hosts in our fleet for a critical maintenance. Customer Machines, volumes, and MPG cluster instances on each host will be unavailable while their host reboots.
Each host will be unavailable for 15 - 20 minutes during the restart, and multiple hosts in a region may be down at once. Users should expect a period of downtime or disruption for their apps, especially if they are running on a single machine.
We are aiming for the highest possible uptime during the rollout, while ensuring this is completed quickly.
We will provide a further update once we begin the restart process.
Duration: 12h 52mVendor update 2 days ago
Incident community checkThis incident
Resolved
Oct 15, 2026, 07:33 AM EDT
Status: investigating
We’re seeing elevated error rates and slow responses for some operations that create or change data. Creating new apps, setting or removing secrets, and some app deletions are affected. You may see 500 or 503 errors from `flyctl`, the Machines API, or the dashboard.
Apps and Machines that are already running are not affected. Starting, stopping and reading existing Machines are working normally. We’re investigating and will post another update within 30 minutes.
Duration: 2h 3mVendor update 4 days ago
Incident community checkThis incident
Resolved
Oct 14, 2026, 10:35 PM EDT
Status: resolved
Subset of hosts in FRA were unavailable due to provider network outage which lasted around 10 minutes
Incident community checkThis incident
Resolved
Oct 13, 2026, 09:50 AM EDT
Status: identified
Our log ingestion pipeline is currently backed up. Historical logs will be delayed while the queue is processed.
Duration: 4h 24mVendor update 6 days ago
Incident community checkThis incident
27 incidents visible (ongoing and monitoring). A free account unlocks resolved history and filters.