juvenilelocksmith
juvenilelocksmith
RRunPod
Created by juvenilelocksmith on 12/20/2024 in #⛅|pods
Repeated RunPod Stripe payment problems
Those aware of the situation failed to intervene or expedite a resolution despite their knowledge of the policy you callously raise as a shield. Yet it is no shield at all given the self-evidently egregious circumstances. This case represents clear negligence that played out on a public platform, yet your response suggests a disturbing lack of concern for customer welfare. Your dismissive response is unacceptable, and I assure you this matter will not be easily resolved. This issue concerns a service provider's fundamental duty to maintain basic standards of care and communication. The evidence demonstrates a pattern of neglect and apathy that cannot be defended. Given these circumstances, you owe both myself and others similarly affected a formal apology and appropriate compensation for the significant harm caused. Should you choose not to address this matter properly, I will take necessary steps to prevent other paying customers from experiencing such disrespect. I await your prompt and comprehensive response, including a compensation proposal that reflects the severity of these failures.
9 replies
RRunPod
Created by juvenilelocksmith on 12/20/2024 in #⛅|pods
Repeated RunPod Stripe payment problems
Your position demonstrates not only a troubling lack of care but also a level of disregard that no reputable company should defend. Let us examine the facts: RunPod's storage fees rank among the highest in the market. The maintenance of a 600GB drive at approximately $30 per month represents a significant investment, clearly indicating the valuable nature of the stored data. Any business observing a customer's continued retention of such a large drive over months, given its premium cost, would recognise this significance. The deletion of a drive after merely "a couple of days," without reasonable attempts to contact the customer, demonstrates reckless disregard for crucial data. "Reasonable" is an objective standard, and this was no unforeseen accident—it was entirely predictable and preventable. Your failure to communicate effectively with a premium-paying customer suggests serious negligence. More concerning still is your non-responsiveness despite knowing that unresolved payment issues would result in data deletion. And if your customer is hospitalised after a traffic accident? This appears an ill-considered position broadly. In my specific case, I documented in this thread my attempts over several days to resolve a payment issue—one your representative acknowledged as inherent to your system and this by design. Your customers neither understand these system mechanics nor have access to any recourse when problems arise. What options exist when your system locks out a customer? I sent private messages to two team members explaining the situation's urgency, receiving no response. Even after this post gained attention, it took hours for initial staff acknowledgement, followed by a day of silence and merely a "like" to my follow-up message. During this period of apparent indifference, my drive was erased.
9 replies
RRunPod
Created by juvenilelocksmith on 12/20/2024 in #⛅|pods
Repeated RunPod Stripe payment problems
No description
9 replies
RRunPod
Created by juvenilelocksmith on 12/20/2024 in #⛅|pods
Repeated RunPod Stripe payment problems
I sent the details through yesterday
9 replies
RRunPod
Created by juvenilelocksmith on 1/28/2024 in #⛅|pods
Pod impossible to access
Removing the s from http(s) appears to resolve the issue.
4 replies