在生产中未反映的最新定价
Pending
- resolved
状况:已解决 这一事件已经得到解决。 我们将在公开事件报告中提供进一步信息。 2026年10月27日,价格变动的账户出现价格更新,没有在店面上反映. 这一事件由内部服务更新所引发. 我们通过对定价模块进行修正并纠正所有受影响的价格变化来减轻其影响。 我们的销售流量 在这个事件中没有受到影响。 我们对此可能造成的不便表示歉意。 影响成分定价计算(业务)
自动翻译自官方事件更新。
33 Vtex incidents · 2025年9月 — official updates, affected components, duration and resolution details.
状况:已解决 这一事件已经得到解决。 我们将在公开事件报告中提供进一步信息。 2026年10月27日,价格变动的账户出现价格更新,没有在店面上反映. 这一事件由内部服务更新所引发. 我们通过对定价模块进行修正并纠正所有受影响的价格变化来减轻其影响。 我们的销售流量 在这个事件中没有受到影响。 我们对此可能造成的不便表示歉意。 影响成分定价计算(业务)
自动翻译自官方事件更新。
Status: Resolved This incident has been resolved. We will not provide further information in a public incident report. Summary On Oct 21, 2026, accounts experienced rendering errors when accessing the VTEX Admin through myvtex environments. This incident was triggered by an internal service update. We mitigated its impact by reverting the update, restoring the previous stable behavior. Our sales flow was unaffected during this incident. We apologize for any inconvenience this may have caused. Affected components Admin Operations (Operational)
状态:解决于2026年10月21日,从00:03到00:34 UTC,将Master Data作为依赖性的系统和集成系统经历了比平时更高的出错率. 在这起事件中,我们的全球销售流量受到了部分影响. 我们对此可能造成的不便表示歉意。 受影响的组件 主数据(业务)
自动翻译自官方事件更新。
状况:已解决 这一事件已经得到解决。 摘要 2026年10月20日,VTEX IO上的一些存储面经历了高发出错和页面加载故障,一些购买者经历了出错导航. 在这次事件中,我们的销售流量微乎其微,间接受到影响,影响到一些账户。 我们对此可能造成的不便表示歉意。 受影响的组件 VTEX IO(业务)
自动翻译自官方事件更新。
状况:已解决 这一事件已经得到解决。 我们不会在公开事件报告中提供进一步信息。 摘要 2026年9月25日 UTC14:19至15:25,少数账户在通过myvtex环境访问VTEX Admin时遇到渲染错误和代理Timeout出错. 这一事件由内部服务更新所引发. 我们通过恢复更新,恢复先前的稳定行为来减轻其影响. 在这次事件中,我们的销售流量没有受到影响。 我们对此可能造成的不便表示歉意。 受影响的组成部分 行政业务(业务)
自动翻译自官方事件更新。
状况:已解决 这一事件已经得到解决。 我们不会在公开事件报告中提供进一步信息。 2026年9月10日,从协调世界时下午1:00至协调世界时2:30,影响账户在竞选管理面板上执行操作和访问性能分析时出错. 该事件已缓解,该平台目前已投入使用. 然而,随着平台的恢复完成,客户仍然可能遭遇到一些后遗症或偶尔的停工. 我们的销售流量 在这个事件中没有受到影响。 我们对此可能造成的不便表示歉意。 受影响的组成部分 行政业务(业务)
自动翻译自官方事件更新。
状况:已解决 这一事件已经得到解决。 摘要 2026年8月17日,从协调世界时22:38到23:04,作为依赖性的Master Data的系统和集成系统经历了比平时更高的出错率. 在这次事件中,我们的全球销售流量受到了部分影响,例如在皮克点情景中。 我们对此可能造成的不便表示歉意。 受影响的组件 主数据(业务)
自动翻译自官方事件更新。
**[DELETE BEFORE POSTING: [Incident template library](https://support.atlassian.com/statuspage/docs/incident-template-library/ "Incident template library")]** We are currently investigating an issue in {Affected Modules}. {Affected Accounts/Target Users} may be experiencing {Symptoms}. Our incident response team is working to identify the root cause and implement a solution. We will send an additional update in the next 30 minutes, or as soon as we have more information to share.
Our monitoring team has detected increased error rates for FastStore. Stores using FastStore may be experiencing intermittent errors when visiting certain pages. Our incident response team is working to identify the root cause. We will send an additional update as soon as we have more information to share.
The fix for the issue in FastStore service has been implemented. Affected accounts should no longer experience issues when accessing their stores. Our incident response team is monitoring to guarantee that normal platform behavior is fully reestablished. We will send an additional update in the next 30 minutes, or as soon as we have more information to share.
This incident has been resolved. **Summary** On Jun 16, 2026, from 18:16 to 19:36 UTC, shoppers navigating in FastStore storefronts experienced intermittent while browsing through some pages. The occurrence of this symptom was dependent on the cache available to the shopper. Around 19:30 UTC we noticed an improvement in FastStore navigation, normalizing by 19:36 UTC. We apologize for any inconvenience this may have caused.
我们目前正在调查一个影响采购后流动的问题。 受影响的用户可能会看到订单被卡在一个特定状态下,更新没有如预期的那样进行. 我们的事件应对小组正在努力查明根源,并执行一项解决办法。 我们将在接下来的30分钟里,或一旦我们有更多的信息要分享,就发出新的消息.
已经针对影响采购后流动的问题采取了补救措施。 受影响的商店不应再陷入订单状态,目前正在处理之中。 我们的事故应对小组正在监测,以保证正常的平台行为得到全面恢复. 我们将在接下来的30分钟里,或一旦我们有更多的信息要分享,就发出新的消息.
这一事件已经得到解决。 ** 概要** 在这次事件中,一些商家在秩序管理方面遇到了问题,特别是在处理订单状态工作流程方面. 店员没有受到这一事件的直接影响,只有购买后订单处理受到影响. 我们对此可能造成的不便表示歉意.
自动翻译自官方事件更新。
We are currently investigating an issue affecting post purchase flow. Affected users may see orders stuck in a particular status, with updates not progressing as expected. Our incident response team is working to identify the root cause and implement a solution. We will send an additional update in the next 30 minutes, or as soon as we have more information to share.
We are still investigating the issue affecting the post purchase flow. Our team continues to analyze the behavior and collect additional data to determine the root cause. We will provide an additional update in the next 30 minutes, or sooner if more information becomes available.
We continue to observe delay in the post purchase flow. We are actively working on mitigation actions and will provide further updates as soon as more information becomes available.
The fix for the issue affecting post purchase flow has been implemented. Affected stores should no longer experience stuck in orders and are now being processed. Our incident response team is monitoring to guarantee that normal platform behavior is fully reestablished. We will send an additional update in the next 30 minutes, or as soon as we have more information to share.
This incident has been resolved. **Summary** On May 14, 2026, from 04:49 to 07:57 UTC, some merchants experienced issues in order management, particularly in processing the orders status workflow. Around 07:41 UTC we noticed an improvement in order processing, normalizing by 07:57 UTC. Shoppers were not directly affected by this incident, only the post-purchase order processing was affected. We apologize for any inconvenience this may have caused.
我们正在调查一个影响离职的问题。 销售可能受到部分影响,一个问题还在影响商店导航和会议稳定性,使用户通过遗产门户访问商店。 我们将在接下来的30分钟内或一旦我们有更多的信息要分享后立即发出新的消息.
调整后,我们正在监测离职服务。 此时,销售可能会被部分地影响,而PDP商店通航,仅供客户通过"遗产门户"访问商店. 我们将在接下来的30分钟内或一旦我们有更多的信息要分享后立即发出新的消息.
这一事件已经得到解决。 内容提要 出站服务在协调世界时16:34完全正常化,PDP商店导航(Legacy Portal)服务在协调世界时16:43完全正常化.
自动翻译自官方事件更新。
The fix for the issue in Orders has been implemented. Merchants may be experiencing issues in order management, particularly in advancing the orders workflow in Processing and Payment Pending status. Our incident response team is working to reprocess affected orders and transactions as soon as possible. We will send an additional update in the next 30 minutes, or as soon as we have more information to share.
This incident has been resolved. **Summary** On May 09, 2026, from 06:24 to 07:16 UTC, some merchants experienced issues in order management, particularly in advancing the orders workflow in Processing and Payment Pending status. We apologize for any inconvenience this may have caused.
We are currently investigating an issue affecting login functionality. Some users may be experiencing errors during the login process. Our incident response team is working to identify the root cause and implement a solution. We will provide an update within the next 30 minutes, or sooner if more information becomes available.
A fix for the login issue has been implemented. Affected users should no longer be experiencing login errors. Our incident response team is monitoring to ensure that normal platform behavior is fully restored. We will provide another update within the next 30 minutes or sooner if more information becomes available.
This incident has been resolved. **Summary** On Apr 14, 2026, from 20:40 to 22:30 UTC, some accounts experienced login instability that impacted access to the platform. This incident was triggered by a recent platform improvement that led to unexpected instability. We mitigated its impact by implementing corrective measures to restore stability. Our sales flow was unaffected during this incident. We apologize for any inconvenience this may have caused.
We are currently investigating an issue affecting storefront availability. Affected users may be experiencing intermittent issues accessing the store, including errors such as 504 Gateway Timeout. Our incident response team is working to identify the root cause and implement a solution. We will send an additional update in the next 30 minutes, or as soon as we have more information to share.
We are still investigating the issue affecting storefront access and error rates. Our team continues to analyze the behavior and collect additional data to determine the root cause. At this time, some users may still experience intermittent errors, including 504 Gateway Timeout, when accessing the store. We are actively working on mitigation actions and will provide further updates as soon as more information becomes available.
We are currently investigating an issue causing instability and intermittent behavior. Multiple stores are experiencing degraded performance, with symptoms that may include slowness, intermittent failures, loading errors, and occasional inability to access certain pages. Our team is actively working to identify the root cause and implement mitigation measures. We will provide further updates as soon as more information becomes available.
We continue to observe intermittent instability affecting multiple stores, with symptoms that may include slowness, intermittent failures, loading errors, and occasional inability to access certain pages. Mitigation measures are in progress to reduce impact. We will provide further updates as soon as more information becomes available.
We have identified cache-related issues as a contributing factor to the instability affecting the platform. Our team is actively working to implement a solution while minimizing the impact. We will provide an additional update in the next 30 minutes, or sooner if more information becomes available.
The fix for the issue affecting storefront availability and platform stability has been implemented. Affected stores should no longer experience slowness, intermittent failures, loading errors, or issues accessing certain pages. Our incident response team is monitoring to ensure that normal platform behavior is fully reestablished. We will provide an additional update in the next 30 minutes, or sooner if more information becomes available.
The platform remains stable following the implemented solution. We are currently verifying a small number of errors affecting some stores. Our teams are actively investigating these occurrences and closely monitoring the environment to ensure continued stability. We will share further updates as more information becomes available.
The platform remains stable following the implemented solution, with no widespread issues observed. We are continuing to monitor the environment while investigating a small number of residual errors affecting a limited set of stores. Our teams remain actively engaged to ensure full stability and will provide another update within 30 minutes or sooner if needed.
We have identified an issue affecting the search functionality and have implemented additional mitigation measures. The platform remains stable, and our teams are closely monitoring the environment to ensure the effectiveness of the applied actions. We will provide further updates as more information becomes available.
The platform remains stable and operating as expected following the mitigation actions. At this time, only a very small number of stores are experiencing isolated errors, with minimal impact. Our teams are actively working to fully resolve these residual issues and ensure complete stability.
We continue to monitor the platform, which remains stable. A small number of stores may still experience isolated errors with minimal impact. We will provide further updates as more information becomes available.
System performance remains within expected levels. A small number of isolated errors continue to affect a limited set of stores, with low overall impact. We will share the next update as soon as there are meaningful developments.
We continue to observe a small number of errors affecting some stores. Our teams remain actively working to ensure full stability.
We are still observing a very small and intermittent issue affecting product search for a limited number of stores, with minimal overall impact. Our teams continue to monitor the platform.We will share the next update as soon as new information becomes available.
This incident has been resolved. We will provide further information in a public incident report. **Summary** On Mar 20, 2026, from 19:38 to Mar 21, 2026, 04:19 UTC, affected stores experienced intermittent instability impacting storefront availability and product search. During this period, some users encountered degraded performance, including increased latency, intermittent errors, page loading failures, and occasional difficulty accessing specific storefront pages. The incident was caused by cache-related issues that led to broader platform instability. Mitigation actions were applied to stabilize the environment, followed by continuous monitoring to ensure full recovery. The sales flow was partially and intermittently impacted for a limited number of accounts over a period of approximately 8 hours and 41 minutes. We apologize for any inconvenience this may have caused.
We are currently investigating an issue in FastStore WebOps. A subset of clients could be experiencing issues seeing FastStore WebOps deployments. Our incident response team is working to identify the root cause and implement a solution. We will send an additional update as soon as we have more information to share.
The fix for the issue in FastStore WebOps has been implemented. Affected accounts should no longer be experiencing issues seeing FastStore deployments. Our incident response team is monitoring to guarantee that normal platform behavior is fully reestablished. We will send an additional update in the next 30 minutes, or as soon as we have more information to share.
This incident has been resolved. **Summary** In this incident, affected accounts experienced issues seeing FastStore deployments. During this incident period, most deployments failed, meaning it was not possible to make changes to published storefronts. Our sales flow was unaffected during this incident, but storefront updates for a few accounts using FastStore WebOps was impacted in this period. We apologize for any inconvenience this may have caused.
We are currently investigating an issue in Intelligent Search. The affected accounts may be experiencing issues where searches are not returning products. Our incident response team is working to identify the root cause and implement a solution. We will send an additional update in the next 30 minutes, or as soon as we have more information to share.
The fix for the issue in Intelligent Search has been implemented. Affected accounts should begin seeing their products gradually return in search results. Our incident response team is monitoring to guarantee that normal platform behavior is fully reestablished. We will send an additional update in the next 30 minutes, or as soon as we have more information to share.
Our incident response team is still monitoring to guarantee that normal platform behavior is fully reestablished. We will send an additional update in the next 30 minutes, or as soon as we have more information to share.
**Summary** On February 20, 2026, from 18:33 to 19:22 UTC, affected accounts experienced an issue where search was not returning products. The incident was triggered by a configuration issue in Intelligent Search. We mitigated the impact by restoring the system configuration. The sales flow was partially affected during this period, impacting some accounts for approximately 49 minutes. We apologize for any inconvenience this may have caused.
We are currently investigating an issue in Intelligent Search. The affected accounts may be experiencing issues where searches are not returning products. Our incident response team is working to identify the root cause and implement a solution. We will send an additional update in the next 30 minutes, or as soon as we have more information to share.
The fix for the issue in Intelligent Search has been implemented. Affected accounts should begin seeing their products gradually return in search results. Our incident response team is monitoring to guarantee that normal platform behavior is fully reestablished. We will send an additional update in the next 30 minutes, or as soon as we have more information to share.
This incident has been resolved. **Summary** On February 11, 2026, from 14:14 to 14:55 UTC, affected accounts experienced an issue where search was not returning products. The incident was triggered by a configuration issue in Intelligent Search. We mitigated the impact by restoring the system configuration. The sales flow was partially affected during this period, impacting some accounts for approximately 41 minutes. We apologize for any inconvenience this may have caused.
We are currently investigating an issue in our Checkout. Affected Accounts may be experiencing errors when trying to purchase orders. Our incident response team is working to identify the root cause and implement a solution. We will send an additional update in the next 30 minutes, or as soon as we have more information to share.
The fix for the issue in our Checkout has been implemented. Affected Accounts should no longer be experiencing errors when trying to purchase orders. Our incident response team is monitoring to guarantee that normal platform behavior is fully reestablished. We will send an additional update in the next 30 minutes, or as soon as we have more information to share.
This incident has been resolved. We will not provide further information in a public incident report. **Summary** On Feb 02, 2026, from 19:15 to 19:33 UTC, affected accounts encountered errors when attempting to place orders. The incident was caused by a degradation in one of our internal infrastructure components. The platform stabilized shortly after, and no further impact was observed. Our sales flow was affected during this incident, impacting most accounts for 19 minutes. We apologize for any inconvenience this may have caused.
We are currently investigating an issue in our Checkout Module. A subset of customers may be experiencing errors when trying to place orders. Our incident response team is working to identify the root cause and implement a solution. We will send an additional update in the next 30 minutes, or as soon as we have more information to share.
This incident has been resolved. We will provide further information in a public incident report. **Summary** On Jan 29, 2026, from 19:55 to 20:21 UTC a subset of customers experienced checkout errors. This incident was caused by an internal deployment issue that temporarily affected checkout service behavior. The situation was mitigated through manual intervention, restoring normal service levels. Our sales flow was partially affected during this incident, impacting a subset of customers for 26 minutes. We apologize for any inconvenience this may have caused.