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

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

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

© Getty Images / Rest of World

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. submitted by /u/jrockowitz [link] [comments]

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

© iStock/Rest of World

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

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

© Joanne Joo for Rest of World

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

submitted by /u/According-Shine-1035
[link] [comments]

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

May 9, 14:42 UTC
Resolved - Between 5:35 and 14:25 UTC today, our Engineering team identified an issue that prevents enabling Two-Factor Authentication (2FA) and Google/GitHub authentication through the Control Panel. During this period, users might have encountered issues while enabling authentication methods and accessing teams with secure sign-in enabled.

Our team has taken appropriate measures to address the issue. We can confirm that service has been restored and is now functioning normally.

We regret the inconvenience caused. However, if you continue to experience any issues, please create a support ticket for further analysis.

May 9, 13:51 UTC
Monitoring - Our Engineering team has implemented necessary changes to address the issue affecting the ability to enable Two-Factor Authentication (2FA) and Google/GitHub authentication through the Control Panel. Our team is currently monitoring the situation to ensure stability.

We appreciate your patience and will provide an update once the issue is fully confirmed as resolved.

May 9, 11:15 UTC
Investigating - Our Engineering team is investigating an issue affecting the ability to enable Two-Factor Authentication (2FA) and Google/GitHub authentication through the Control Panel. During this time, users may encounter errors while enabling these authentication methods and could also experience issues accessing teams with secure sign-in enabled.

We apologize for the inconvenience and will provide an update as soon as more information becomes available.

May 8, 21:54 UTC
Resolved - The upstream outage with Let's Encrypt has been resolved. Customers should now be able to issue Let's Encrypt certificates for Spaces, Load Balancers, and App Platform Custom Domains. Our Engineering team has also confirmed that stuck or delayed actions with Mongo, Advanced PG, and Advanced MySQL databases should complete normally now.

We appreciate your patience. If you continue to experience any issues, please open a support ticket from within your account.

May 8, 20:46 UTC
Identified - Our Engineering team is aware of an upstream outage with Let's Encrypt (see https://letsencrypt.status.io/) which impacts the following services:

- Inability to create new Let's Encrypt certificates for Spaces, Load Balancers, and App Platform Custom Domains
- Stuck or delayed creates/forks/restores on Mongo, PG, and MySQL databases.

Please note that operations related to Managed Databases and App Platform Custom Domains will automatically retry and should complete successfully once the upstream outage is resolved.

We'll continue to monitor this situation and provide updates. We apologize for the inconvenience.

May 8, 19:59 UTC
Resolved - Our engineering team has resolved the issue with multiple services in NYC2 region, and all services should now be operating normally. If you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience and thank you for your patience.

May 8, 19:53 UTC
Update - We are continuing to monitor for any further issues.

May 8, 19:21 UTC
Monitoring - Our Engineering team has identified the issue and implemented a fix to resolve the issues with multiple services, and is monitoring the situation. We will post an update as soon as the issue is fully resolved.

May 8, 18:01 UTC
Investigating - We are currently investigating an issue affecting multiple services in our NYC2 region. Our engineering team is aware of the situation and is working to identify the root cause and restore full connectivity as quickly as possible.

Users with resources in the NYC2 region may experience issues with Droplet connectivity, API requests, or other services.

We will provide additional updates as more information becomes available. We apologize for any inconvenience this may cause.

For at least the past two U.S. administrations, cutting China out of the tech supply chain has been a strategic goal in multiple industries. But the drone industry is one...

© Kinling Lo/Rest of World

May 7, 21:00 UTC
Completed - The scheduled maintenance has been completed.

May 7, 15:20 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.

May 7, 15:13 UTC
Scheduled - Start: 2026-05-07 15:00 UTC
End: 2026-05-07 21:00 UTC

Our Engineering team is performing maintenance on core control plane infrastructure. Please note that the existing infrastructure will continue running without issue. This maintenance may impact create, read, update, and delete (CRUD) operations in all regions.

Expected Impact:

During the maintenance window, users may experience brief periods of increased latency with the following platform operations:

Cloud Control Panel and API operations
Event processing
Droplet creates, resizes, rebuilds, and power events
Managed Kubernetes reconciliation and scaling
Load Balancer operations
Container Registry operations
App Platform operations
Managed Database creation and scaling

We do not expect any impact to customer traffic due to this maintenance. If an unexpected issue for the control plane arises, we will endeavor to keep any impact to a minimum and may revert if required.

If you have any questions related to this maintenance please send us a ticket from your cloud support page. https://cloudsupport.digitalocean.com/s/createticket