Starlink is now cheaper than leading internet provider in some African countries

© Victor Moriyama/The New York Times/Redux

© Victor Moriyama/The New York Times/Redux

© Karen Dias/Bloomberg/Getty Images
Jan 9, 18:01 UTC
Resolved - From 15:28 to 15:32 UTC, an internal service disruption may have resulted in users experiencing errors while using the Cloud Panel or API to manage Spaces Buckets, Apps, Managed Database Clusters, or Load Balancers as well as other actions due to impacted downstream services.
If you continue to experience problems, please open a ticket with our support team.
Thank you and we apologize for any inconvenience.
| submitted by /u/mlhess [link] [comments] |
Jan 7, 16:43 UTC
Resolved - From 13:09 - 14:48 UTC, we experienced an issue with IPv6 network connectivity in our SFO3 region. Our Engineering team was able to identify the root cause, revert changes, and resolve the issue.
During that time, connectivity via IPv6 to services in SFO3 was impacted. This included, in particular, connectivity to and provisioning of Load Balancers, control plane connectivity to Kubernetes clusters, and connectivity to App Platform Apps.
If you continue to experience problems, please open a ticket with our support team. Thank you for your patience and we apologize for any inconvenience.
Jan 7, 15:51 UTC
Monitoring - Our engineering team has implemented a fix to resolve the networking issue in our SFO3 region. Users should no longer encounter connectivity issues, provisioning Load Balancers, latency, and timeout errors while interacting with resources in the SFO3 region.
We will post an update as soon as the issue is fully resolved.
Jan 7, 14:47 UTC
Update - Our Engineering team is continuing to investigate the cause of the issue with networking in our SFO3 region and is taking action to mitigate this incident by reverting recent changes. In addition to connectivity issues, users may see failures with provisioning Load Balancers in SFO3.
We are seeing some services recover, but expect to see a few more short periods of network connectivity issues as the reverts progress.
We will continue to share updates as soon as we have new information.
Jan 7, 13:35 UTC
Investigating - Our engineering team is investigating an issue related to the SFO3 network maintenance here: https://status.digitalocean.com/incidents/lf0njg8ysj0w
During this time users may experience connectivity issues, latency, and timeout errors while interacting with resources in the SFO3 data center.
We apologize for the inconvenience and will share an update once we have more information.
Jan 7, 14:14 UTC
Resolved - Our engineering team has resolved the issue preventing some users from adding new credit cards from the control panel. If you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience.
Jan 7, 13:38 UTC
Monitoring - Our engineering team has implemented a fix to resolve issues that some users experienced when attempting to add new credit cards to the Cloud Control Panel.
We are monitoring the situation and will post an update as soon as the issue is fully resolved.
Jan 7, 13:24 UTC
Investigating - Our engineering team is investigating reports of issues occurring when users attempt to add a new credit card in the billing settings page of the Cloud Control Panel.
During this time, some users may be unable to input card information. We apologize for the inconvenience and will share an update once we have more information.

© Simon Maina/AFP/Getty Images

Jan 7, 14:00 UTC
Completed - The scheduled maintenance has been completed.
Jan 7, 10:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jan 5, 10:15 UTC
Scheduled - Start: 2025-01-07 10:00 UTC
End: 2025-01-07 14:00 UTC
During the above window, our Networking team will be making changes to core networking infrastructure, to improve performance and scalability in the SFO3 region.
Expected impact:
These upgrades are designed and tested to be seamless and we do not expect any impact to customer traffic due to this maintenance. If an unexpected issue arises, affected Droplets and Droplet-based services may experience increased latency or a brief disruption in network traffic. We will endeavor to keep any such impact to a minimum.
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





In this release, the coding focus has been on moving to PHP 8.1+ and refactoring the integration of the SimplePie library (which was long due). At the same time, plenty of new features have been added. Enjoy! 🎄
Breaking changes 💥:
A few highlights ✨:
search:UserQueryA date:P1dCache-Control: max-age and ExpiresThis release has been made by @aledeg, @Alkarex, @Art4, @ColonelMoutarde, @Frenzie, @math-GH, @ramazansancar
and newcomers @DevGrohl, @UserRoot-Luca, @aarnej, @andrey-utkin, @bhj, @christophehenry, @davralin, @drego85, @ev-gor, @killerog, @kwarraich, @minna-xD, @mtalexan, @oshaposhnyk, @patHyatt
Full changelog:
search:UserQueryA date:P1d #6851Cache-Control: max-age and Expires #6812, FreshRSS/simplepie#26Authorization) #6820&state=96 (no UI button yet)phpgt/cssxpath library with improved CSS selectors #6618
:last-child, :first-of-type, :last-of-type, ^=, |=("a b") or (!c) #6818v mode #7009+ #7033
Referer #6822, FreshRSS/simplepie#27
Referer: https://example.net/ to the custom HTTP headers of the feed #6820windows.open noopener (to avoid flash of white page in dark mode) #7077, #7089aria-hidden bug, and use HTML5 hidden #6910<pre> and <code> #6770<template> instead of duplicated HTML code #6751, #7113<template> #6864? to show shortcut page and help #6981simplepie_after_init #7007Minz_Request::paramArray() #6800booleansInConditions #6793phpstan.dist.neon to allow custom configuration in phpstan.neon #6892ControlSignature #6896

© Rest of World

Dec 19, 05:03 UTC
Resolved - From 1:23 UTC to 3:04 UTC, users may have experienced issues with events being stuck or delayed, such as powering on/off, and resizing Droplets in the NYC3, AMS2, BLR1, SGP1, and SYD1 regions. Additionally, Managed Database creates were delayed in all regions.
Our Engineering team has confirmed full resolution of the issue, delayed events and new events should complete as normal now.
Thank you for your patience through this issue. If you continue to experience any issues, please open a support ticket from within your account.
Dec 19, 04:28 UTC
Update - Our Engineering team has confirmed that new events are succeeding, and we're finalizing cleaning up any stalled events. We will post an update as soon this issue is fully resolved.
Dec 19, 03:08 UTC
Monitoring - Events in NYC3 has been enabled now and users may continue to submit new events. We are starting to see success rates with event processing go up.
We will post another update soon. Thank you for your patience.
Dec 19, 02:42 UTC
Update - Our Engineering team continues to work to mitigate the issue with event processing in multiple regions.
To help address the issue, we are temporarily disabling all Droplet-related actions in the NYC3 region for a period of 20 minutes. During this time, users in NYC3 will not be able to submit actions, such as creating, resizing, powering on/off, etc.
We apologize for the inconvenience and appreciate your patience as we work to resolve this issue. Further updates will be shared as they become available.
Dec 19, 01:45 UTC
Investigating - Our Engineering team is investigating an issue impacting Droplet event processing in multiple regions.
At this time, users may experience issues with events appearing to be stuck or delayed, such as powering on/off, and resizing Droplets in NYC3, AMS2, BLR1, SGP1, and SYD1 regions. Additionally, Managed Database creates are delayed in all regions.
We apologize for the inconvenience and will share an update once we have more information.