© Rest of World/iStock
© Rest of World/iStock
Jun 17, 18:00 UTC
Completed - The scheduled maintenance has been completed.
Jun 17, 09:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jun 17, 05:53 UTC
Scheduled - Core Infrastructure Maintenance
Start: 2025-06-17 09:00 UTC
End: 2025-06-17 18:00 UTC
During the above time, our Engineering Team will be performing maintenance to failover some internal databases from one cluster to another.
Existing infrastructure, including Droplets and Droplet-based services, should continue running without issue. There is no network disruption to existing services expected as part of this maintenance. However, there are dependencies on multiple services. During the failover, there may be customer impacts that should be brief and transitory.
Multiple teams will be engaged to keep downtime to a minimum and mitigate any impact that does occur. We’ll post updates here for any unexpected changes to this scheduled maintenance, as well as progress updates during the maintenance itself.
If you have any questions related to this issue please send us a ticket from your cloud support page. https://cloudsupport.digitalocean.com/s/createticket
Thank you,
Team DigitalOcean
Jun 17, 00:29 UTC
Resolved - The connectivity issues affecting our Serverless/GenAI Inference API have been fully resolved.
Our engineering teams successfully completed the connectivity restoration. All systems should be functioning normally, and the endpoint should be fully operational.
Jun 16, 23:29 UTC
Monitoring - Our engineering teams have successfully begun implementing mitigation steps to resolve the connectivity issues affecting the inference API. We will provide another update once the API has fully recovered and error rates return to normal.
Jun 16, 22:00 UTC
Investigating - We are actively investigating an issue causing elevated HTTP 500 error rates for customers utilizing our Serverless/GenAI Inference API.
Customer Impact: Customers making calls to the inference API—specifically targeting /v1/* endpoints—will experience intermittent HTTP 500 errors and failed requests.
Jun 18, 17:30 UTC
Completed - The scheduled maintenance has been completed.
Jun 18, 14:30 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jun 16, 14:32 UTC
Scheduled - Start: 2026-06-18 14:30 UTC
End: 2026-06-18 17:30 UTC
During the above window, our Networking team will be making changes to the core networking infrastructure to improve performance and scalability in the SGP1 region.
Expected impact:
We do not anticipate any downtime for Droplets or Droplet-related services, including Managed Databases, Load Balancers, App Platform, and Managed Kubernetes, as this maintenance has been carefully designed and tested to be seamless. In the unlikely event that an undetected misconfiguration occurs, a subset of customers could experience temporary network disruption. We will endeavor to keep this to a minimum for the duration of the change.
If you have any questions related to this issue, please send us a ticket from your cloud support page. https://cloudsupport.digitalocean.com/s/createticket
© Rest of World/iStock
If you ran into the
Your requirements could not be resolved to an installable set of packages.
error message while running composer update today, see this issue:
https://www.drupal.org/project/drupal/issues/3599842
In brief, quoting the the issue:
While these were fixed a few weeks ago (see https://github.com/advisories/GHSA-hq7v-mx3g-29hw), we can see the composer datasource was only registered with the vulnerabilities on June 11th.
and
You can temporarily fetch the 2.11.0 version of
guzzlehttp/psrand alias it to 2.8.1 with this:
composer require "guzzlehttp/psr7:2.11.0 as 2.8.1"
Revert this once a new Drupal core is released by deleting theguzzlehttp/psr7": "2.11.0 as 2.8.1",line in composer.json, and then updating Drupal core.
 | I kept running into the same thing on Drupal sites: the SEO basics (metatags, structured data, sitemap, clean URLs) were half-finished, and the generic online SEO checkers don't know anything about Drupal, so their advice is only half the solution. So I built a small free tool that scans any URL and, if it detects Drupal, adds Drupal-specific checks on top of the usual technical and content ones. It gives you a score per category and a plain-language list of what to fix. It's free, no sign-up! Works on any site, but it's sharpest on Drupal. Let me know your score! [link] [comments] |
hola, me gustaría imprimir bastantes fotos de los momentos más importantes para ponerlas en un álbum, para que no se me pierdan entre las miles de fotos de la nube, saben de algun lugar en dónde se pueda imprimir por volumen y tenga un precio razonable?
 | Built to deliver a modern, fast and conversion-focused shopping experience, Bootiq enhances every part of your online store: [link] [comments] |
Hola, soy de la ciudad y me ha tocado irme a chiriqui y tenía la duda de que tan difícil es conseguir una oportunidad laboral en chiriqui? Contemplando que no tenga una gran experiencia en trabajos o cosas por el estilo? Cuál sería la mejor opción para conseguir algún trabajo "rápido" ?
Hi everyone,
I have an upcoming technical interview for a Drupal-focused full-stack role, and I would appreciate some guidance from experienced Drupal developers.
From my conversation with the interviewer, I expect the interview to involve reviewing existing code, tracing complete workflows, identifying production issues, and explaining improvements. The organization is also planning work around upgrading from Drupal 10 to Drupal 11.
The areas I believe may be covered include:
My background is stronger in general software engineering than in PHP and Drupal. I have been using AI-assisted exercises and small Drupal code-review challenges to prepare, but I want to make sure I am learning the right concepts and not developing an unrealistic understanding of production Drupal work.
For someone interviewing at roughly the three-year experience level:
Any practical examples, learning resources, or advice about what to prioritize would be greatly appreciated. Thank you!
Login
![[link]](https://i.redd.it/2rwhg4k7na7h1.jpeg){kind=link}