最近还有其他人遇到在 SMS-activate 上充值的问题吗？
最近我遇到了一个问题，连续几天无法在 sms-activate 上充值余额。<p>这并不是一次偶发的故障——支付根本没有成功，而何时能解决这个问题也没有太多信息。对于依赖 SMS 验证服务进行测试、用户引导流程或质量保证的任何人来说，这种依赖失败是相当具有破坏性的。<p>这让我反思了一个我们常常低估的事情：那些“基础设施类”的第三方服务是多么脆弱，尤其是在它们被广泛使用但抽象程度较低的情况下。<p>在过去几个月里，我一直在开发一个名为 SMS-Act 的小型替代方案，最初只是为了降低我自己的运营风险。我的目标并不是在规模上竞争，而是专注于一些我个人关心的原则：
• 明确的范围：仅提供一次性、临时号码（不提供长期租赁）
• 透明的定价（如果验证失败，积分自动退款）
• 为开发者和测试人员提供更简单的用户体验，只需快速获取验证码
• 当出现问题时，减少“黑箱”行为<p>我并没有计划公开谈论这个项目，但最近的停机让我意识到，许多人可能面临同样的问题，并在默默寻找替代方案。<p>我很好奇：
• 你们是如何处理技术栈中的 SMS 验证依赖的？
• 你们是构建内部备用方案，还是在出现问题时直接更换服务提供商？
• 你在使用此类服务时遇到的最大痛点是什么？<p>如果有人感兴趣，我很乐意分享我在构建 SMS-Act 过程中的经验，或者讨论更好的方法来降低这类外部服务的风险。<p>（这里没有强硬推销——我更感兴趣的是其他人如何应对这个问题。）
查看原文
Recently I ran into an issue where I couldn’t top up my balance on sms-activate for several days.<p>This wasn’t a one-off glitch — payments simply didn’t go through, and there wasn’t much visibility on when it would be resolved. For anyone relying on SMS verification services for testing, onboarding flows, or QA, this kind of dependency failure is surprisingly disruptive.<p>It made me reflect on something we often underestimate: how fragile “infrastructure-like” third-party services can be, especially when they’re widely used but lightly abstracted.<p>Over the past months, I’ve been working on a small alternative called SMS-Act, initially just to reduce my own operational risk. The goal wasn’t to compete on scale, but to focus on a few principles I personally cared about:
• Clear scope: one-time, temporary numbers only (not long-term rentals)
• Transparent pricing (credits refunded automatically if verification fails)
• Simpler UX for developers and testers who just need a code, fast
• Fewer “black box” behaviors when something goes wrong<p>I didn’t plan to talk about it publicly, but the recent downtime made me realize many people here might be facing the same issue and quietly scrambling for alternatives.<p>I’m curious:
• How do you handle SMS verification dependencies in your stack?
• Do you build internal fallbacks, or just switch providers when things break?
• What’s the biggest pain point you’ve had with services like this?<p>If anyone’s interested, I’m happy to share what I’ve learned building SMS-Act so far — or just discuss better ways to reduce risk around these kinds of external services.<p>(No hard pitch here — genuinely more interested in how others approach this problem.)