核心次级服务绩效退化
- investigating
我们正在调查影响核心下层服务的退化业绩报告。 一些客户使用部分服务可能会遇到反应较慢或困难. 我们的小组正在努力查明根源,并将在我们得到更多信息后立即提供另一个最新情况.
- monitoring
性能似乎已经恢复正常。 并且一旦部署细节得到确认.
- resolved
性能恢复正常,事发后得到解决. 所有相关服务都已投入运作.
自动翻译自官方事件更新。
55 Subbly incidents · 2021年9月 — official updates, affected components, duration and resolution details.
我们正在调查影响核心下层服务的退化业绩报告。 一些客户使用部分服务可能会遇到反应较慢或困难. 我们的小组正在努力查明根源,并将在我们得到更多信息后立即提供另一个最新情况.
性能似乎已经恢复正常。 并且一旦部署细节得到确认.
性能恢复正常,事发后得到解决. 所有相关服务都已投入运作.
自动翻译自官方事件更新。
在2026年8月31日协调世界时06:00至2026年9月2日协调世界时11:00之间,销售税没有适用于在Subbly上所开出的一些发票. 原因是我们用来计算税率的供应商TaxJar在上游意外出故障,而我们的系统并没有浮出水面。 受影响的发票是在不缴纳本应缴纳的税款的情况下收取的。 我们现在已更正了这些发票,收缴了拖欠的缺失税款,并通知了所有受影响的人.
□ 总结 在2026年8月31日协调世界时06:00至2026年9月2日协调世界时11:00之间,销售税没有适用于在Subbly上所开出的一些发票. 原因是我们用来计算税率的供应商TaxJar在上游意外出故障,而我们的系统并没有浮出水面。 受影响的发票是在不缴纳本应缴纳的税款的情况下收取的。 现在,我们纠正了这些发票,收缴了所欠的缺失税,并通知了所有受影响的人(只有少数商人受到影响)。 # 发生了什么事# 在这个窗口期间,TaxJar开始毫无警告地将403个错误退回我们的税收计算请求. 我们的计费引擎将一个失败的计算作为"不收税",用零税额建造了发票,并向客户收取未收税总额. 因为失败是悄悄处理的 我们的团队没有接到警报 我们得知了这个问题,当它向我们报告时,当时潜在的TaxJar错误已经停止了。 只有依靠Subbly自己的TaxJar整合的商店受到影响. 拥有自己的TaxJar账户的商店,以及具有兼顾税收的定价的商店,都没有向客户收取过低费用。 ** 根据我们的深入分析,我们只影响到一小部分发票(~0.1%\),但如果你受到影响,我们没有联系你,请告诉我们。 ∮我们所做的∮ 我们查明了窗口中每张漏税的发票,并重新计算了应缴的税额,采用与原续签或离职时相同的计算方法。 对于具有排他性定价的商店,我们将缺失的税费记入了档案中的客户支付方法,作为单独的,有明显标签的销售税发票,并将税费记入了原始发票和订单. 每一个客户都收到商店的电子邮件,解释指控。 如果无法收取费用,店主被告知哪些客户受到影响,以便他们决定如何采取后续行动。 对于具有普惠性定价的商店,客户已经支付了正确的金额,因此我们只记录了发票和订单上缺失的税分. 没有收费,也没有发送客户电子邮件。 每个受到影响的店主都收到了一份为店铺所做的具体工作的摘要。 # 我们正在改变 # 税收计算失败不再保持沉默。 我们的团队现在立即被通知 当税收提供者返回错误, 所以这样的问题 将在几分钟内而不是几天内被抓住。 我们还在努力制定税收计算退税战略,以便上游停税不会导致不征税的发票被收取。 我们的道歉 我们为这给你和你的顾客带来的不便感到抱歉。 我们知道,一个意外的收费,无论多么小,也无论解释的多么清楚,不是任何人想从他们信任的商店得到的东西。 你对我们这个平台的信任被认真对待. 如果您对受影响的发票有任何疑问, 我们所做的更正, 或以上的步骤, 请通过您的行政支持聊天联系我们, 我们将提供帮助.
自动翻译自官方事件更新。
内部操作测试事件
这一问题已经确定,一个解决办法正在实施之中.
这一事件已经得到解决.
自动翻译自官方事件更新。
We've temporarily disabled the checkouts to avoid double charges. The team is working on the fix.
We've identified the root cause and deployed a fix. Checkouts are fully operational again. We're keeping this incident open while we monitor checkout behavior and assess the impact on orders placed during the disruption. We'll post a final update once monitoring confirms stability.
Incident has been resolved and the system is fully operational. Check the postmortem for additional information.
Service Disruption - August 10, 2026 \(Resolved\) On August 10, between 12:39 and 14:08 UTC, checkout was not working, affecting 29 users and 77 purchases. The issue was caused by a routine update that relied on a database field mistakenly present in engineer's local development database and missing from production; a fix was deployed and all services were fully restored by 14:08 UTC. All the payments during this window were processed without orders or invoices being created. All affected charges should be refunded.
我们目前正在调查一个影响一些传统建筑商网站的问题。 受到影响的商人在访问其网站和遗产编辑时可能遇到503个暂时无法获取的服务错误。 我们的团队正在努力找出根源,尽快恢复服务.
这个问题是由第三方服务引起的,它赋予我们传统的网站建设者权力。 我们正与他们的团队合作,尽快恢复服务。 我们预计这个问题至少还需要30分钟才能解决, 也鼓励商人利用传统建筑商, 我们的团队乐于帮助尽可能平稳地过渡, 包括在必要时重建您的网站。 只要联系到更多的资讯, 电子邮件支持@ subbly.co
我们已经解决了影响遗产建设者网站的问题,现在所有服务应该正常运行. 谢谢你的耐心.
自动翻译自官方事件更新。
我们知道一个问题 阻止一些用户 访问遗产构建器 和一些网站 关闭。 我们的团队正在积极调查这个事业,并正在设法解决问题。 我们对此不便表示歉意,一旦我们掌握了更多信息,我们将再次介绍最新情况.
他的问题已经解决了,现在又有了遗产建设者.
自动翻译自官方事件更新。
CSV export requests are not generating or sending export emails to merchants. We are working to identify the root cause and implement a fix as soon as possible. Further updates will be provided once we have more information.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
We're currently investigating the intermittent problems with the preview servers on the Agentic Builder. Live builds are not affected. We're sorry for the inconvenience.
We've identified the issue, working on the fix.
We are continuing to work on a fix for this issue.
A fix has been implemented and we are monitoring the results.
Fix was implemented, we're continuing to monitor the situation. Preview servers have been restored. Please contact support team for any questions or if you're still having problems. Apologies for the hiccup.
The Agentic Builder is currently experiencing problems with previews being loaded for a smaller subset of customers. We apologize if your build is currently affected (and you're not able to see the preview). We're working on a solution. Published sites are not affected.
We deployed the fix, preview servers are working again. We're currently monitoring the situation. Please report any potential problems to the support team.
We are continuing to monitor for any further issues.
This incident has been resolved.
We are investigating reports of users being unable to access the AI Builder. Our engineering team is currently investigating the root cause and will update you shortly.
The issue affecting access to the AI Builder has been resolved. Users should now be able to access and use the builder normally. We apologize for the disruption and appreciate your patience while our team worked on restoring the service.
We recently rolled out a major upgrade to the AI Builder, and this issue appeared following that update. The issue has been identified, and our team is actively working on implementing a fix.
A fix has been put in place and the builder should be operating as normal. IMPORTANT: if you do experience the same issue as before, please create a new chat to overcome this. Apologies for the inconvenience, the upgrade is a big step for us and will make everything much smoother and more reliable. If you experience any issues please report them to us so we can resolve them quickly for you. Thank you! - Subbly's Engineering Team
We are continuing to monitor for any further issues.
Considering there have been no more reports of this issue, we're marking it as resolved. Apologies again for the inconvenience.
We are currently experiencing an issue where the AI Builder preview may appear offline or fail to load. Our team is aware of the issue and actively working on identifying the cause and resolving it as quickly as possible. We’ll share an update as soon as we have more information.
The issue with the AI Builder preview not loading has now been resolved. Everything should be functioning as expected.
We’re currently investigating an issue where the AI Builder may not open or load as expected for some users. Our team is actively looking into this and working on identifying the root cause. We’ll share an update as soon as we have more information. Thank you for your patience.
The issue with the AI Builder not loading has been fully resolved. Everything should now be working as expected. Thank you for your patience.
We're currently experiencing issues accessing the legacy builder. More information to follow. Sites and builds are intact and publicly accessible, access to the builder editor is currently degraded and inaccessible.
Problem with the hosting provider has been diagnosed. We're working on implementing the temporary solution.
Access to the legacy builder has been restored. Thanks for your patience and apologies for any inconvenience.
We're currently having problems with 3rd party hosting we're using to host projects made on the legacy website builder. Problem has been diagnosed and the hosting partners are actively working on resolving this. As a result of this, access to the legacy builder is revoked, but the sites are fully operational. We apologize for the inconvenience.
Root cause of the issue has been identified, we're waiting for the hosting partners to resolve for it. There's no ETA communicated at this point, we'll update once we have ETA for this to be resolved.
A fix has been deployed, we're still monitoring the problem. Website builder is accessible now.
Problem was resolved. Everything is fully operational again. Sorry for the downtime.
We are currently experiencing an outage related to our API which is affecting the checkout functionality and some website builder pages. The engineering team is actively investigating the issue and working to identify the root cause. We will provide an update as soon as more information is available and once the issue has been resolved.
We've identified and deployed the hotfix for the problem. Checkouts are partially operational at the moment. We're continuing to monitor.
The issue has been resolved and all services are operating normally. Thank you for your patience while we investigated and fixed the problem.
Checkouts are temporarily unavailable due to an unexpected issue during the recent deployment.
Checkouts are live again. Apologies for the downtime.
We are currently investigating an issue affecting the Agent Builder Chat. Users may experience problems loading or interacting with the chat interface. Our engineering team is actively working on identifying and resolving the problem. We will provide updates as soon as more information becomes available.
We have identified the root cause of the issue affecting the Agent Builder Chat. A fix has been implemented and is currently being prepared for deployment. We expect the update to be released shortly. Thank you for your patience while we work to fully resolve this.
The issue affecting the Agent Builder Chat has been resolved. A fix has been successfully deployed, and the service is now operating normally. Thank you for your patience and understanding.
We are investigating API synchronization issues affecting AI site builds. Impact includes unavailable checkouts, missing product metadata/bundles, and related logic failures.
Problem with the API identified. Working on a fix.
Fix was deployed, system is fully operational.
We are currently experiencing intermittent instability across the Subbly platform. The root cause is an ongoing Cloudflare outage affecting global traffic routing. Cloudflare is still actively working on resolving the issue, and because our infrastructure relies on their network, Subbly services may continue to fluctuate. Our engineering team is continuously monitoring the situation and will provide updates as soon as there are changes in Cloudflare’s status.
The issue has been identified and a fix is being implemented.
This issue appears to have resolved, however Cloudflare haven't marked it as resolved on their end so we recommend monitoring their status page if you experience further issues: https://www.cloudflarestatus.com/ We apologise for any inconvenience.