Minor impactResolvedCloud

DigitalOcean incident: Response Degradation Impacting Kimi-K3

DigitalOcean reported this minor-impact incident on its official status page on Jul 29, 2026, 17:56 UTC. It was resolved after 12h 19m.

Right now DigitalOcean is operational. Live DigitalOcean status →

🔔 Get alerted when DigitalOcean has issuesFree · email alerts · no credit card
Jul 29, 2026, 17:56 UTC
started
Jul 30, 2026, 06:15 UTC
resolved
12h 19m
duration
Minor
impact

Affected components

  • Model Services
  1. resolvedJul 30, 2026, 06:15 UTC

    Our Engineering team has resolved the issue causing empty or broken responses from Kimi-K3. If you continue to experience any problems, please open a ticket with our Support team. We apologize for any inconvenience this may have caused.

  2. investigatingJul 29, 2026, 21:41 UTC

    Our Engineering team is investigating reports of empty or broken responses impacting Kimi-K3. At this point, users may experience degraded response quality, specifically empty or broken outputs (including repeated characters), when querying the Kimi-K3 service. We apologize for the inconvenience and will share an update once we have more information.

  3. investigatingJul 29, 2026, 17:56 UTC

    We are currently investigating this issue.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in DigitalOcean's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

How often does DigitalOcean have incidents?

DigitalOcean reported 20 incidents in the last 90 days, 3 of them major or critical. A typical incident lasted 5h 35m. See DigitalOcean's uptime and incident history

DigitalOcean incident on Jul 29, 2026: Response Degradation Impacting Kimi-K3 · APIStatus.watch