Incidentsby GlyphBlock Storage Volumes in NYC1 and AMS3
Nov 17, 19:26 UTCNov 17, 19:26 UTC
Duration
0m
Impact
Informational
Root cause
Not disclosed
DigitalOcean, 90 days
12 incidents
Affected
Not listed by the vendor.
Final update
From 16:59 to 17:34 UTC, our Engineering team observed an issue with block storage volumes in the NYC1 and AMS3 regions. During this time, users may have experienced failures when attempting create, snapshot, attach, detach, or resize volumes. There was no impact to performance or availability of existing volumes. Our team has fully resolved the issues as of 17:34 UTC and volumes should be operating normally. If you continue to experience problems, please open a ticket with our support team from within your Cloud Control Panel. We apologize for any inconvenience caused.
Timeline
- Resolved · Nov 17, 19:26 UTC
From 16:59 to 17:34 UTC, our Engineering team observed an issue with block storage volumes in the NYC1 and AMS3 regions. During this time, users may have experienced failures when attempting create, snapshot, attach, detach, or resize volumes. There was no impact to performance or availability of existing volumes. Our team has fully resolved the issues as of 17:34 UTC and volumes should be operating normally. If you continue to experience problems, please open a ticket with our support team from within your Cloud Control Panel. We apologize for any inconvenience caused.
More from DigitalOcean
Full historyKubernetes Cluster Management Operationslasted 3h 40mApp Platform Deploymentslasted 0mDNS Resolution for Managed Kuberneteslasted 1h 27mVPC Networking Availabilitylasted 1h 35mA Network Disruption in BLR1 Region Impacted Multiple Products (Resolved)lasted 0mSupport Portal Service Disruptionlasted 11h 21m