Normal view

DNS Resolution for .co TLD

Apr 18, 14:10 UTC
Resolved - Our Engineering team has confirmed that the issue affecting the DNS resolution of .co top-level domain (TLD) has been resolved. The DNS resolution for .co domains is now working as expected.

We apologize for the inconvenience. If you continue to face any issues, please open a support ticket from within your account.

Apr 17, 22:53 UTC
Monitoring - Our Engineering team has implemented a fix to resolve the issue that was affecting the DNS resolution of .co top-level domain (TLD).

During this time, users who are using DigitalOcean DNS resolvers in their resources should no longer experience issues related to the DNS resolution.

Our Engineers are currently monitoring the situation. We will post an update as soon as the issue is fully resolved.

Apr 17, 21:22 UTC
Identified - Our Engineering team is aware of a widespread, external issue affecting .co top-level domain (TLD). While this incident originates outside of DigitalOcean's infrastructure, you may experience errors when querying a .co domain, regardless of the DNS resolver being used.

Our Engineers are actively deploying temporary backend mitigations to help minimize the impact on our customers. We will continue to monitor the situation closely and post updates as more information becomes available.

Spaces availability in NYC3

Apr 17, 18:27 UTC
Resolved - From 17:22 to 17:46 UTC, our Engineering team observed an issue impacting Spaces availability in the NYC3 region. During this time, customers may have encountered 500 errors and degraded performance while accessing Spaces buckets. The issue has now been fully resolved. If you continue to experience problems, please open a ticket with our support team from within your Cloud Control Panel. We apologize for any inconvenience caused.

Bangladesh’s gig workers are stuck in gas lines as Iran-U.S. war strains fuel supply

17 April 2026 at 08:40
On a recent Saturday evening, a line of motorcycles stretched from a gas station in Dhaka. The queue snaked along the road for kilometers, its end out of sight. In...

© Sony Ramani/NurPhoto/Getty Images

Motorcycles and private cars line up for hours at a filling station in the Tejgaon Trust area of Dhaka, Bangladesh, on [Month Day, Year], as motorists attempt to purchase limited fuel supplies. Despite government assurances of a stable supply, many fuel stations remain closed for extended periods due to insufficient deliveries from depots, resulting in long queues and public inconvenience. (Photo by Sony Ramani/NurPhoto via Getty Images)

The Mexican security company with a $1.27 billion surveillance empire

16 April 2026 at 05:00
This article was adapted from our latest investigation, produced in partnership with Type Investigations: A Mexican surveillance giant you’ve never heard of is now watching the U.S. border. Grupo Seguritech...

© Adriana Zehbrauskas for Rest of World

Ciudad Juarez, Chihuahua, Mexico, October 8, 2025:
Staff monitor screens at the C7 command center for the Department of Public Security for the state of Chihuahua in Ciudad Juarez on Wednesday, October 14, 2025. Photo by Adriana Zehbrauskas for Rest of World

Does Drupal feel complex because it is… or because we don’t use it often enough?

Every time I come back to a Drupal project after working on other stacks,
there’s a short phase where everything feels… heavier than expected.

not necessarily bad just different:

• configuration layers
• content types + fields + views
• hooks / services / structure

but after spending some time with it, things start to click again and the flexibility becomes clear.

it made me wonder

is Drupal actually complex by nature,
or does it just feel that way because you need to stay “in its ecosystem” consistently to be comfortable with it?

especially compared to tools where you can jump in quickly after a break.

curious how others feel
does Drupal complexity go away with regular use,
or is it just part of the system regardless?

submitted by /u/OliverPitts
[link] [comments]

Wrote a full Drupal to headless CMS migration guide (content mapping, TypeScript scripts, checklist)

Drupal 7 EOL hit in January and I've seen a lot of teams scrambling. Put together a step-by-step guide covering:

- Content type and node mapping
- Field migration with TypeScript
- Media and file handling
- Taxonomy migration
- Go-live checklist

Hope it helps someone: cosmicjs.com/blog/migrate-from-drupal-to-cosmic

submitted by /u/tonyspiro
[link] [comments]

Serverless Inference

Apr 15, 02:56 UTC
Resolved - From 23:20 UTC to 02:00 UTC, users may have experienced elevated error rates due to service instability, which resulted in intermittent HTTP 500 errors and terminated connections.

Our Engineering team has confirmed full resolution of the issue, and all systems are now operating normally.

If you continue to experience any issues, please open a ticket with our support team. We apologize for any inconvenience caused.

Apr 15, 02:24 UTC
Monitoring - Our Engineering team has implemented a fix for the issue causing elevated error rates due to service instability. We are currently monitoring the situation to ensure stability and confirm that error rates, including HTTP 500 responses, have returned to normal levels.

We will provide a further update once we confirm the issue is fully resolved.

Apr 15, 01:07 UTC
Investigating - Our Engineering team is investigating an issue causing elevated error rates due to service instability and terminating open connections which causes some 500s. Some requests may fail while we work to resolve it.

We apologize for the inconvenience and will share an update once we have more information.

App Platform Deployments

Apr 14, 17:57 UTC
Resolved - From 16:07 to 16:50 UTC, Our Engineering team observed an issue with App Platform Deployments in all regions. During this time, App deployments of both new and existing apps would have been affected. Our team has fully resolved the issues as of 16:50 UTC. All new and existing App deployments should now be functioning as expected. If you continue to experience problems, please open a ticket with our support team from within your Cloud Control Panel. We apologize for any inconvenience caused.

Managed Database Resizes

Apr 14, 15:19 UTC
Resolved - Our Engineering team has resolved the issue with resize operations for Managed Databases and should now be operating normally. If you continue to experience problems, please open a ticket with our support team from within your Cloud Control Panel. We apologize for any inconvenience.

Apr 14, 14:30 UTC
Monitoring - Our Engineering team has taken action to mitigate the issue with resize operations for Managed Databases and implemented a fix . We are monitoring the situation and will post an update as soon as we confirm that the issue is fully resolved.

Apr 14, 12:53 UTC
Investigating - Our engineering team is investigating an issue impacting resize operations for Managed Databases. During this time, users may experience error when attempting to resize Managed Database via Cloud Control Panel and API in all regions. We apologize for the inconvenience and will share an update once we have more information.

Core Infrastructure Maintenance in All Regions 2026-04-16 09:00 UTC

Apr 22, 18:31 UTC
Completed - The scheduled maintenance has been completed.

Apr 22, 09:07 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.

Apr 21, 22:15 UTC
Scheduled - Phase 3 maintenance is complete. Phase 4 is scheduled to begin on the 22nd of April 2026 (Wednesday) at 09:00 UTC.

Apr 21, 09:07 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.

Apr 20, 15:22 UTC
Scheduled - Phase 2 maintenance is complete. Phase 3 is scheduled to begin on the 21st of April 2026 (Tuesday) at 09:00 UTC.

Apr 20, 09:25 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.

Apr 16, 15:05 UTC
Scheduled - Phase 1 maintenance is complete. Phase 2 is scheduled to begin on the 20th of April 2026 (Monday) at 09:00 UTC.

Apr 16, 09:10 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.

Apr 14, 09:37 UTC
Scheduled - Hello,

During the above window, our Engineering team will be performing maintenance on core control plane infrastructure across all regions. Please note that the existing infrastructure will continue running without issue.

This maintenance will be carried out in four phases as outlined below:

16 April 2026 (Thursday), 09:00–15:00 UTC
20 April 2026 (Monday), 09:00–15:00 UTC
21 April 2026 (Tuesday), 09:00–22:00 UTC
22 April 2026 (Wednesday), 09:00–22:00 UTC

Expected Impact:

We do not anticipate any impact, however, there is a small possibility that Control Panel functionality specifically CRUD (Create, Read, Update, Delete) operations may be affected during the maintenance window. All running workloads are expected to continue operating normally without interruption.

Our team will be actively monitoring the environment throughout the maintenance, and any unexpected events will be promptly communicated through our status page.

If you have any questions or concerns regarding this maintenance, please feel free to open a support ticket from https://cloudsupport.digitalocean.com/s/createticket. We’re here to help.

Thank you,

Team DigitalOcean

Suddenly can't edit Text - "Your site doesn’t include support for the "core/group" block."

Hey guys,

somehow my content looks kind of weird since a few days. The gaps between the text got less and I can't edit the text directly in the cms.

I get this error "Your site doesn’t include support for the "core/group" block. You can leave this block intact, convert its content to a Custom HTML block, or remove it entirely."

In the system tab it says that there are updates available. The problem is I'm an SEO and my client thinks I've breaked the page even though all I did, was changing the CMS content. (Text and Internal Links)

Could this have been caused by me? Or is this a deeper problem.

submitted by /u/lukaszadam_com
[link] [comments]
❌