Vtex 장애 기록

1. 2026년 10월 27일 오후 11:44 UTCresolved

   상태: 해결 이 사건은 해결되었습니다. 우리는 공공 사건 보고서에 더 많은 정보를 제공 할 것입니다. 요약 10월 27, 2026, 가격이 책정 된 가격의 업데이트를 변경하는 계정은 storefront에 반영되지 않습니다. 이 사건은 내부 서비스 업데이트에 의해 트리거되었습니다. 우리는 가격 모듈에 대한 수정을 구현하고 모든 영향을받는 가격 변경을 수정하여 영향을 미쳤습니다. 우리의 영업 흐름은이 사건에 영향을 미치지 않았습니다. 우리는이 발생 할 수있는 불편에 대해 사과합니다. Affected 부품 가격 계산 (Operational)

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 10월 21일 오후 5:13 UTCresolved

   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)

1. 2026년 10월 21일 오전 12:34 UTCresolved

   상태 : 10 월 21, 2026에 해결, 00 : 03에서 00 : 34 UTC, 시스템 및 통합은 일반적으로 오류율보다 높은 경험으로 Master Data를 가지고. 이 사건 도중, 우리의 세계적인 판매 교류는 부분적으로 영향을 미쳤습니다. 우리는이 발생 할 수있는 불편에 대해 사과합니다. 완전한 구성 요소 마스터 데이터 (Operational)

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 10월 20일 오후 9:24 UTCresolved

   상태: 해결 이 사건은 해결되었습니다. 10 월 20, 2026에 대한 개요, VTEX IO의 일부 저장소는 높은 오류와 페이지로드 실패를 경험, 일부 구매자 경험 오류 항해. 우리의 영업 흐름은이 사건 중 최소 및 간접 영향을 받았으며 일부 계정에 영향을 미쳤습니다. 우리는이 발생 할 수있는 불편에 대해 사과합니다. 부품 VTEX IO (Operational)

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 9월 25일 오후 4:18 UTCresolved

   상태: 해결 이 사건은 해결되었습니다. 우리는 공공 사건 보고서에 더 많은 정보를 제공하지 않습니다. 요약 9월 25, 2026, from 14:19 to 15:25 UTC, myvtex 환경을 통해 VTEX 관리자에 액세스 할 때 경험있는 렌더링 오류 및 ProxyTimeout 오류의 작은 숫자. 이 사건은 내부 서비스 업데이트에 의해 트리거되었습니다. 우리는 업데이트, 이전의 안정적인 행동을 복원하여 영향을 미쳤습니다. 우리의 영업 흐름은이 사건 중 비범했다. 우리는이 발생 할 수있는 불편에 대해 사과합니다. 부품 관리 운영 (Operational)

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 9월 10일 오후 2:45 UTCresolved

   상태: 해결 이 사건은 해결되었습니다. 우리는 공공 사건 보고서에 더 많은 정보를 제공하지 않습니다. 요약 9 월 10 일, 2026, 13 : 00 UTC에서 14:30 UTC, 캠페인 관리자 패널 및 액세스 성능 분석에서 작업을 수행 할 때 영향 계정 경험 오류. 사건은 mitigated이고, 플랫폼은 현재 가동입니다. 그러나 고객은 여전히 플랫폼이 복구를 완료하기 위해 하루의 끝까지 일부 잔여 대기 시간 또는 가끔의 타임 아웃을 경험할 수 있습니다. 우리의 영업 흐름은이 사건에 영향을 미치지 않았습니다. 우리는이 발생 할 수있는 불편에 대해 사과합니다. 부품 관리 운영 (Operational)

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 8월 17일 오후 11:28 UTCresolved

   상태: 해결 이 사건은 해결되었습니다. 요약 8월 17, 2026, 부터 22:38 에 23:04 UTC, 시스템 및 통합 마스터 데이터는 일반적으로 오류율보다 더 높은 경험. 이 사건 도중, 우리의 세계적인 판매 교류는 픽업 점 대본과 같은 부분적으로 영향을 미쳤습니다. 우리는이 발생 할 수있는 불편에 대해 사과합니다. 완전한 구성 요소 마스터 데이터 (Operational)

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 8월 7일 오전 3:08 UTCmonitoring

   **[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.

1. 2026년 6월 16일 오후 7:22 UTCinvestigating

   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.

2. 2026년 6월 16일 오후 7:32 UTCmonitoring

   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.

3. 2026년 6월 16일 오후 7:49 UTCresolved

   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.

1. 2026년 5월 14일 오후 2:16 UTCinvestigating

   우리는 현재 게시물 구매 흐름에 영향을 미치는 문제점을 조사하고 있습니다. 수정된 사용자는 특정 상태에 갇힌 주문을 볼 수 있으며, 업데이트는 예상대로 진행되지 않습니다. 우리의 사건 응답 팀은 뿌리 원인을 확인하고 해결책을 실행하기 위하여 일하고 있습니다. 우리는 다음 30 분에 추가 업데이트를 보낼 것입니다, 또는 우리가 공유하는 더 많은 정보가 있기 때문에.

2. 2026년 5월 14일 오후 2:39 UTCmonitoring

   게시물 구매 흐름에 영향을 미치는 문제에 대한 수정이 구현되었습니다. 해당 매장은 더 이상 주문에 갇히지 않아 처리되고 있습니다. 우리의 사건 응답 팀은 정상적인 플랫폼 행동이 완전히 reestablished 보장하기 위하여 감시 입니다. 우리는 다음 30 분에 추가 업데이트를 보낼 것입니다, 또는 우리가 공유하는 더 많은 정보가 있기 때문에.

3. 2026년 5월 14일 오후 2:51 UTCresolved

   이 사건은 해결되었습니다. ** 일정 ** 이 사건에서 몇몇 상인은 순서 관리에 있는 문제점을 경험했습니다, 특히 순서 상태 워크플로우 가공에서. Shoppers는이 사건에 의해 직접 영향을받지 않았으며, 포스트 구매 주문 처리 만 영향을 받았습니다. 우리는이 발생 할 수있는 불편에 대해 사과합니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 5월 14일 오전 6:36 UTCinvestigating

   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.

2. 2026년 5월 14일 오전 7:09 UTCinvestigating

   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.

3. 2026년 5월 14일 오전 7:40 UTCinvestigating

   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.

4. 2026년 5월 14일 오전 7:54 UTCmonitoring

   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.

5. 2026년 5월 14일 오전 8:06 UTCresolved

   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.

1. 2026년 5월 9일 오후 4:16 UTCinvestigating

   우리는 checkout 가용성에 영향을 미치는 문제점을 조사하고 있습니다. 판매는 부분적으로 영향을 미칠 수 있으며, 발급은 Legacy Portal을 통해 매장에 접근하는 사용자를 위한 매장 내비게이션 및 세션 안정성에 영향을 미칩니다. 우리는 다음 30 분 이내에 추가 업데이트를 보내거나 우리가 공유하는 더 많은 정보가 있기 때문에 곧.

2. 2026년 5월 9일 오후 4:49 UTCmonitoring

   우리는 조정이 적용된 후에 체크 아웃 서비스를 감시하고 있습니다. 이 시간에, 판매는 부분적으로 영향을 미칠 수 있습니다, 뿐만 아니라 PDP 상점 네비게이션, Legacy Portal을 통해 매장에 접근하는 고객만. 우리는 다음 30 분 이내에 추가 업데이트를 보내거나 우리가 공유하는 더 많은 정보가 있기 때문에 곧.

3. 2026년 5월 9일 오후 5:05 UTCresolved

   이 사건은 해결되었습니다. 제품정보 Checkout 서비스는 16:34 UTC 및 PDP 저장소 내비게이션 (Legacy Portal) 서비스에 완전히 정상화되었습니다. 16:43 UTC.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 5월 9일 오전 7:28 UTCmonitoring

   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.

2. 2026년 5월 9일 오전 7:54 UTCresolved

   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.

1. 2026년 4월 14일 오후 9:59 UTCinvestigating

   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.

2. 2026년 4월 14일 오후 10:32 UTCmonitoring

   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.

3. 2026년 4월 14일 오후 10:44 UTCresolved

   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.

1. 2026년 3월 20일 오후 8:48 UTCinvestigating

   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.

2. 2026년 3월 20일 오후 9:19 UTCinvestigating

   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.

3. 2026년 3월 20일 오후 9:56 UTCinvestigating

   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.

4. 2026년 3월 20일 오후 10:28 UTCinvestigating

   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.

5. 2026년 3월 20일 오후 10:55 UTCidentified

   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.

6. 2026년 3월 20일 오후 11:05 UTCmonitoring

   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.

7. 2026년 3월 20일 오후 11:38 UTCmonitoring

   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.

8. 2026년 3월 21일 오전 12:12 UTCmonitoring

   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.

9. 2026년 3월 21일 오전 12:51 UTCmonitoring

   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.

10. 2026년 3월 21일 오전 1:26 UTCmonitoring

    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.

11. 2026년 3월 21일 오전 2:00 UTCmonitoring

    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.

12. 2026년 3월 21일 오전 2:40 UTCmonitoring

    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.

13. 2026년 3월 21일 오전 3:26 UTCmonitoring

    We continue to observe a small number of errors affecting some stores. Our teams remain actively working to ensure full stability.

14. 2026년 3월 21일 오전 4:05 UTCmonitoring

    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.

15. 2026년 3월 21일 오전 4:31 UTCresolved

    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.

1. 2026년 3월 6일 오후 4:06 UTCinvestigating

   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.

2. 2026년 3월 6일 오후 4:43 UTCmonitoring

   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.

3. 2026년 3월 6일 오후 5:08 UTCresolved

   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.

1. 2026년 2월 20일 오후 7:20 UTCinvestigating

   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.

2. 2026년 2월 20일 오후 7:46 UTCmonitoring

   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.

3. 2026년 2월 20일 오후 8:25 UTCmonitoring

   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.

4. 2026년 2월 20일 오후 8:53 UTCresolved

   **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.

1. 2026년 2월 11일 오후 2:49 UTCinvestigating

   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.

2. 2026년 2월 11일 오후 2:57 UTCidentified

   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.

3. 2026년 2월 11일 오후 3:18 UTCresolved

   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.

1. 2026년 2월 2일 오후 7:29 UTCinvestigating

   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.

2. 2026년 2월 2일 오후 7:41 UTCmonitoring

   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.

3. 2026년 2월 2일 오후 8:15 UTCresolved

   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.

1. 2026년 1월 29일 오후 9:15 UTCinvestigating

   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.

2. 2026년 1월 29일 오후 9:15 UTCresolved

   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.