Minor impactResolvedCloud

Fly.io incident: Delayed ingestion of app logs

Fly.io reported this minor-impact incident on its official status page on Oct 1, 2026, 01:11 UTC. It was resolved after 1h 38m.

Right now Fly.io is operational. Live Fly.io status →

🔔 Get alerted when Fly.io has issuesFree · email alerts · no credit card
Oct 1, 2026, 01:11 UTC
started
Oct 1, 2026, 02:49 UTC
resolved
1h 38m
duration
Minor
impact
  1. resolvedOct 1, 2026, 02:49 UTC

    This incident has been resolved.

  2. monitoringOct 1, 2026, 02:35 UTC

    The backlog of app logs has been processed, and we're monitoring the health of the log cluster. No logs were lost.

  3. identifiedOct 1, 2026, 02:27 UTC

    We've resolved the ingestion issue and our systems are processing the backlog of app logs. No logs have been lost.

  4. identifiedOct 1, 2026, 01:39 UTC

    We've identified the cause of the slowed log ingestion and are working on a fix.

  5. investigatingOct 1, 2026, 01:11 UTC

    We're investigating delayed ingestion of app logs across all regions. New logs from machines may not be visible, but past logs are still available.

What APIStatus.watch saw

  • Oct 1, 2026, 01:15 UTCoperational → degraded
  • Oct 1, 2026, 02:40 UTCdegraded → operational

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

How often does Fly.io have incidents?

Fly.io reported 19 incidents in the last 90 days, 11 of them major or critical. A typical incident lasted 57 min. See Fly.io's uptime and incident history

Fly.io incident on Oct 1, 2026: Delayed ingestion of app logs · APIStatus.watch