❌

Reading view

Kubernetes Deployments in NYC1

Jul 11, 01:27 UTC
Resolved - The issue affecting Kubernetes deployments in the NYC1 region has been resolved. Our investigation found intermittent DNS timeouts affecting a small number of DOKS clusters, with affected worker nodes running on shared-CPU Droplets. This is a documented limitation for latency-sensitive cluster DNS workloads such as CoreDNS.

The affected clusters are currently functional. To reduce the risk of recurrence, we recommend running CoreDNS on non-shared/dedicated CPU node pools and using sufficient CoreDNS replicas.

If you continue to see DNS failures or NodeNotReady events, please open a support ticket so we can investigate that cluster specifically.

Jul 10, 01:18 UTC
Monitoring - The issue affecting Kubernetes deployments in NYC1 has subsided. Workloads should now be functioning normally.

Our Engineering team is continuing to monitor the affected systems to confirm full resolution. We'll update this page if any further action is needed. We apologize for the inconvenience this may have caused.

Jul 9, 20:31 UTC
Investigating - Our Engineering team is investigating an issue affecting Kubernetes deployments in NYC1. Users may see intermittent DNS failures and NodeNotReady events from application workloads during this time.

We apologize for the inconvenience, we'll share new information on this page as soon as it is available.

  •  

Drupal 11.4 performance: expectation vs reality

Now that we talked through a few deployment day issues, I interested in hearing feedback from folks that have completed the upgrade to Drupal 11.4. The release notes generate a lot of excitement around the performance improvements for cold start cache scenarios: https://www.drupal.org/blog/drupal-11-4-0

I'm hopeful that this excitement is paired with real-world performance differences.

Has anyone experienced or measured greater performance after deploying 11.4 out?

submitted by /u/cosmicdreams
[link] [comments]
  •  

Disappearing frontpage articles

I'm creating a Drupal page for the first time and it is only showing one article at a time on the frontpage. I have 3 articles "written" so far. Tried a lot of troubleshooting already, all 3 are being promoted to frontpage, the preview shows that they are "showing," there are no filters interfering, and cache has been cleared. When I once did get them to all show, the images and titles are showing, but the article text is missing. All 3 are published. Using Drupal 11's 7/3 updated version with Olivero theme. Thanks in advance.

submitted by /u/BlueSky2028
[link] [comments]
  •  

Limited access to Deepseek V4 Pro model

Jul 5, 00:53 UTC
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.

Jul 4, 23:18 UTC
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.

Jul 4, 22:13 UTC
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.

  •  

Droplet Actions in NYC3

Jul 4, 15:10 UTC
Resolved - Our Engineering team has confirmed that the issue impacting Droplets in the NYC3 region has been fully resolved. Users can now perform actions on their Droplets or create new Droplets in this region without any issues.

We appreciate your patience while we worked to resolve this issue. If you continue to experience any problems, please open a support ticket from your account so our team can investigate further.

Jul 4, 14:42 UTC
Monitoring - Our Engineering team has implemented a fix to address the issue affecting Droplets in the NYC3 region. The issue, which began at 12:38 UTC, caused disruptions to customers attempting to perform actions on their Droplets in the NYC3 region.

During this time, customers may also have experienced errors when trying to create Droplets in this region.

We are actively monitoring the situation to ensure the fix remains effective and will provide another update once the issue has been fully resolved.

  •  

NYC2 Network Maintenance

Jul 7, 15:30 UTC
Completed - The scheduled maintenance has been completed.

Jul 7, 10:30 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.

Jul 4, 09:05 UTC
Scheduled - Start: 2026-07-07 10:30 UTC
End: 2026-07-07 15:30 UTC

During the above maintenance window, our Networking Engineering team will be making changes to the core networking infrastructure on Baremetal GPU to enhance performance and scalability in the NYC2 region.

Expected impact:

We do not expect any customer impact during this maintenance. However, if any unexpected issues arise, our team will continuously monitor the situation and take appropriate corrective actions, including rolling back the change if necessary to restore service stability. We will make every effort to minimize any impact.

If you have any questions related to the maintenance, please don’t hesitate to reach out to us through https://cloudsupport.digitalocean.com/s/createticket

  •  

Managed Database Clusters

Jul 3, 08:20 UTC
Resolved - Our engineering team has resolved the issue with Managed Database Clusters. All database systems should now be operating normally. If you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience.

Jul 3, 06:08 UTC
Monitoring - Our engineering team has implemented a fix to resolve the issue with Managed Database Clusters and is monitoring the situation. We will post an update as soon as the issue is fully resolved.

Jul 3, 02:28 UTC
Update - Our engineering team is still investigating the issue affecting Managed Database Clusters. Users may still encounter delays creating/scaling/forking/restoring the aforementioned Managed Database Clusters.

We are working to resolve this as soon as possible. we apologize for the inconvenience. We will post an update here once we have more information.

Jul 2, 22:04 UTC
Investigating - Our engineering team is investigating an issue affecting Managed Database Clusters. Currently, users may encounter delays when creating/scaling/forking and restoring Standard MySQL, Standard PostgreSQL, OpenSearch, Kafka, and Valkey clusters through the Cloud Control Panel or API.

We apologize for the inconvenience and will provide further updates as soon as more information is available.

  •  

Upgrade from 11.3.x to 11.4.0 results in a 500 error

So I did a standard composer upgrade.

sudo -u www-data /usr/bin/php8.4 /usr/local/bin/composer update "drupal/*" --with-all-dependencies

and all went well.
Then I opened my browser at example.com/update.php and got a 500.

AH01071: Got error 'PHP message: PHP Warning: require_once(autoload_runtime.php): Failed to open stream: No such file or directory in /var/www/website.com/web/update.php on line 13; PHP message: PHP Fatal error: Uncaught Error: Failed opening required 'autoload_runtime.php' (include_path='.:/usr/share/php') in /var/www/website.com/web/update.php:13\nStack trace:\n#0 {main}\n thrown in /var/www/website.com/web/update.php on line 13'

So in the update.php and the index.php I had to change this bit:

// require_once 'autoload_runtime.php';
require_once __DIR__ . '/../vendor/autoload_runtime.php';

What's wrong on my system? I can't imagine this should need to be done?

submitted by /u/Chris8080
[link] [comments]
  •  
❌