Fly.io reported "Historical logs are currently delayed" on its status page at 2026-10-13 09:25 UTC.

Fly.io did not name the affected components. The updates on this page have the details.

When did the incident start and end?

It started at 2026-10-13 09:25 UTC and ended at 2026-10-13 13:50 UTC. It lasted 4 h 25 min.

How do I get alerts for Fly.io?

Subscribe to the Fly.io live feed over RSS or in Slack, or add the outages.live MCP server to your coding agent.

Where does this information come from?

From the official status page of Fly.io. outages.live reads it every few minutes and keeps every update.

Fly.ioIncident · 2026-10-13 09:25 UTC

Historical logs are currently delayed

ResolvedOfficial update

This has been resolved

The latest update from Fly.io.

State

Resolved

Started

20 d ago

2026-10-13 09:25 UTC

Lasted

4 h 25 min

until 2026-10-13 13:50 UTC

Worst impact

Degraded

Timeline

3 updates

09:2510:3111:3712:4313:50

DegradedUpdate postedTimes in UTC

Identified

1 h 45 min 39%

Monitoring

2 h 40 min 61%

Updates

Times in UTC

As posted by Fly.io

Resolved2026-10-13 13:50 UTC

This has been resolved

Monitoring2026-10-13 11:09 UTC

Logs are caught up and we are monitoring the situation

Identified2026-10-13 09:25 UTC

Our log ingestion pipeline is currently backed up. Historical logs will be delayed while the queue is processed.

Fly.io in the last 90 days

Full history

90 days agoToday

Incidents in 90 days

Days with an incident

Median duration

1 h 49 min

This incident

2.4× 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