RunpodReviews of runpod.io

Response from RunpodOct 16, 2025

Hi there, We're really sorry to hear about your experience and appreciate you bringing this to our attention. That definitely shouldn’t happen. If a pod goes down due to emergency maintenance, you shouldn't be billed during that downtime. Losing access unpredictively is not the level of service we aim to provide. Did you happen to reach out to our support team when this occurred? We don’t see a ticket associated with your account, and we’d really like the chance to investigate what went wrong and make things right. Please contact us directly - our team is here to help and will ensure everything is sorted out properly. Best Regards, Runpod

Response from RunpodOct 3, 2025

Hi there, We’re really sorry to hear about the issues you experienced with the templates and upload speeds. That’s definitely not the experience we want for our users, especially when it comes to getting full value for your spend. We absolutely don’t want you to lose a penny. We couldn’t find any support requests from your side in our help center, and it would’ve been great if you had reached out. Our team is always here to help. Please contact us at [email protected] with a screenshot of this review and our response, and our support team will do everything possible to improve your experience. We look forward to talk to you! Best Regards, RunPod

Response from RunpodOct 16, 2025

Hi there, Thank you for your detailed and honest feedback. We’re really sorry to hear about the difficulties you experienced. This is definitely not the experience we aim to provide, and we understand how frustrating it must have been to spend hours troubleshooting storage and uploads. We truly appreciate the specific suggestions you've shared; they’re incredibly helpful and will be passed on to our product team for review. We also noticed you haven’t raised a support ticket, and we’d love the opportunity to make things right. Our support team is always here to help and would be more than happy to walk you through the setup, resolve any S3 issues, and ensure everything works smoothly for you. We will make sure you don't waste your funds if there's any issue from our end. Please don’t hesitate to reach out — we’re confident that we can resolve this issue quickly. Best Regards, Runpod

Response from RunpodOct 16, 2025

Hi there, We're truly sorry to hear about your experience, and we appreciate you taking the time to share this feedback. It’s absolutely not the experience we want our users to have. Sudden interruptions shortly after launching a session are understandably frustrating, and it sounds like your session may have been affected by spot instance availability or resource constraints in a specific region. Please be aware that we strive to communicate these limitations clearly, and we continually work on enhancing infrastructure reliability and capacity. That said, if you're still encountering this issue, we’d really like the opportunity to make it right. We encourage you to contact our support team directly at [email protected] so we can investigate your specific case and assist you in finding a more stable setup — whether that involves switching to a different instance type or region. Thank you again for your honest feedback. Best Regards, Runpod

Response from RunpodAug 25, 2025

Hi there, Thank you for sharing your feedback, and we're sorry to hear about the frustration you've experienced. When you shut down a pod, it releases the GPU back into the pool, which is why you're only billed for idle storage. This is by design to help manage resources more efficiently. However, if the specific GPU you're trying to use is in high demand at the time you attempt to restart your pod, it may not be immediately available. This can result in the pod starting without a GPU. To avoid this, we recommend checking GPU availability across different regions. Often, selecting an alternate region can help you access the GPU you need without delay. If you're still unable to secure a GPU or if you have specific requirements, our support team is happy to help. Please feel free to contact us directly at [email protected], and we’ll work with you to find the best possible solution. Regards, Runpod

Response from RunpodAug 14, 2025

Hi there, Thanks for sharing your feedback. We understand your frustration around the serverless setup and the issues you encountered with the unsupported model. We noticed that you had reached out to our support team and seemed satisfied with the assistance provided—glad we could help! To make the serverless setup smoother, we highly recommend going through our documentation, as it covers key steps and best practices that can save you valuable time. The service interruptions you experienced were due to the use of an unsupported model. To avoid similar issues, please ensure you're selecting models from our list of supported options. If you're ever unsure or need help choosing or setting up your model, don't hesitate to contact our support team—we're always here to help you get everything running smoothly. Best Regards, RunPod

Response from RunpodJul 31, 2025

Hi Vladimir, Thanks for sharing your feedback, though we do wish it had come with a bit more context from your side. We took a close look at your interaction with our support team. The issue you experienced was related to a CUDA version mismatch -something that resulted from a manual configuration on your end. While this wasn’t a fault on our part, we still added $15 in credits as a goodwill gesture to help you recover and get back on track. That wasn’t something we were obligated to do, but we wanted to be supportive anyway. That said, it’s important to be honest here. Reaching out with demands for significantly more credits while stating you’ll leave a negative review if we don’t comply doesn’t set the right tone for constructive dialogue. We’re always open to helping our users, but we can’t support a practice where negative reviews are used as leverage for free credits. It’s just not something we can encourage. We’re very transparent with our billing. You’re only charged for actual runtime, and if there’s ever a genuine issue on our end, we fully reimburse — whether it’s $50 or $5000. But we also have to be fair to all users, and can’t refund usage tied to configuration errors that fall outside of our control. We’d still be happy to help you optimize your setup and avoid similar issues in the future. Just contact our support team, and we’ll do our best to assist. Best Regards, RunPod Support Team

Response from RunpodJul 31, 2025

Hi Marlon, We're really sorry to hear how frustrating your experience has been, and we truly appreciate you taking the time to share this — even if it’s tough to read. Feedback like yours is important, and we want to address your concerns directly. We understand that certain feature changes can feel like steps backward, especially if they impact workflows you've come to rely on. The visibility of network speeds was removed as part of broader updates to our UI and monitoring tools, but your point is valid — that transparency was helpful, and we’re currently exploring ways to bring back more detailed system metrics in a cleaner, more consistent way. As for the disk download speeds, we want to be clear: there’s absolutely no intentional throttling or attempt to slow things down. If you’re seeing unusually low speeds or pod loading times that feel unfairly long, that’s something we’d really like to look into. Our goal is always to provide the best performance possible, and if anything's falling short, it deserves attention. We never want a user to feel pushed away from our platform. If you're willing, please reach out to [email protected] or submit a ticket with details about the pod type, workload, and network issues you encountered. We’ll investigate thoroughly and do what we can to make it right. Best Regards, RunPod Support Team