Live / DigitalOcean / Incident
DigitalOcean: Response Degradation Impacting Kimi-K3
DigitalOcean · digitalocean.comMinor incidentResolved2026-07-30 06:15 UTC
Public — what happened
Summary
DigitalOcean reported a minor problem with its Kimi-K3 service, where users sending queries could get back empty or malformed answers, sometimes made up of repeated characters. The company opened the incident on 2026-07-29 at 17:56 UTC and described the symptoms in an update at 21:41 UTC while its engineers looked into it. DigitalOcean did not name a cause. It said the issue was resolved on 2026-07-30 at 06:15 UTC and asked anyone still seeing problems to contact its Support team.
Affected
Model Services
Timeline
- Started — 2026-07-29 17:56 UTC
- Investigating — 2026-07-29 17:56 UTC (2 updates)
- Resolved — 2026-07-30 06:15 UTC · 12h 19m 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