Rewindex

CompaniesDigitalOceanIncidents

DigitalOcean: Static Site components for the App Platform in NYC3 region

MinorStatus: resolvedStarted Resolved (29 min)1 updatestatus.digitalocean.com (opens in new tab)
Part of an outage event

AWS outage, Sep 28, 2023 · 23 vendors, 24 incidents

DigitalOcean’s incident started in the same window without naming AWS (timing only, not evidence of a link). (timing only, posted +10 min vs the first vendor naming AWS)

Swipe sideways to see the whole diagram.

same windowAWSown incident not archivedWithin an hour3 vendors, 1 blamed AWSAbly, Temporal Cloud, Keeper1 to 4 hours later4 vendors, 3 blamed AWSDremio, Firebolt, CockroachDB, Elastic CloudLater3 vendors, 1 blamed AWSAptible, Temporal Cloud, ConfluentDigitalOcean (this incident)posted +10 min
same windowAWSown incident not archivedWithin an hour3 vendors, 1 blamed AWSAbly, Temporal Cloud, Keeper1 to 4 hours later4 vendors, 3 blamed AWSDremio, Firebolt, CockroachDB,Elastic CloudLater3 vendors, 1 blamed AWSAptible, Temporal Cloud,ConfluentDigitalOcean (this incident)posted +10 min
DigitalOcean is outlined in red. Groups show up to a few vendors each; the event page lists every incident.
Mermaid source
flowchart LR
  root["AWS<br/>own incident not archived"]:::inferred
  h1["Within an hour<br/>3 vendors, 1 blamed AWS<br/>Ably, Temporal Cloud, Keeper"]:::blames
  root --> h1
  h4["1 to 4 hours later<br/>4 vendors, 3 blamed AWS<br/>Dremio, Firebolt, CockroachDB, Elastic Cloud"]:::blames
  root --> h4
  later["Later<br/>3 vendors, 1 blamed AWS<br/>Aptible, Temporal Cloud, Confluent"]:::blames
  root --> later
  me["DigitalOcean (this incident)<br/>posted +10 min"]:::me
  root -.->|"same window"| me

Full event: timeline, evidence and all vendors →

Detected automatically from incidents that started together and named the same provider. A link means one vendor’s incident named another, not a confirmed cause.

Timeline of updates

  1. resolved

    Our Engineering team has confirmed that the issue with Static Site components for the App Platform in our NYC3 region has been fully resolved. We apologize for the inconvenience. If you continue to experience any issues related to this incident, please open a ticket with our support team from within your Cloud Control Panel.

From DigitalOcean’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.

Impact, status and times are the vendor’s own, as last archived. View on status.digitalocean.com (opens in new tab).

DigitalOcean profileRecent DigitalOcean incidentsMarkdownJSON