Limited access to Deepseek V4 Pro model

highDigitalOceanJul 4, 2026 22:13Duration: 2h 40m
networkcomputeapiauthentication
Network / RoutingCapacity IssueAuthentication IssueAPI Issue

Summary

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.

Impact

major

Timeline

Jul 4, 2026 22:13

[investigating] 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.

via statuspage
+1h 4m
Jul 4, 2026 23:18

[monitoring] 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.

via statuspage
+1h 35m
Jul 5, 2026 00:53

[resolved] 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.

via statuspage

Lessons Learned

DigitalOcean has experienced 94 incidents in the past year. This frequency suggests systemic reliability challenges that may warrant additional monitoring.

📊Incidents related to network, compute, api, authentication have occurred 953 times across all providers in the past year. This is one of the most common failure categories in cloud infrastructure.

💡This incident is categorized as: Network / Routing, Capacity Issue, Authentication Issue, API Issue. Consider implementing preventive measures specific to this failure category.