Response Degradation Impacting Kimi-K3
Update - 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.
Jul 29, 2026 - 21:41 UTC
Investigating - We are currently investigating this issue.
Jul 29, 2026 - 17:56 UTC
API Operational
Billing Operational
BYOIP Operational
Cloud Control Panel Operational
Cloud Firewall Operational
Community Operational
DNS Operational
Support Center Operational
Reserved IP Operational
WWW Operational
Agentic Inference Cloud Degraded Performance
Agent Runtime Operational
Inference Operational
ADK Operational
Knowledge Bases Operational
Guardrails Operational
Model Services Degraded Performance
App Platform Operational
Global Operational
Amsterdam Operational
Atlanta Operational
Bangalore Operational
Frankfurt Operational
Kansas Operational
London Operational
New York Operational
Richmond Operational
San Francisco Operational
Singapore Operational
Sydney Operational
Toronto Operational
Container Registry Operational
Global Operational
AMS3 Operational
BLR1 Operational
FRA1 Operational
NYC3 Operational
SFO2 Operational
SFO3 Operational
SGP1 Operational
SYD1 Operational
Droplets Operational
Global Operational
AMS2 Operational
AMS3 Operational
ATL1 Operational
BLR1 Operational
FRA1 Operational
LON1 Operational
MKC1 Operational
NYC1 Operational
NYC2 Operational
NYC3 Operational
RIC1 Operational
SFO1 Operational
SFO2 Operational
SFO3 Operational
SGP1 Operational
SYD1 Operational
TOR1 Operational
Event Processing Operational
Global Operational
AMS2 Operational
AMS3 Operational
ATL1 Operational
BLR1 Operational
FRA1 Operational
LON1 Operational
MKC1 Operational
NYC1 Operational
NYC2 Operational
NYC3 Operational
RIC1 Operational
SFO1 Operational
SFO2 Operational
SFO3 Operational
SGP1 Operational
SYD1 Operational
TOR1 Operational
Functions Operational
Global Operational
AMS3 Operational
BLR1 Operational
FRA1 Operational
LON1 Operational
MKC1 Operational
NYC1 Operational
SFO3 Operational
SGP1 Operational
SYD1 Operational
TOR1 Operational
GPU Droplets Operational
Global Operational
ATL1 Operational
MKC1 Operational
NYC2 Operational
RIC1 Operational
TOR1 Operational
Managed Databases Operational
Global Operational
AMS3 Operational
ATL1 Operational
BLR1 Operational
FRA1 Operational
LON1 Operational
MKC1 Operational
NYC1 Operational
NYC2 Operational
NYC3 Operational
SFO2 Operational
SFO3 Operational
SGP1 Operational
SYD1 Operational
TOR1 Operational
Monitoring Operational
Global Operational
AMS2 Operational
AMS3 Operational
ATL1 Operational
BLR1 Operational
FRA1 Operational
LON1 Operational
MKC1 Operational
NYC1 Operational
NYC2 Operational
NYC3 Operational
RIC1 Operational
SGP1 Operational
SFO1 Operational
SFO2 Operational
SFO3 Operational
SYD1 Operational
TOR1 Operational
Networking Operational
Global Operational
AMS2 Operational
AMS3 Operational
ATL1 Operational
BLR1 Operational
FRA1 Operational
LON1 Operational
MKC1 Operational
NYC1 Operational
NYC2 Operational
NYC3 Operational
RIC1 Operational
SFO1 Operational
SFO2 Operational
SFO3 Operational
SGP1 Operational
SYD1 Operational
TOR1 Operational
Network File Storage Operational
ATL1 Operational
MKC1 Operational
RIC1 Operational
Kubernetes Operational
Global Operational
AMS3 Operational
ATL1 Operational
BLR1 Operational
FRA1 Operational
LON1 Operational
MKC1 Operational
NYC1 Operational
NYC3 Operational
RIC1 Operational
SFO2 Operational
SFO3 Operational
SGP1 Operational
SYD1 Operational
TOR1 Operational
Load Balancers Operational
Global Operational
AMS2 Operational
AMS3 Operational
ATL1 Operational
BLR1 Operational
FRA1 Operational
LON1 Operational
MKC1 Operational
NYC1 Operational
NYC2 Operational
NYC3 Operational
RIC1 Operational
SFO1 Operational
SFO2 Operational
SFO3 Operational
SGP1 Operational
SYD1 Operational
TOR1 Operational
Spaces Operational
Global Operational
AMS3 Operational
ATL1 Operational
BLR1 Operational
FRA1 Operational
MKC1 Operational
NYC3 Operational
RIC1 Operational
SFO2 Operational
SFO3 Operational
SGP1 Operational
SYD1 Operational
LON1 Operational
Spaces CDN Operational
Global Operational
AMS3 Operational
ATL1 Operational
FRA1 Operational
LON1 Operational
MKC1 Operational
NYC3 Operational
RIC1 Operational
SFO3 Operational
SGP1 Operational
SYD1 Operational
VPC Operational
Global Operational
AMS2 Operational
AMS3 Operational
ATL1 Operational
BLR1 Operational
FRA1 Operational
LON1 Operational
MKC1 Operational
NYC1 Operational
NYC2 Operational
NYC3 Operational
RIC1 Operational
SFO1 Operational
SFO2 Operational
SFO3 Operational
SGP1 Operational
SYD1 Operational
TOR1 Operational
Volumes Operational
Global Operational
AMS2 Operational
AMS3 Operational
ATL1 Operational
BLR1 Operational
FRA1 Operational
LON1 Operational
MKC1 Operational
NYC1 Operational
NYC2 Operational
NYC3 Operational
RIC1 Operational
SFO1 Operational
SFO2 Operational
SFO3 Operational
SGP1 Operational
SYD1 Operational
TOR1 Operational
CSPM Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance

Jul 29, 2026

Unresolved incident: Response Degradation Impacting Kimi-K3.

Jul 28, 2026

Agent Platform Requests Returning HTTP 500 Errors
Resolved - This incident has been resolved.
Jul 28, 15:24 UTC
Identified - The issue has been identified and a fix is being implemented.
Jul 27, 19:44 UTC
Investigating - We are currently investigating this issue.
Jul 27, 18:31 UTC

Jul 27, 2026

Jul 26, 2026

No incidents reported.

Jul 25, 2026

No incidents reported.

Jul 24, 2026

Network Connectivity from India to NYC
Resolved - Between 07:46  UTC & 10:24 UTC today, some users in India accessing resources in the NYC region may have experienced connectivity issues. The impact was limited to users using Airtel as their ISP.

Our investigation determined that the issue was caused by an internal network issue within Airtel and was not related to DigitalOcean network. The connectivity issue now appears to be resolved, and users should no longer experience problems accessing their resources.

We apologize for any inconvenience this may have caused. However, if you continue to experience any connectivity issues, please don't hesitate to open a support ticket for further investigation; we'll be happy to assist you further.
Jul 24, 12:42 UTC
Monitoring - We are observing improvements in network connectivity for users in India accessing resources in our NYC region. Our team is monitoring the situation to ensure that the service has returned to normal operation and remain stable. We appreciate your patience and will provide an update once the issue is fully confirmed as resolved.
Jul 24, 11:45 UTC
Identified - We have noticed ​​​​​​​network connectivity issues affecting some users connecting from India to resources in the NYC region. Based on our current investigation, users on Airtel and BSNL have reported increased latency, packet loss, or intermittent connectivity. We apologize for the inconvenience and will provide an update as soon as more information becomes available.
Jul 24, 10:36 UTC

Jul 23, 2026

Llama-4-Maverick Model Availability
Resolved - This incident has been resolved.
Jul 23, 12:37 UTC
Investigating - Our Engineering team is currently investigating an issue where the llama-4-maverick model is unavailable. Users may experience HTTP 500 errors while using this model with Serverless Inference.

We apologize for the inconvenience. Our Engineering team is working with high priority to resolve the issue. Thank you for your patience and understanding.
Jul 23, 11:16 UTC

Jul 22, 2026

Gradient AI Serverless Inference Requests Timing Out for qwen3.5-397b-a17b
Resolved - This incident has been resolved.
Jul 22, 19:42 UTC
Investigating - We are currently investigating this issue.
Jul 22, 16:50 UTC

Jul 21, 2026

No incidents reported.

Jul 20, 2026

No incidents reported.

Jul 19, 2026

Block Storage Volume NYC1, NYC3, SGP1, SYD1 and BLR1
Resolved - Our Engineering team has confirmed that the issue regarding volume attachment to Droplets in the NYC1, NYC3, SGP1, SYD1, and BLR1 regions has been fully resolved, and all services are now operating normally.

If you continue to experience any issues, please contact our Support team by opening a ticket. We apologize for any inconvenience caused.
Jul 19, 15:32 UTC
Monitoring - Our Engineering team has identified the root cause of the issue preventing volume attachments to Droplets in NYC1, NYC3, SGP1, SYD1, and BLR1 and has successfully implemented a fix. You should now be able to attach volumes to your Droplet(s) without encountering any further errors or issues.

We are actively monitoring the situation to ensure the fix remains effective and will provide another update once the issue has been fully resolved.
Jul 19, 14:52 UTC
Update - We are continuing to investigate this issue.
Jul 19, 13:36 UTC
Update - We are continuing to investigate this issue.
Jul 19, 13:34 UTC
Investigating - Our Engineering team is investigating an issue with attaching volume to the droplets in the NYC1, NYC3, SGP1, SYD1 and BLR1 regions. During this time you may experience an issue with attaching volume to the Droplet(s). We apologize for the inconvenience and will share an update once we have more information.
Jul 19, 09:51 UTC
Networking in BLR1
Resolved - Our engineering team has resolved the outbound network connectivity issue in the BLR1 region. If you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience.
Jul 19, 09:52 UTC
Monitoring - Our engineering team has implemented the necessary fixes affecting upstream network connectivity for Droplet-based services in the BLR1 region. Users should now be able to connect to the external endpoints from Droplets in BLR1.

We are currently monitoring the situation to ensure that the service has returned to normal operation and remain stable. We appreciate your patience and will provide an update once the issue is fully confirmed as resolved.
Jul 19, 09:31 UTC
Identified - Our Engineering team has identified an issue affecting upstream network connectivity for Droplet-based services in the BLR1 region and is actively working with the relevant upstream providers to implement a resolution.

Customers may continue to experience intermittent timeouts or connectivity issues when attempting to reach external endpoints from Droplets in BLR1.

We will provide another update once the issue has been fully resolved or when additional information becomes available.
Jul 19, 08:27 UTC
Investigating - We are currently investigating an issue affecting outbound network traffic for Droplets in the BLR1 region. Customers may experience timeout errors or connectivity issues when attempting to reach external services.
Our Engineering team is actively investigating the issue and working to identify the root cause. We will provide additional updates as soon as more information becomes available.
Jul 19, 06:57 UTC

Jul 18, 2026

No incidents reported.

Jul 17, 2026

No incidents reported.

Jul 16, 2026

Reserved IP routing in TOR1
Resolved - Our Engineering team has confirmed that the underlying issue affecting Reserved IP routing in the TOR1 region has been fully resolved, and services are now operating normally.

If you continue to experience any issues, please contact our Support team by opening a ticket. We apologize for any inconvenience caused.
Jul 16, 17:24 UTC
Monitoring - Our Engineering team has implemented a fix for the issue affecting Reserved IP routing in the TOR1 region, and we are currently monitoring the results.

Inbound and outbound traffic to and from Reserved IPs in TOR1 should now be restored. If you reassigned your Reserved IP as a workaround and are still experiencing issues, please reach out to our support team.

We will continue to monitor the situation closely and provide a further update once we have confirmed the issue is fully resolved.
Jul 16, 17:01 UTC
Identified - Our Engineering team has identified the cause of the issue affecting Reserved IP routing in the TOR1 region, which was causing inbound and outbound traffic to and from Reserved IPs in TOR1 to fail.

Detaching and reassigning the Reserved IP to the Droplet may restore connectivity in the meantime. We recommend trying this workaround if you are still experiencing issues with your Reserved IP in TOR1.

Our engineering team is now working on implementing a fix. We will provide updates as more information becomes available.
Jul 16, 15:30 UTC
Investigating - Our Engineering team is investigating an issue affecting Reserved IP routing in the TOR1 region. The issue is causing inbound and outbound traffic to and from Reserved IPs in TOR1 to fail.

In the meantime, detaching and reassigning the Reserved IP to the Droplet may restore connectivity. We recommend trying this workaround if you are experiencing issues with your Reserved IP in TOR1.

Our engineering team is actively investigating the root cause and working towards a resolution. We will provide updates as more information becomes available.
Jul 16, 13:39 UTC

Jul 15, 2026

Serverless Inference - Gemma4 Latency Issues Causing Timeouts & Slow Responses
Resolved - The deployed fix has successfully restored full functionality, and our monitoring shows that system performance has completely stabilized. Response times for all Gemma 4 inference workflows have returned to normal baseline levels.
We will continue to track platform stability moving forward to ensure long-term reliability. We apologize for any disruption this may have caused to your workflows and appreciate your patience throughout the recovery process.
Jul 15, 21:46 UTC
Monitoring - A fix has been deployed to resolve the issue. We are closely monitoring system performance to ensure full recovery and normal response times for all Gemma 4 inference workflows.
Jul 15, 10:06 UTC
Identified - We are currently experiencing an issue affecting customers using the Gemma 4 model on our Serverless Inference platform. Customers may experience significantly increased latency or request timeouts.

Our Engineering team has identified a backend configuration issue as the root cause, which is temporarily impacting model performance. Please be assured that our Engineering team is actively working on a fix and is treating this issue with high priority.

We sincerely apologise for any inconvenience this may have caused and appreciate your patience and understanding. If you have any further questions, please create a support ticket so that we can investigate your specific case further.
Jul 14, 11:07 UTC
Monitoring - A fix has been deployed to resolve the backend configuration issue. We are closely monitoring system performance to ensure full recovery and normal response times for all Gemma 4 inference workflows.
Jul 13, 22:24 UTC
Identified - We are currently experiencing an issue where customers using the Gemma 4 model on our Serverless Inference and Dedicated Inference platforms may experience severe latency or request timeouts.
Our engineering team has identified a backend configuration issue as the root cause, which is temporarily degrading performance. We are actively working on a fix to restore normal response times and will provide another update as soon as the mitigation is in place
Jul 13, 19:04 UTC
← Incident History Powered by Atlassian Statuspage