Normal view

How UAE is shifting gears to lead Middle East’s EV revolution

12 May 2025 at 05:00
Once a land of gas-guzzling super-cars, the United Arab Emirates is rapidly emerging as the Middle East’s unexpected electric vehicle leader, signaling global energy transition has reached the heartlands of...

© Christopher Pike/Bloomberg/Getty Images

A Tesla Inc. electric vehicle drives past residential and commercial skyscrapers in the Dubai Marina district of Dubai, United Arab Emirates, on Friday, Aug. 25, 2023. Chinese investors are gradually returning to Dubai's real estate market, joining Russian and other international buyers who have already pushed property prices in the emirate to record levels. Photographer: Christopher Pike/Bloomberg via Getty Images

How do you compete with Chinese e-commerce giants? A Vietnamese company is deploying housewives

By: Lam Le
9 May 2025 at 05:00
Vietnam’s e-commerce platform Sendo, once seen as a homegrown rival to deep-pocketed foreign competitors, shut down its core marketplace on April 15. While Sendo’s closure stemmed from the dominance of...

© Photography by Linh Pham for Rest of World

Nguyen Lan Huong, 30, receives groceries from a Sendo Farm motorbike delivery rider on May 3, 2025, in Hanoi, Vietnam. (Linh Pham for Rest of World)

The trade war is delaying the future of humanoid robot workers

8 May 2025 at 05:00
As viral clips of robots doing flips, kung-fu, and running a marathon rack up views online, U.S. and Chinese firms are locked in a more high-stakes race: deploying humanoid robots...

© Florence Lo/Reuters/Redux

An employee works on a desk near displays of humanoid robot parts, at the office of developer Ex-Robots in Dalian, Liaoning province, China June 6, 2024. REUTERS/Florence Lo

Droplet Metrics in BLR1

May 8, 13:01 UTC
Resolved - Our Engineering team has confirmed the resolution of the issue affecting certain Droplet metrics in the BLR1 region. Users should no longer see intermittent gaps in monitoring graphs for Droplets in the BLR1 region.

We appreciate your patience and apologize for any inconvenience this may have caused.

May 8, 01:26 UTC
Monitoring - Our Engineering team has implemented a fix to address the intermittent unavailability of Droplet metrics and delayed Resource Alerts in the BLR1 region.

Our team is now and monitoring the results and will continue to do so for an extended period to ensure this sporadic issue is addressed by the implemented fix.

At this time, we expect users not to experience further metrics gaps or delays in alerts.

We will post an update as soon as we confirm this incident is fully resolved or once we have further information. Thank you for your patience.

May 7, 22:04 UTC
Update - Our Engineering team is continuing to investigate the root cause of the issue with intermittent unavailability of Droplet metrics in the BLR1 region. Multiple reproduction efforts and testing against potential root causes are underway. Due to the sporadic nature of the issue, we anticipate incident updates for this issue to be less frequent, but we will share new information as soon as it is available.

At this time, users impacted by this incident will experience intermittent gaps in monitoring graphs for Droplets in BLR1, as well as delayed notifications for Resource Alerts (for any resources in BLR1).

We apologize for the inconvenience, and we'll share an update once we have more information.

May 7, 09:41 UTC
Update - Our Engineering team continues to investigate the intermittent unavailability of certain Droplet metrics in the BLR1 region. Due to the sporadic nature of this issue, our analysis requires additional time to correlate patterns and isolate the root cause.

We apologize for the inconvenience, and we'll share an update once we have more information.

May 6, 13:00 UTC
Investigating - Our Engineering team is currently investigating issues with certain Droplet metrics that are missing for the BLR1 region. Users may experience issues when accessing certain metrics on Droplets.

We apologize for the inconvenience, and we'll share an update once we have more information.

Droplet Creation in NYC1

May 5, 15:46 UTC
Resolved - Our Engineering team has confirmed the complete resolution of the issue that was affecting Droplet creation and console access in the NYC1 region. Users should now be able to deploy new droplets and access them normally in the NYC1 region.

All systems are now operating normally. We appreciate your patience and apologize for any inconvenience this may have caused.

May 5, 15:18 UTC
Monitoring - Our Engineering team has implemented a fix for the issue affecting Droplet creation and console access in the NYC1 region. Impacted users may have seen 504 Gateway Timeout errors during Droplet creation or when accessing the Droplet console.

Our team is currently monitoring the situation to ensure stability. We will provide a final update once we confirm the issue is fully resolved.

May 5, 14:18 UTC
Investigating - Our Engineering team is currently investigating an issue with creating Droplets in NYC1 region. During this time, users may see 504 Gateway Timeout errors when creating droplets in the NYC1 region.

We apologize for the inconvenience and will provide an update as soon as we have more information.

LON1 Network Maintenance 2025-05-07 20:00 UTC

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

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

May 4, 20:10 UTC
Scheduled - Start: 2025-05-07 20:00 UTC
End: 2025-05-07 23:00 UTC

During the above window, our Networking team will be making changes to the core networking infrastructure to improve performance and scalability in the LON1 region.

Expected impact:

During the maintenance window, users may experience delays or failures with event processing for a brief duration on Droplets and Droplet-based services, including Droplets, Managed Kubernetes, Load Balancers, Container Registry, and App Platform. 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

FreshRSS 1.26.2

3 May 2025 at 15:27

This is a security-focussed release for FreshRSS 1.26.x, addressing several CVEs (thanks @Inverle) 🛡

A few highlights ✨:

  • Implement JSON string concatenation with & operator
  • Support multiple JSON fragments in HTML+XPath+JSON mode (e.g. JSON-LD)
  • Multiple security fixes with CVEs
  • Bug fixes

Notes ℹ:

  • Favicons will be reconstructed automatically when feeds gets refreshed. After that, you may need to refresh your Web browser as well.

This release has been made by @Alkarex, @Frenzie, @hkcomori, @loviuz, @math-GH
and newcomers @dezponia, @glyn, @Inverle, @Machou, @mikropsoft

Full changelog:

Spaces Availability in FRA1

Apr 30, 14:57 UTC
Resolved - Our Engineering team has confirmed the complete resolution of the issue that was impacting the availability of Spaces in our FRA1 region. Users should no longer experience elevated error rates when accessing Spaces in the region.

We appreciate your patience and understanding while we worked to restore normal service.

If you continue to experience any issues, please open a support ticket from within the Cloud Control Panel for further review.

Apr 30, 14:14 UTC
Monitoring - Our Engineering team has implemented a fix for the issue affecting the availability of Spaces in our FRA1 region. Users should now see improved performance, and error rates have decreased.

We are continuing to monitor the situation closely to ensure stability. Thank you for your patience during the process and we will provide a final update once we confirm the issue is fully resolved.

Apr 30, 13:06 UTC
Investigating - Our Engineering team is currently investigating an issue affecting the availability of Spaces in our FRA1 region. During this time, users may experience high error rate when attempting to access Spaces in this region.

We are actively working on identifying the root cause and resolving the issue as quickly as possible. We understand the inconvenience this may cause and appreciate your patience.

We will provide further updates in the due course.

❌