outages.live
Live
Fly.ioIncident ยท 2026-10-16 18:08 UTC

Fly-metrics.net Grafana Dashboard Outage

ResolvedOfficial update

The [fly-metrics.net](https://fly-metrics.net) hosted Grafana and log search instance is now fully reachable.

The latest update from Fly.io.

State

Resolved

Started

16 d ago

2026-10-16 18:08 UTC

Lasted

1 h 16 min

until 2026-10-16 19:24 UTC

Worst impact

Partial outage

Timeline

3 updates
18:0818:2718:4619:0519:24
Partial outageUpdate postedTimes in UTC

Identified

35 min 46%

Monitoring

41 min 54%

Updates

Times in UTC

As posted by Fly.io

Resolved2026-10-16 19:24 UTC

The [fly-metrics.net](https://fly-metrics.net) hosted Grafana and log search instance is now fully reachable.

Monitoring2026-10-16 18:43 UTC

The [fly-metrics.net](https://fly-metrics.net) hosted Grafana and log search instance should now be reachable again. We're continuing to monitor for any issues as a result of .

Identified2026-10-16 18:08 UTC

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.

Fly.io in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

20

Days with an incident

16

Median duration

1 h 49 min

This incident

31% shorter than the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

12 h 53 min
median 1 h 49 min
90 days agoToday

Other Fly.io incidents

All incidents

Fly.ioยทOutbound IPv4 connectivity failures in ARN, JNB, and GRU

Outbound IPv4 connectivity failed for machines with static egress IPs in the ARN, JNB, and GRU regions. IPv6 connectivity was not affected. Fly.io resolved the incident after 2 hours and 10 minutes.

Resolvedresolved 5 h ago

Fly.ioยทSlow image pulls delaying Machine starts in IAD

Image pull times in IAD have returned to normal.

Resolvedresolved 2 d ago

Fly.ioยทElevated issues with the Machines API

The incident has been resolved.

Resolvedresolved 3 d ago

Fly.ioยทCreating WireGuard peers in ARN is currently broken

The ARN WireGuard gateways are up

Resolvedresolved 3 d ago

Fly.ioยทDegraded networking to AWS IPs

This incident has been resolved, connectivity from AWS to all of our hosts is back to normal.

Resolvedresolved 6 d ago

Follow Fly.io

Your coding agent knows when Fly.io is down, and tells you when a failure is theirs, not yours. You can also get Fly.io incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "fly" and tell me if Fly.io has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.live/feed.xml?providers=fly
Slack
/feed subscribe https://outages.live/feed.xml?providers=fly

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane