Vendor reports: partial outageResolved · vendor status “resolved”Official status API

Agent Platform Requests Returning HTTP 500 Errors

Reported by DigitalOcean · Cloud & Infrastructure · source last read just now

Vendor start
Jul 27, 2026, 18:31 UTC
Vendor's clock
Resolved
Jul 28, 2026, 15:24 UTC
Vendor's clock
First seen by Statuswall
Before tracking began
Statuswall's clock
Duration
20 h 53 min
From vendor start and resolution

Summary

Built from the facts below, no AI

Potential impact, not a confirmed outage of your systems.

What the vendor confirmed

  • DigitalOcean reports partial outage: "Agent Platform Requests Returning HTTP 500 Errors".[E1, E2]
  • The vendor marked it resolved at 2026-07-28 15:24 UTC.[E3, E7]

Affected products and regions

  • Components: Agent Runtime.[E6]

What is unknown

  • Which regions are affected: the vendor did not say.[E5]
  • Whether your own systems are affected: a vendor report cannot tell you; check your monitoring.

Last update in these facts: 2026-07-28 15:24 UTC · summary s1, evidence 312f664580596790

Evidence (7)
  1. E1DigitalOcean reports partial outage. (vendor) source (opens in a new tab)
  2. E2Vendor title: "Agent Platform Requests Returning HTTP 500 Errors". (vendor) source (opens in a new tab)
  3. E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
  4. E4Vendor-reported start: 2026-07-27 18:31 UTC. (vendor) source (opens in a new tab)
  5. E5The vendor did not state which regions are affected. (Statuswall)
  6. E6Components the vendor attached: Agent Runtime. (vendor) source (opens in a new tab)
  7. E7Vendor-reported resolution: 2026-07-28 15:24 UTC. (vendor) source (opens in a new tab)

Affected scope

Not stated by the vendor

Components: Agent Runtime

The vendor's feed gives no region for this incident. It is not assumed to be global.

Potential relevance

DigitalOcean is not in your stack. Follow it to see whether reports like this fall inside the regions you use.

Timeline

Vendor times come from the vendor. “Seen by Statuswall” times are when Statuswall noticed a change, which can lag the vendor by a few minutes. Statuswall does not store the vendor's update text; read it on the official page.

  1. Jul 27, 2026, 18:31 UTCVendor-reported startVendor time
  2. Jul 28, 2026, 15:24 UTCVendor-reported resolutionVendor time

No changes observed yet. Statuswall began recording changes on incidents in November 2026.