Changes / DigitalOcean / DeepSeek V4 Pro is returning HTTP 429 "Rate limit exceeded"

DigitalOcean: Major incident: DeepSeek V4 Pro is returning HTTP 429 "Rate limit exceeded"

Summary

DigitalOcean reported a major outage affecting Gradient AI DeepSeek V4 Pro, which returned HTTP 429 "Rate limit exceeded" errors in Agentic Inference Cloud - Model Services and Model Services. It started at 2026-06-11 14:24 UTC and was resolved at 2026-06-11 17:42 UTC, lasting 3 h 17 min; DigitalOcean identified the issue and implemented a fix without specifying details.

Machine-written from the diff below (Sol; type: incident outage). Check the diff before relying on it.

Major incidentLabel: outage (model (Jev), 85%)Changed Detected Source: stspg.io

What changed

AddedTitle#1
Before: not present
After: DeepSeek V4 Pro is returning HTTP 429 "Rate limit exceeded"
AddedImpact#2
Before: not present
After: major
AddedStatus#3
Before: not present
After: resolved
AddedStart time#4
Before: not present
After: 2026-06-11 14:24 UTC
AddedResolved time#5
Before: not present
After: 2026-06-11 17:42 UTC
AddedAffected components#6
Before: not present
After: Agentic Inference Cloud - Model Services, Model Services
AddedUpdateinvestigating#7
Before: not present
After: We are currently facing issues with Gradient AI DeepSeek V4 Pro is returning HTTP 429 "Rate limit exceeded"
AddedUpdateinvestigating#8
Before: not present
After: We are continuing to investigate this issue.
AddedUpdateidentified#9
Before: not present
After: The issue has been identified and a fix is being implemented.
AddedUpdateresolved#10
Before: not present
After: This incident has been resolved.

First version of this incident archived by Rewindex. View the live incident.

History of this incident

When (UTC)ChangeKind
Major incident: DeepSeek V4 Pro is returning HTTP 429 "Rate limit exceeded" (this change)
DigitalOcean reported a major outage affecting Gradient AI DeepSeek V4 Pro, which returned HTTP 429 "Rate limit exceeded" errors in Agentic Inference Cloud - Model Services and Model Services. It started at 2026-06-11 14:24 UTC and was resolved at 2026-06-11 17:42 UTC, lasting 3 h 17 min; DigitalOcean identified the issue and implemented a fix without specifying details.
Major incident

All DigitalOcean changes → · DigitalOcean profile · Markdown · JSON