Incidentsby GlyphSpaces Access Keys and DigitalOcean Container Registry
Dec 15, 16:19 UTCDec 15, 16:19 UTC
Duration
0m
Impact
Informational
Root cause
Not disclosed
DigitalOcean, 90 days
12 incidents
Affected
Not listed by the vendor.
Final update
From 08:28 to 13:03 UTC, Our Engineering team observed an issue with Spaces Access keys for DOCR in AMS3 region. During this time, users encountered an error with "403 (InvalidAccessKeyId): The access key ID you provided does not exist in our records" while accessing spaces keys. Our team has fully resolved the issues as of 13:03 UTC. 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 · Dec 15, 16:19 UTC
From 08:28 to 13:03 UTC, Our Engineering team observed an issue with Spaces Access keys for DOCR in AMS3 region. During this time, users encountered an error with "403 (InvalidAccessKeyId): The access key ID you provided does not exist in our records" while accessing spaces keys. Our team has fully resolved the issues as of 13:03 UTC. 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