RunpodReviews of runpod.io

Response from RunpodJul 6, 2026

Hello Jorge, thank you for the detailed feedback, and we're sorry to hear about this experience. We'd like to look into your specific case. Could you reach out to us at [email protected] with your account email, the endpoint or Pod ID, and roughly when this occurred? We'll have someone investigate right away. We appreciate the feedback on surfacing queue status and availability more clearly. We will pass this feedback along to the appropriate teams. Best regards, Runpod

Response from RunpodJul 6, 2026

Hello, thank you for the feedback, and we're sorry to hear about this experience. We understand the frustration of paying for a high-end GPU like the RTX 5090 and then losing usable time to an issue with pulling a public Docker Hub image. We'd like to dig into what went wrong. Could you reach out to us at [email protected] with your account email, the Pod ID (or approximate timeframe), the datacenter/region, and the image name you were trying to pull? We want to confirm exactly what happened in your case and get it fixed. We appreciate you flagging it, and we'll make sure our team investigates right away. Best regards, Runpod

Response from RunpodJun 30, 2026

Hello, thank you for the detailed feedback, and we're sorry to hear about this experience. We understand how frustrating it is to pay for persistent storage and then find that GPU capacity isn't available when you try to restart your Pod, especially after being offered a migration option that then also failed. We'd like to look into your specific case to understand exactly what happened. Could you reach out to us at [email protected] with your account email and the Pod ID or approximate timeframe? We'll have someone investigate right away. We also appreciate the point about communicating this availability risk more clearly before users create a Pod and pay for network volumes. Best regards, Runpod

Response from RunpodJun 30, 2026

Hello, we're sorry to hear about the data loss and understand how upsetting that is, especially after putting time into training work. We'd like to understand what happened so we can look into it properly. Could you let us know more about your setup, such as whether you were using a Network Volume or a Pod's local storage, and roughly when this occurred? Please reach out to us at [email protected] so our team can investigate. Best regards, Runpod

Response from RunpodJun 30, 2026

Hello, we're sorry to hear about the repeated pod crashes and the frustration with the responses you received, that's not the experience we want anyone to have. We'd like to look into the crashes you encountered and the credit request directly. Could you reach out to us at [email protected] with details on the pods and templates involved, along with approximate timeframes? We'll have someone take a closer look. Best regards, Runpod

Response from RunpodJun 5, 2026

Hi there, Thank you for taking the time to share your feedback. We’re sorry to hear that your experience with Runpod has been frustrating. We understand how disappointing it can be when you’re trying to deploy quickly and run into challenges with storage availability, regional capacity, logging, and platform responsiveness. The points you’ve raised are valuable feedback. Infrastructure availability can change as demand fluctuates, and we recognize that coordinating storage and compute resources across regions can add complexity to the deployment process. We’re continually working to improve both the user experience and platform visibility so it’s easier to understand available resources and deploy reliably. We’re also concerned by your comments regarding log visibility after crashes and delays in status updates. These are areas where troubleshooting and observability are critical, and we’d like to better understand the specific issues you encountered. If you’re willing, please reach out to our support team at [email protected] with additional details about your deployment. We’d appreciate the opportunity to investigate your experience and help resolve any underlying issues. Thank you again for your honest feedback. Input like this helps us identify where we need to improve. Best Regards, Runpod

Response from RunpodJun 5, 2026

Getting charged for compute while troubleshooting failed deployments or interrupted downloads is understandably frustrating. While there can be several reasons why a pod, model, or template doesn’t complete successfully, we never want users feeling like they’re spending more time and credits debugging than actually building. We’d appreciate the opportunity to investigate what happened in your case. If you reach out to our support team at [email protected] with additional details about the pod, model, or template involved, we’ll take a closer look and help determine what may have caused the issue. Thank you for sharing your experience. Feedback like this helps us identify areas where we can improve reliability and make the platform easier to use for everyone. Best Regards, Runpod

Response from RunpodJun 2, 2026

Thanks for sharing the detail. A pod that cannot start, slow model downloads, and uncertainty around data safety are serious concerns, and we understand why that would make the experience frustrating. We will route this feedback internally. If you are open to it, please contact support at https://contact.runpod.io with the pod, region, GPU type, and timeframe so the team can investigate what happened in your specific case.