Skip to main content
DigitalOcean

Volume Attach/Detach events in FRA1

Degraded Lasted 0m · started · DigitalOcean's page

Level
confirmed
Worst impact
Degraded
Components
FRA1
Down Index
8of 100

What to do

  • Check whether you use DigitalOcean FRA1. 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 0m it lasted.

    Anything that failed between 2026-08-13 14:59 UTC and 2026-08-13 14:59 UTC may need a replay.
  • Subscribe to DigitalOcean's feed to hear about the next one first. RSS feed

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

Updates from DigitalOcean 1

  1. resolved

    Between Aug 13, 09:50 UTC and 14:30 UTC, customers in the FRA1 region experienced an issue affecting Block Storage Volumes attachment and detachment operations on Droplets and Managed Kubernetes clusters. During this window, customers may have encountered delays or been unable to attach and detach Block Storage Volumes from their resources. Block Storage Volumes attachment and detachment operations now appear to be functioning normally, and customers should no longer experience issues with these operations. For Managed Kubernetes clusters specifically, some residual cleanup of affected volume attachments may still be needed, and our team is actively working through this. We apologize for any inconvenience this may have caused. If you continue to experience issues with Block Storage Volumes operations, please don't hesitate to open a support ticket for further investigation. Our team will be happy to assist you.

    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-eecd940fbc

Is DigitalOcean still down?

No, this incident was resolved 2026-08-13 14:59 UTC. For DigitalOcean's live state, see https://down.guide/digitalocean.

How long did it last?

0m, from 2026-08-13 14:59 UTC to 2026-08-13 14:59 UTC, by the times DigitalOcean posted.

What was affected?

DigitalOcean named FRA1.

What caused it?

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

Where does this come from?

DigitalOcean's official status page, https://status.digitalocean.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.