May 20, 05:13 UTC
Resolved - From 00:00 UTC to 01:40 UTC, users may have experienced degraded write performance and intermittent impacts to workloads dependent on Block Storage Volumes in the NYC3 region.

Our Engineering team has confirmed that the underlying infrastructure issue affecting Block Storage Volumes at the storage layer 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.

May 20, 02:19 UTC
Monitoring - Our Engineering team has implemented mitigation measures for the infrastructure issue affecting Block Storage Volumes in the NYC3 region. The team is monitoring the situation, and we will share another update once the issue is fully resolved

May 20, 01:05 UTC
Investigating - Our Engineering team is currently investigating an ongoing infrastructure issue in the NYC3 region affecting Block Storage Volumes at the storage layer. Users may experience degraded write performance and intermittent impact to services dependent on the affected storage infrastructure.

We apologize for the inconvenience and will continue to provide updates as more information becomes available.

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

When Donald Trump arrived in Beijing last week for his first state visit to China since 2017, he was joined by the CEOs of Tesla, Apple, Nvidia, Micron, Qualcomm, and...

© Getty Images/Rest of World

In the spring of 2025, the CEO of a European childcare startup posted a brief write-up about the qualities of a good leader on their LinkedIn page. Dozens of executives...

© iStock/Rest of World

May 19, 17:30 UTC
Completed - The scheduled maintenance has been completed.

May 19, 14:30 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.

May 17, 14:35 UTC
Scheduled - Start: 2026-05-19 14:30 UTC
End: 2026-05-19 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

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

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

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

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

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...

© iStock/Rest of World

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...

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

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