Störungsverlauf von Vtex

1. 27. Oktober 2026 um 23:44 UTCresolved

   Status: gelöst Dieser Vorfall wurde behoben. Wir werden weitere Informationen in einem öffentlichen Vorfallsbericht zur Verfügung stellen. Zusammenfassung Am 27. Oktober 2026 erlebten Konten, die die Preise änderten, Preisupdates, die nicht an der Ladenfront reflektiert wurden. Dieser Vorfall wurde durch ein internes Service-Update ausgelöst. Wir haben seine Auswirkungen gemildert, indem wir einen Fix für das Preismodul implementiert und alle betroffenen Preisänderungen korrigiert haben. Unser Verkaufsfluss war während dieses Vorfalls nicht betroffen. Wir entschuldigen uns für alle Unannehmlichkeiten, die dies verursacht haben könnte. Betroffene Komponenten Preisberechnung (Operational)

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 21. Oktober 2026 um 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. Oktober 2026 um 00:34 UTCresolved

   Status: Gelöst Am 21. Oktober 2026, von 00:03 bis 00:34 UTC, erlebten Systeme und Integrationen, die Stammdaten als Abhängigkeit haben, eine höhere Fehlerrate als üblich. Während dieses Vorfalls war unser globaler Verkaufsfluss teilweise betroffen. Wir entschuldigen uns für alle Unannehmlichkeiten, die dies verursacht haben könnte. Betroffene Komponenten Stammdaten (Operational)

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 20. Oktober 2026 um 21:24 UTCresolved

   Status: gelöst Dieser Vorfall wurde behoben. Zusammenfassung Am 20. Oktober 2026 erlebten einige Storefronts auf VTEX IO erhöhte Fehler und Seitenladefehler, und einige Käufer erlebten Fehler beim Navigieren. Unser Verkaufsfluss war während dieses Vorfalls minimal und indirekt betroffen, was sich auf einige Konten auswirkte. Wir entschuldigen uns für alle Unannehmlichkeiten, die dies verursacht haben könnte. Betroffene Komponenten VTEX IO (Operational)

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 25. September 2026 um 16:18 UTCresolved

   Status: gelöst Dieser Vorfall wurde behoben. Wir werden keine weiteren Informationen in einem öffentlichen Vorfallsbericht bereitstellen. Zusammenfassung Am 25. September 2026, von 14:19 bis 15:25 UTC, gab es bei einer kleinen Anzahl von Konten Rendering- und ProxyTimeout-Fehler beim Zugriff auf den VTEX-Admin über myvtex-Umgebungen. Dieser Vorfall wurde durch ein internes Service-Update ausgelöst. Wir haben seine Auswirkungen gemildert, indem wir das Update rückgängig gemacht und das vorherige stabile Verhalten wiederhergestellt haben. Unser Verkaufsfluss war während dieses Vorfalls nicht betroffen. Wir entschuldigen uns für alle Unannehmlichkeiten, die dies verursacht haben könnte. Betroffene Komponenten Admin Operations (Operational)

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 10. September 2026 um 14:45 UTCresolved

   Status: gelöst Dieser Vorfall wurde behoben. Wir werden keine weiteren Informationen in einem öffentlichen Vorfallsbericht bereitstellen. Zusammenfassung Am 10. September 2026, von 13:00 Uhr UTC bis 14:30 Uhr UTC, hatten die betroffenen Konten Fehler bei der Ausführung von Operationen im Kampagnen-Admin-Panel und beim Zugriff auf Performance-Analysen. Der Vorfall wurde gemildert und die Plattform ist derzeit in Betrieb. Kunden können jedoch noch einige Restlatenz oder gelegentliche Timeouts bis zum Ende des Tages erleben, wenn die Plattform ihre Wiederherstellung abgeschlossen hat. Unser Verkaufsfluss war während dieses Vorfalls nicht betroffen. Wir entschuldigen uns für alle Unannehmlichkeiten, die dies verursacht haben könnte. Betroffene Komponenten Admin Operations (Operational)

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 17. August 2026 um 23:28 UTCresolved

   Status: gelöst Dieser Vorfall wurde behoben. Zusammenfassung Am 17. August 2026, von 22:38 bis 23:04 UTC, erlebten Systeme und Integrationen, die Stammdaten als Abhängigkeit haben, eine höhere Fehlerrate als üblich. Während dieses Vorfalls war unser globaler Verkaufsfluss teilweise betroffen, wie in Pickup-Punkte-Szenarien. Wir entschuldigen uns für alle Unannehmlichkeiten, die dies verursacht haben könnte. Betroffene Komponenten Stammdaten (Operational)

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 7. August 2026 um 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. Juni 2026 um 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. Juni 2026 um 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. Juni 2026 um 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. Mai 2026 um 14:16 UTCinvestigating

   Wir untersuchen derzeit ein Problem, das den Post-Kauffluss beeinflusst. Betroffene Benutzer können sehen, dass Bestellungen in einem bestimmten Status stecken bleiben, wobei Updates nicht wie erwartet voranschreiten. Unser Incident Response Team arbeitet daran, die Ursache zu identifizieren und eine Lösung zu implementieren. Wir werden in den nächsten 30 Minuten ein zusätzliches Update senden, oder sobald wir weitere Informationen zu teilen haben.

2. 14. Mai 2026 um 14:39 UTCmonitoring

   Der Fix für das Problem, das den Post-Kauf-Flow beeinflusst, wurde implementiert. Betroffene Geschäfte sollten nicht mehr in Bestellungen stecken bleiben und werden jetzt verarbeitet. Unser Incident Response Team überwacht, um sicherzustellen, dass das normale Plattformverhalten vollständig wiederhergestellt wird. Wir werden in den nächsten 30 Minuten ein zusätzliches Update senden, oder sobald wir weitere Informationen zu teilen haben.

3. 14. Mai 2026 um 14:51 UTCresolved

   Dieser Vorfall wurde behoben. **Zusammenfassung** Bei diesem Vorfall hatten einige Händler Probleme mit dem Auftragsmanagement, insbesondere bei der Verarbeitung des Auftragsstatus-Workflows. Käufer waren von diesem Vorfall nicht direkt betroffen, nur die Bearbeitung nach dem Kauf war betroffen. Wir entschuldigen uns für alle Unannehmlichkeiten, die dies verursacht haben könnte.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 14. Mai 2026 um 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. Mai 2026 um 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. Mai 2026 um 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. Mai 2026 um 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. Mai 2026 um 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. Mai 2026 um 16:16 UTCinvestigating

   Wir untersuchen ein Problem, das die Verfügbarkeit von Checkouts beeinflusst. Der Verkauf kann teilweise betroffen sein, und ein Problem wirkt sich auch auf die Store-Navigation und die Sitzungsstabilität für Benutzer aus, die über das Legacy-Portal auf Stores zugreifen. Wir werden innerhalb der nächsten 30 Minuten ein zusätzliches Update senden oder sobald wir weitere Informationen zu teilen haben.

2. 9. Mai 2026 um 16:49 UTCmonitoring

   Wir überwachen die Checkout-Services, nachdem die Anpassungen vorgenommen wurden. Zu diesem Zeitpunkt können Verkäufe teilweise betroffen sein, ebenso wie die PDP-Store-Navigation, nur für Kunden, die über das Legacy-Portal auf Geschäfte zugreifen. Wir werden innerhalb der nächsten 30 Minuten ein zusätzliches Update senden oder sobald wir weitere Informationen zu teilen haben.

3. 9. Mai 2026 um 17:05 UTCresolved

   Dieser Vorfall wurde behoben. Zusammenfassung Die Checkout-Dienste wurden um 16:34 UTC vollständig normalisiert und die PDP-Store-Navigation (Legacy Portal) wurde um 16:43 UTC vollständig normalisiert.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 9. Mai 2026 um 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. Mai 2026 um 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. April 2026 um 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. April 2026 um 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. April 2026 um 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. März 2026 um 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. März 2026 um 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. März 2026 um 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. März 2026 um 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. März 2026 um 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. März 2026 um 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. März 2026 um 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. März 2026 um 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. März 2026 um 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. März 2026 um 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. März 2026 um 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. März 2026 um 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. März 2026 um 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. März 2026 um 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. März 2026 um 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. März 2026 um 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. März 2026 um 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. März 2026 um 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. Februar 2026 um 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. Februar 2026 um 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. Februar 2026 um 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. Februar 2026 um 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. Februar 2026 um 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. Februar 2026 um 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. Februar 2026 um 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. Februar 2026 um 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. Februar 2026 um 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. Februar 2026 um 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. Januar 2026 um 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. Januar 2026 um 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.