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.

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

• Milestone

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:

• Features
  • Implement JSON string concatenation with & operator #7414
  • Support multiple JSON fragments in HTML+XPath+JSON mode #7369
• Bug fixing
  • Fix escaping of tag search #7468
  • Fix CLI parsing of Boolean flags #7430
  • Fix API for labels with slash #7437
• SimplePie
  • Fix support for feeds with XML preamble + DTD #7515, simplepie#914
  • Merged upstream #7434
    • Upstream fix simplepie#912
• Security
  • Disallow <iframe srcdoc=""> #7494, CVE-2025-32015
  • Disallow <button formaction=""> #7506
  • Improve favicons hash to avoid favicon pollution #7505, CVE-2025-46339
  • Add Content-Security-Policy HTTP headers to favicons #7471, CVE-2025-31136
  • Web scraping forbid security HTTP headers in cURL #7496, CVE-2025-46341
  • Add some HTTP headers Referrer-Policy: same-origin #6303, #7478
  • Use HTTP POST for logout #7489, CVE-2025-31482
  • Make update URL read-only #7477
  • Fix for extensions: Restrict valid paths in ext.php #7479, CVE-2025-31134
  • Fix for extensions: Secure serving of user files #7495
• Extensions
  • Fix file serving for symlinked extensions #7545
  • Catch extension exceptions in override #7475
  • JavaScript: new event to detect context loaded #7452
• Deployment
  • Apache: add check for mod_filter to ensure that AddOutputFilterByType works #7419
• UI
  • Accessibility: Add :focus style to some dropdown menus #7491
  • New size option for the Mark as read button #7314
  • Update bcrypt.js from 2.4.4 to 3.0.2 #7449
  • Various UI and style improvements: #7168, #7526
• I18n
  • Rework credits #7426
  • Improve French #7432
  • Improve Italian #7540
  • Improve Polish #7508
  • Improve Turkish #7442
• Misc.
  • Improve PHP code #7431, #7488, #7534
  • Update dev dependencies #7480, #7482, #7483,
    #7484, #7485, #7486,
    #7487, #7533, #7535,
    #7536, #7537, #7538

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.

Apr 30, 00:11 UTC
Resolved - Our Engineering team has confirmed full resolution of the network issue with new DOKS worker nodes in our SFO2 region.

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

Apr 29, 23:49 UTC
Monitoring - Our Engineering team identified the cause of the issue and has rolled out a fix to resolve the network issue with new DOKS worker nodes. At this time, all services should be operating normally.

We are actively monitoring the fix and will post an update as soon as the issue is fully resolved.

Apr 29, 22:25 UTC
Investigating - Our Engineering team is investigating an issue causing new DOKS worker nodes to have network issues in our SFO2 region. Operations such as creating new DOKS nodes, manually or autoscaled, will have network connectivity issues within the clusters they are added to during this time.

Our Engineering team is actively working to identify the root cause and restore service as quickly as possible. We will continue to provide updates here as we make progress.

Apr 30, 21:00 UTC
Completed - The scheduled maintenance has been completed.

Apr 30, 13:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.

Apr 28, 13:25 UTC
Scheduled - Start: 2025-04-30 13:00 UTC
End: 2025-04-30 21:00 UTC

Hello,

During the above window, our Engineering team will be 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 increased latency during two 5 minute windows 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

Thank you,
Team DigitalOcean

Apr 28, 11:17 UTC
Resolved - This incident has been resolved.

Apr 28, 11:14 UTC
Investigating - Between 09:58 UTC and 10:11 UTC, our Engineering team observed issues impacting DNS resolution in our LON1 region. During this time, some users may have experienced errors while trying to resolve domain names from within Digitalocean resources.

Our team was able to take quick action to mitigate the impact and resolve the issue, and all services in the LON1 region are now functioning normally. Thank you for your patience, and we apologize for any inconvenience.

If you are still experiencing issues or have additional questions, please open a Support ticket right away.

Apr 24, 16:31 UTC
Resolved - Our Engineering team has confirmed full resolution of the issue impacting event processing in the FRA1, AMS2, BLR1, SGP1, NYC1, and SYD1 regions.

If you continue to experience any problems, please open a ticket with our Support team. Thank you for your patience, and we apologize for any inconvenience.

Apr 24, 15:53 UTC
Monitoring - Our Engineering team has identified the cause of the issue causing delays in Droplet event processing in our FRA1 region, and has implemented a fix.

While investigating this issue, our Engineers also observed some events appearing to be stuck or delayed in the AMS2, BLR1, SGP1, NYC1, and SYD1 regions. As of now, the event processing rates have returned to normal in all these regions.

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

Apr 24, 13:41 UTC
Investigating - Our Engineering team is investigating an issue causing delays in Droplet event processing in our FRA1 region.

This includes operations such as creating, resizing, powering on/off, or deleting Droplets. These actions may take longer than usual to complete or may appear to be temporarily stalled.

Our engineering team is actively working to identify the root cause and restore normal processing speeds as quickly as possible. We will continue to provide updates here as we make progress.