Historia awarii Vtex

1. 27 października 2026 23:44 UTCresolved

   Status: rozwiązany Ten incydent został rozwiązany. Dostarczymy dalszych informacji w raporcie o incydencie publicznym. Podsumowanie dotyczące 27 października 2026 r., sprawozdania finansowe, w których zmieniono ceny, nie odzwierciedlały aktualizacji cen w sklepach. Ten incydent został wywołany przez wewnętrzną aktualizację usług. Zminimalizowaliśmy jego wpływ poprzez wprowadzenie rozwiązania dla modułu cenowego i skorygowanie wszystkich zmian cen. Podczas tego incydentu nasz przepływ sprzedaży nie uległ zmianie. Przepraszamy za wszelkie niedogodności. Elementy dotknięte Obliczanie cen (operacyjne)

Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.

1. 21 października 2026 17: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. 21 października 2026 00:34 UTCresolved

   Status: W dniu 21 października 2026 r., od 00: 03 do 00: 34 UTC, systemy i integracje, które mają Master Data jako zależność, doświadczyły wyższego niż zwykle poziomu błędu. Podczas tego incydentu, nasz globalny przepływ sprzedaży został częściowo dotknięty. Przepraszamy za wszelkie niedogodności. Dostosowane komponenty Dane główne (operacyjne)

Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.

1. 20 października 2026 21:24 UTCresolved

   Status: rozwiązany Ten incydent został rozwiązany. Podsumowanie: 20 października 2026 roku, niektóre sklepy na VTEX IO doświadczyły zwiększonych błędów i awarii obciążenia, a niektórzy klienci doświadczyli błędów nawigacyjnych. Nasz przepływ sprzedaży był minimalny i pośredni, wpływając na niektóre konta. Przepraszamy za wszelkie niedogodności. Elementy dotknięte VTEX IO (operacyjne)

Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.

1. 25 września 2026 16:18 UTCresolved

   Status: rozwiązany Ten incydent został rozwiązany. Nie dostarczymy dalszych informacji w raporcie o incydentach publicznych. Podsumowanie: 25 września 2026 r., od 14: 19 do 15: 25 UTC, mała liczba kont doświadczyła błędów renderowania i błędów ProxyTimeout podczas dostępu do VTEX Admin poprzez środowiska myvtex. Ten incydent został wywołany przez wewnętrzną aktualizację usług. Złagodziliśmy jego wpływ, cofając aktualizację, przywracając poprzednie stabilne zachowanie. Podczas tego incydentu nasz przepływ sprzedaży nie uległ zmianie. Przepraszamy za wszelkie niedogodności. Dopracowane komponenty Operacje adminowe (operacyjne)

Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.

1. 10 września 2026 14:45 UTCresolved

   Status: rozwiązany Ten incydent został rozwiązany. Nie dostarczymy dalszych informacji w raporcie o incydentach publicznych. Podsumowanie 10 września 2026 r., od 13: 00 UTC do 14: 30 UTC, dotknięte konta wystąpiły błędy podczas wykonywania operacji w panelu administracyjnym kampanii i dostępu do analizy wydajności. Incydent został złagodzony, a platforma działa. Klienci mogą jednak nadal doświadczać pewnego pozostałego opóźnienia lub sporadycznych przerw do końca dnia, ponieważ platforma kończy odzyskiwanie. Podczas tego incydentu nasz przepływ sprzedaży nie uległ zmianie. Przepraszamy za wszelkie niedogodności. Dopracowane komponenty Operacje adminowe (operacyjne)

Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.

1. 17 sierpnia 2026 23:28 UTCresolved

   Status: rozwiązany Ten incydent został rozwiązany. Podsumowanie dotyczące 17 sierpnia 2026 r., z 22: 38 do 23: 04 UTC, systemy i integracje, które mają Master Data jako zależność, doświadczyły wyższego niż zwykle poziomu błędu. Podczas tego incydentu, nasz globalny przepływ sprzedaży został częściowo dotknięty, jak w scenariuszach punktów odbioru. Przepraszamy za wszelkie niedogodności. Dostosowane komponenty Dane główne (operacyjne)

Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.

1. 7 sierpnia 2026 03: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. 16 czerwca 2026 19: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. 16 czerwca 2026 19: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. 16 czerwca 2026 19: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. 14 maja 2026 14:16 UTCinvestigating

   Obecnie badamy problem wpływający na przepływ po zakupie. Dotknięci użytkownicy mogą zobaczyć, że zamówienia utknęły w określonym stanie, a aktualizacje nie postępują zgodnie z oczekiwaniami. Nasz zespół reagowania na incydenty pracuje nad zidentyfikowaniem przyczyny i wdrożeniem rozwiązania. W ciągu najbliższych 30 minut wyślemy dodatkową aktualizację lub jak tylko będziemy mieli więcej informacji do przekazania.

2. 14 maja 2026 14:39 UTCmonitoring

   Zastosowano rozwiązanie problemu wpływającego na przepływ po zakupie. Dotknięte sklepy nie powinny już mieć doświadczenia w zamówieniach i są obecnie przetwarzane. Nasz zespół reagowania na incydenty monitoruje, aby zagwarantować, że normalne zachowanie platformy jest w pełni przywrócone. W ciągu najbliższych 30 minut wyślemy dodatkową aktualizację lub jak tylko będziemy mieli więcej informacji do przekazania.

3. 14 maja 2026 14:51 UTCresolved

   Ten incydent został rozwiązany. / Podsumowanie W tym incydencie niektórzy kupcy doświadczyli problemów związanych z zarządzaniem zamówieniami, szczególnie w przetwarzaniu statusu zamówień. Ten incydent nie wpłynął bezpośrednio na klientów, tylko na przetwarzanie zamówień po zakupie. Przepraszamy za wszelkie niedogodności.

Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.

1. 14 maja 2026 06: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. 14 maja 2026 07: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. 14 maja 2026 07: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. 14 maja 2026 07: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. 14 maja 2026 08: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. 9 maja 2026 16:16 UTCinvestigating

   Badamy kwestię wpływającą na dostępność czeków. Sprzedaż może być częściowo naruszona, a problemem jest również wpływ na nawigację sklepową i stabilność sesji dla użytkowników dostępu do sklepów za pośrednictwem portalu Legacy. Prześlemy dodatkową aktualizację w ciągu najbliższych 30 minut lub jak tylko będziemy mieli więcej informacji do przekazania.

2. 9 maja 2026 16:49 UTCmonitoring

   Monitorujemy usługi wymeldowania po zastosowaniu korekt. W tym czasie sprzedaż może być częściowo naruszona, jak również nawigacja sklepu PDP, tylko dla klientów dostępu do sklepów za pośrednictwem portalu Legacy. Prześlemy dodatkową aktualizację w ciągu najbliższych 30 minut lub jak tylko będziemy mieli więcej informacji do przekazania.

3. 9 maja 2026 17:05 UTCresolved

   Ten incydent został rozwiązany. Streszczenie Usługi wymeldowania zostały w pełni znormalizowane o 16: 34 UTC, a nawigacja sklepu PDP (Legacy Portal) o 16: 43 UTC.

Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.

1. 9 maja 2026 07: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. 9 maja 2026 07: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. 14 kwietnia 2026 21: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. 14 kwietnia 2026 22: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. 14 kwietnia 2026 22: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. 20 marca 2026 20: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. 20 marca 2026 21: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. 20 marca 2026 21: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. 20 marca 2026 22: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. 20 marca 2026 22: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. 20 marca 2026 23: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. 20 marca 2026 23: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. 21 marca 2026 00: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. 21 marca 2026 00: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. 21 marca 2026 01: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. 21 marca 2026 02: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. 21 marca 2026 02: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. 21 marca 2026 03:26 UTCmonitoring

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

14. 21 marca 2026 04: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. 21 marca 2026 04: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. 6 marca 2026 16: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. 6 marca 2026 16: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. 6 marca 2026 17: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. 20 lutego 2026 19: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. 20 lutego 2026 19: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. 20 lutego 2026 20: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. 20 lutego 2026 20: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. 11 lutego 2026 14: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. 11 lutego 2026 14: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. 11 lutego 2026 15: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. 2 lutego 2026 19: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. 2 lutego 2026 19: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. 2 lutego 2026 20: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. 29 stycznia 2026 21: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. 29 stycznia 2026 21: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.