Unstable Internet Connection in the Workers
Recently, I've noticed that several serverless jobs are encountering a very unstable internet connection, leading to extremely slow download and upload speeds.
This instability is resulting in connection errors on HTTP requests and the loss of packets. Additionally, the slow connection speed is causing significant delays in downloading from and uploading to S3, even for asset files that are just a few MBs in size, resulting in the consumption of excessive credits.
Furthermore, there are instances where connection errors or timeouts are causing the failure of generated output files to upload, resulting in job failures. This is particularly frustrating as credits were spent generating the output.
It's worth noting that this issue doesn't occur consistently; rather, it happens occasionally on some jobs.
Is anyone else experiencing this issue, or is it just me?
This instability is resulting in connection errors on HTTP requests and the loss of packets. Additionally, the slow connection speed is causing significant delays in downloading from and uploading to S3, even for asset files that are just a few MBs in size, resulting in the consumption of excessive credits.
Furthermore, there are instances where connection errors or timeouts are causing the failure of generated output files to upload, resulting in job failures. This is particularly frustrating as credits were spent generating the output.
It's worth noting that this issue doesn't occur consistently; rather, it happens occasionally on some jobs.
Is anyone else experiencing this issue, or is it just me?
Solution
Never mind. After using Runpod for over 4 months and spending over a thousand dollars on it, our company has decided to completely drop Runpod and switch to another platform. This decision was made due to Runpod's frequent instability and lack of timely and adequate support.
During our time with Runpod, we encountered numerous issues, including a significant "throttle disaster" two weeks ago, problems with webhooks, network issues, and more.
These incidents have resulted in financial losses for us, with some customers becoming upset and leaving. We can no longer tolerate these challenges.
We appreciate the creation of Runpod, and it can still be useful for testing, development, or personal purposes.
However, it is not suitable for use in production environments.
During our time with Runpod, we encountered numerous issues, including a significant "throttle disaster" two weeks ago, problems with webhooks, network issues, and more.
These incidents have resulted in financial losses for us, with some customers becoming upset and leaving. We can no longer tolerate these challenges.
We appreciate the creation of Runpod, and it can still be useful for testing, development, or personal purposes.
However, it is not suitable for use in production environments.
