Skip to main content
Fly.io

Metrics in some regions are lagging behind

Degraded Lasted 2h 24m · started · Fly.io's page

Level
confirmed
Worst impact
Degraded
Components
Metrics

What to do

  • Check whether you use Fly.io Metrics. Check your stack

    Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
  • Confirm your retries, queues and scheduled jobs caught up after the 2h 24m it lasted.

    Anything that failed between 2026-08-24 10:23 UTC and 2026-08-24 12:47 UTC may need a replay.
  • Subscribe to Fly.io's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=fly works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Fly.io 3

  1. investigating

    We are currently experiencing some metrics lag on servers in some regions. We are provisioning more metric processing instances to accommodate the backlog and catch up.

    provider

  2. monitoring

    All hosts have caught up with metrics and we're monitoring the situation

    provider

  3. resolved

    This is now resolved

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Questions about DWN-6137c5cd9f

Is Fly.io still down?

No, this incident was resolved 2026-08-24 12:47 UTC. For Fly.io's live state, see https://down.guide/fly.

How long did it last?

2h 24m, from 2026-08-24 10:23 UTC to 2026-08-24 12:47 UTC, by the times Fly.io posted.

What was affected?

Fly.io named Metrics.

What caused it?

Fly.io hasn't published a root cause. If it does, it shows here.

Where does this come from?

Fly.io's official status page, https://status.flyio.net, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.