Live / DigitalOcean / Incident
DigitalOcean: Limited access to Deepseek V4 Pro model
DigitalOcean · digitalocean.comMajor incidentResolved2026-07-05 00:53 UTC
Public — what happened
Summary
DigitalOcean said it began looking into problems with the Deepseek V4 Pro model on its Serverless Inference and Agent Platform services at 22:13 UTC on July 4, 2026, with users getting 429 errors when trying to use the model. The company reported putting a fix in place by 23:18 UTC and then watching to confirm it worked. It did not share a cause. DigitalOcean marked the issue fully resolved at 00:53 UTC on July 5.
Affected
Inference, Model Services
Timeline
- Started — 2026-07-04 22:13 UTC
- Investigating — 2026-07-04 22:13 UTC
- Monitoring — 2026-07-04 23:18 UTC
- Resolved — 2026-07-05 00:53 UTC · 2h 40m 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