As a tech journalist in Bengaluru, I spent much of the early 2010s writing about Indian startups raising money from Silicon Valley investors. Every other month, I would find myself...
May 15, 02:00 UTC Resolved - As of the current time, our Engineering team has confirmed that the issue with Serverless Inference has been resolved. The root cause of the issue was an outage with our provider, Anthropic, which affected users of Sonnet 4.6 and Opus 4.7 models. According to Anthropic's status page (https://status.claude.com/incidents/8z7l5zcy0v3b), they have resolved the outage. If you continue to experience problems, please open a ticket with our Support team. We apologize for any inconvenience this may have caused.
May 15, 01:23 UTC Identified - According to Anthropic's status page (https://status.claude.com/incidents/8z7l5zcy0v3b), they have identified the root cause and are actively working on a fix. At this time, users may continue to experience errors when attempting to use Sonnet 4.6 and Opus 4.7 models. We will provide another update once Anthropic has implemented a fix and service is restored.
May 15, 01:21 UTC Monitoring - As of the current time, our Engineering team is aware of an ongoing incident with our provider, Anthropic, that is impacting Serverless Inference. The outage is affecting all users attempting to use Sonnet 4.6 and Opus 4.7 models. According to Anthropic's status page (https://status.claude.com/incidents/8z7l5zcy0v3b), they are currently experiencing an outage that is causing this disruption. We apologize for the inconvenience and will provide updates as more information becomes available.
May 14, 20:46 UTC Resolved - As of 19:50 UTC, the issue affecting the DNS service has been fully resolved, and all related services, including Let's Encrypt certificate issuance and Managed MongoDB provisioning, are now operating normally.
The backlog of delayed requests has been successfully processed, and all DNS record updates, pending certificate, and MongoDB operations should now be complete.
We apologize for the disruption this caused and appreciate your patience while our team worked to restore full functionality.
However, if you continue to experience any issues, please don't hesitate to raise a support ticket for further investigation. We'll be happy to assist you.
May 14, 16:42 UTC Monitoring - Our Engineering team has implemented a fix for the issue affecting our DNS service and are now seeing DNS record updates successfully propagate to the edge.
As a result, Let's Encrypt certificate issuance and Managed MongoDB provisioning (including scaling operations) should resume. We are currently monitoring the systems as they process the backlog of delayed requests. Affected MongoDB clusters and certificate requests should complete their provisioning automatically.
We will continue to monitor the situation closely to ensure full stability. We appreciate your patience throughout this process and will provide an update once the issue is fully confirmed as resolved.
May 14, 15:52 UTC Update - Our engineering team continues to investigate an issue affecting our DNS service. At this time, DNS resolution remains functional; however, new changes to DNS records are currently not being reflected at the edge.
This issue is also impacting related services. Specifically, customers may be unable to create new Let's Encrypt certificates. Regarding Managed MongoDB, customers will be able to submit requests to create new clusters or scale existing ones, but the completion of the provisioning process is currently delayed. This is due to the dependency on Let's Encrypt certificate issuance, which requires functional DNS propagation.
Affected clusters will automatically recover and complete their provisioning once the DNS issue is resolved. Our engineering team is actively working to restore full functionality across all affected services.
We apologize for the inconvenience and will share more information as it becomes available.
May 14, 13:57 UTC Investigating - Our Engineering team is investigating an issue affecting our DNS service. At this time, DNS resolution remains functional but any changes to DNS records are not being reflected at the edge. Additionally, customers may be unable to create new Let's Encrypt certificates at this time. Our engineering team is actively working to identify the root cause and restore full functionality.
We apologize for any inconvenience, and we'll share more information as it becomes available.
Governments around the world are rushing to regulate children’s access to social media. From Australia’s social media ban for minors to growing concerns around artificial intelligence, predators, privacy, and screen...
I made a small starter kit for using Drupal without putting Drupal in production.
The idea is simple.
Run Drupal locally with DDEV. Use it as the CMS. Astro fetches the content at build time through JSON:API and Linkset. Then you deploy the static output.
No hosted Drupal. No production database. No PHP runtime on the public site.
This is not meant to replace every Drupal site. It is for the cases where the public site does not need to be dynamic, but the content editing model still benefits from Drupal.
It is early, but the basic path is there: clone, setup, edit content locally, build static files, deploy dist/.
If you try it and the first run breaks, I’d want to know where.
May 16, 05:07 UTC Completed - The scheduled maintenance currently in progress has encountered unexpected roadblocks. As a result, we have made the decision to pause the maintenance at this time.
We will provide a further update with a specific time and date for the resumption and expected completion as soon as those details are finalized.
We apologize for any inconvenience and thank you for your understanding.
If you have questions or concerns about this maintenance, please reach out to us by opening up a ticket on your account.
May 15, 06:06 UTC Update - Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 14, 20:06 UTC In progress - Phase 1 maintenance is complete. Phase 2 is scheduled to begin on the 15th of May 2026 (Friday) at 04:30 UTC.
May 14, 20:05 UTC Scheduled - Phase 1 maintenance is complete. Phase 2 is scheduled to begin on the 15th of May 2026 (Friday) at 04:30 UTC.
May 14, 04:30 UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 13, 21:02 UTC Scheduled - Phase 1 Start: 2026-05-14 04:30 UTC Phase 1 End: 2026-05-14 17:30 UTC
Phase 2 Start: 2026-05-15 04:30 UTC Phase 2 End: 2026-05-15 17:30 UTC
During the above windows, our Engineering team will be performing upgrades to Functions backend infrastructure in the SYD1 region.
Expected Impact:
We anticipate some potential service disruptions during these maintenance windows. Function invocations may experience brief periods of elevated error rates or timeouts during node pool recycling in each region, and Apps that are configured with DBaaS Trusted Sources may see Trusted Source connectivity failures until DBaaS firewall rules are refreshed post-upgrade. We do not anticipate any impact to other non-Function components.
If you have any questions related to this event, please send us a ticket from your cloud support page. https://cloudsupport.digitalocean.com/s/createticket
U.S. President Donald Trump and Chinese President Xi Jinping are scheduled to meet in Beijing this week amid the urgent geopolitical tensions surrounding the war in Iran and the status...
I recently released a module called the AI Schema.org JSON-LD module, which I built with AI in 4 days. It replaces a key part of my Schema.org Blueprints module that I worked on for 4 years. AI ate my work, and I need to be okay with that.
May 12, 11:37 UTC Resolved - The remediation for the issue affecting the GradientAI Agent Platform Playground has been fully implemented, and the service is operating normally. We are no longer observing customer impact related to this issue, and the incident has been resolved.
May 12, 11:36 UTC Monitoring - We have applied a fix for the issue affecting the GradientAI Agent Platform Playground and are monitoring the service to ensure continued stability. At this time, we are no longer observing new reports related to this issue.
May 12, 11:14 UTC Update - A fix has been applied for the issue affecting the GradientAI Agent Platform Playground, and we are observing recovery in service behavior.
May 12, 10:50 UTC Identified - We have identified the cause of the issue affecting the GradientAI Agent Platform Playground. Our engineering team is implementing a fix, and we will provide another update as soon as it is available.
May 12, 10:24 UTC Investigating - We are currently investigating an issue affecting the GradientAI Agent Platform Playground. Users may see a “Something went wrong” error for all agent interactions in the Playground. Agent functionality through API endpoints remains unaffected. We are actively working to identify the cause and will provide an update as soon as more information is available.
In recent years, there have been several reminders of how interconnected the global economy is, and how fragile supply chains are. The shutdowns during the Covid-19 pandemic led to big...
Hi, Drupal Developer here with 10+ years of remote experience with Drupal 7-10.
I am now currently working for a full-time remote position; but every application on LinkedIn/Indeed yields no results, not even a mail from recruiter.
So, the question is, which sites are most popular for Drupal positions? Or what approach can I use to land a job with Drupal?
Last fall, I moved into Mark Zuckerberg’s old house. A pale blue ranch home dubbed the Facebook House, it was perched in the hills of Los Altos, an affluent enclave...
Drupal CMS 2.1.0-beta includes a new site template, Haven, with a warm and bright design and features aimed at non-profit websites.
This release should be used for testing only and is not suitable for building websites. There is no update path for Drupal CMS.
It may be a glorious journey to upgrade from the current Drupal CMS 1.1.0 but I don't feel that adventurous.
Right now I just want to make sure I don't fall behind on security updates with all installed modules whether they are part of the Drupal CMS 1.x recipes even if I don't upgrade to 2.x.x.
If Drupal CMS 1.x is locked to particular versions of Drupal Core does that mean it will be eventually insecure and have to be abandoned, unless it offers the ability transfer the content to Drupal 2.x?
In a couple of weeks I’ll be trying to get my backend specialist certification. However I don’t feel like I’ve grasped the concepts of Core API and especially caching that well… so I would like to ask for tips and tricks for getting better at them.
Also, how did you experience the exam? What kind of questions did they ask?
Hi! I am a full stack developer -- MERN, Django specializing in backend, I have seen many people using platforms like wordpress, shopify, drupal, flutter to make websites rather than coding everything from scratch.
I genuinely have no experience with these apps and want to explore these things.
I learned PHP and how it works recently to understand drupal but I am not finding any good resource to learn drupal, can any gentlemen or woman help me with their knowledge from where I can learn about Drupal architecture?
Login
DigitalOcean Status - Incident History
Drupal - Open Source Content Platform | #Celebr8D8
