Limited access to Deepseek V4 Pro model
Jul 4, 22:13 UTCJul 5, 00:53 UTC
Duration
2h 40m
Impact
Major
Root cause
Not disclosed
DigitalOcean, 90 days
12 incidents
Affected
InferenceModel ServicesAgentic Inference Cloud - InferenceAgentic Inference Cloud - Model Services
Final update
Our Engineering team has confirmed that the issue with the Deepseek V4 Pro model in Serverless Inference and Agent Platform has been fully resolved. The model is now operational, and users should be able to use it without experiencing any errors. If you continue to experience any problems, please open a ticket with our Support team. We apologize for any inconvenience this may have caused and appreciate your patience.
Timeline
- Resolved · Jul 5, 00:53 UTC
Our Engineering team has confirmed that the issue with the Deepseek V4 Pro model in Serverless Inference and Agent Platform has been fully resolved. The model is now operational, and users should be able to use it without experiencing any errors. If you continue to experience any problems, please open a ticket with our Support team. We apologize for any inconvenience this may have caused and appreciate your patience.
- Monitoring · Jul 4, 23:18 UTC
Our Engineering team has implemented a fix for the issue with the Deepseek V4 Pro model in Serverless Inference and Agent Platform. The model should now be operational, and users should no longer receive error 429 messages when attempting to use it. We are currently monitoring the situation to ensure the fix is successful and the model is functioning as expected. We will post an update if any further issues arise. If you continue to experience problems, please open a ticket with our Support team. We apologize for any inconvenience this may have caused.
- Investigating · Jul 4, 22:13 UTC
Our Engineering team is investigating reports of an incident affecting the Deepseek V4 Pro model in Serverless Inference and Agent Platform. Users may experience errors when attempting to use this model, specifically receiving error 429 messages. We apologize for the inconvenience and are working to resolve the issue as soon as possible. We will provide an update once we have more information.
More from DigitalOcean
Full historyKubernetes Cluster Management Operationslasted 3h 40mApp Platform Deploymentslasted 0mDNS Resolution for Managed Kuberneteslasted 1h 27mVPC Networking Availabilitylasted 1h 35mA Network Disruption in BLR1 Region Impacted Multiple Products (Resolved)lasted 0mSupport Portal Service Disruptionlasted 11h 21m