Live  /  DigitalOcean  /  Incident

DigitalOcean: Functions on App Platform

DigitalOcean · digitalocean.comMinor incidentResolved2026-08-06 21:05 UTC
Public — what happened

Summary

DigitalOcean reported a minor problem with Functions running on its App Platform starting at 19:01 UTC on August 6, 2026, where building or deploying Functions components could fail and calls to Functions endpoints could return 504 errors. The company said the failed requests stemmed from an SSL error that occurred when App Platform tried to pass traffic along to Functions, and that the issue appeared limited to Functions deployed within App Platform. A fix was put in place by 20:02 UTC, after which DigitalOcean watched the service, and it declared the incident fully resolved at 21:05 UTC.

Affected

Global, Global

As listed on DigitalOcean’s status page.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

Independent path health

The status page is the symptom. SquidGrid measures the paths that reach DigitalOcean against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.

🔒 Sign in to see
Customers get the live Provider Assessment Report for DigitalOcean: paths off baseline right now, where on the route conditions change, and its full incident track record.

Included with any paid plan.

Open the DigitalOcean report →

More from DigitalOcean

The full archive is on the DigitalOcean status & history page.

Related: DigitalOcean status & history. SquidGrid is not affiliated with DigitalOcean.