Live / DigitalOcean / Incident
DigitalOcean: Agent Platform Requests Returning HTTP 500 Errors
DigitalOcean · digitalocean.comMajor incidentResolved2026-07-28 15:24 UTC
Public — what happened
Summary
DigitalOcean reported a major incident in which requests to its Agent Platform were failing with HTTP 500 errors, beginning on July 27, 2026 at 18:31 UTC. The company said it had pinpointed the problem by 19:44 UTC and was rolling out a fix, though it did not describe the cause or say which customers were affected. DigitalOcean marked the incident resolved on July 28 at 15:24 UTC.
Affected
Agent Runtime
Timeline
- Started — 2026-07-27 18:31 UTC
- Investigating — 2026-07-27 18:31 UTC
- Identified — 2026-07-27 19:44 UTC
- Resolved — 2026-07-28 15:24 UTC · 20h 53m after it started
With SquidGrid — where it starts on the route
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 seeCustomers 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