After what seemed like never-ending downtime within our upload server, we are finally live and back in action. This, of course, isn't without its issues. Before we get started with this post, we would like to thank everyone for their patience while we worked to finish our bucket migration. It was a long and painful process that I am happy is finally over. This post will provide more information on why we made this change, what exactly has changed, the issues we faced along the way, and how we are working to mitigate them to ensure they do not happen again in the future.

Some insight

For the past year, we have relied on third-party services, mainly DigitalOcean, to be the main provider for our buckets. While it seemed to work fine at first, over time, this decision quickly became one we regret. Though we respect DigitalOcean as a hosting company and S3 provider, in the long run, using their services led to unexpected downtimes, authorization issues, and, most recently, data loss (but we will get into more detail about that below).

What changed

During the past month or so our team has been having discussions regarding hosting our own bucket system/service and what products/libs would allow us to obtain this goal with the least amount of downtime, problematic code and general issues. With that being said we are happy to announce that though it took longer than expected we are now officially hosting our own Bucket Service, for security reason we will not be sharing more info on the product/service used for the time being but this of course could change in the future.

About our bucket

Our new bucket is hosted within our server and is controlled and maintained by our Dev/Technical Team, all of the content within our bucket is backed up to a secure source on a rolling basis (every 24hrs) and will remain as such for the forseeable future. Authorization is required when accessing the important endpoints within the bucket (you can see this in action here by visiting bucket.cordximg.host).

Data Loss??

As briefly mentioned above during this migration we once again experienced yet another unfortunate Digital Ocean experience that resulted in data loss but don't worry about this to much, uploads were the only data affected by this issue, our technical team has a backup of uploads that will be added to our bucket within the coming weeks. Please note that this data is not guaranteed to be recent and you could still be missing some of your most recent uploads with CordX.

Our best efforts

As a result of the lost data our team has done their best to ensure this does not happen again in the future, we have implemented backups as mention above and took the necessary measures to ensure access is strictly forbidden. We know it's not much at the moment but it's definitely a foot in the right direction.

Ending statement

We understand that this migration has been a challenging time for everyone involved, and we deeply appreciate your patience and support throughout this process. Our team is committed to continuously improving our services and ensuring a more reliable and secure experience for all our users. If you have any questions or concerns, please do not hesitate to reach out to our support team. Thank you for being a valued member of our community.

System