Vtex driftsforstyrrelser

1. 27. oktober 2026 kl. 23.44 UTCresolved

   Status: Opløst Denne hændelse er blevet løst. Vi vil give yderligere oplysninger i en rapport om en offentlig hændelse. Oversigt over 27 okt 2026, konti, der ændrede priser oplevede prisopdateringer ikke afspejles på butiksfronten. Denne hændelse blev udløst af en intern serviceopdatering. Vi mindskede dens virkning ved at implementere en rettelse til prismodulet og korrigere alle berørte prisændringer. Vores salgsstrøm blev ikke påvirket under denne hændelse. Vi undskylder for eventuelle ulemper. Berørte komponenter Prisberegning (operationel)

Automatisk oversat fra den officielle hændelsesopdatering.

1. 21. oktober 2026 kl. 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 kl. 00.34 UTCresolved

   Status: Resolved On Oktober 21, 2026, fra 00: 03 til 00: 34 UTC, systemer og integreringer, der har Master Data som en afhængighed oplevet en højere fejlrate end normalt. Under denne hændelse blev vores globale salgsstrøm delvist påvirket. Vi undskylder for eventuelle ulemper. Berørte komponenter Master Data (Operationel)

Automatisk oversat fra den officielle hændelsesopdatering.

1. 20. oktober 2026 kl. 21.24 UTCresolved

   Status: Opløst Denne hændelse er blevet løst. Oversigt på oktober 20, 2026, nogle butiksmeddelelser på VTEX IO oplevede forhøjede fejl og sidebelastningssvigt, og nogle kunder oplevede fejl navigation. Vores salgsstrøm var minimal og indirekte påvirket under denne hændelse, påvirker nogle konti. Vi undskylder for eventuelle ulemper. Berørte komponenter VTEX IO (operationel)

Automatisk oversat fra den officielle hændelsesopdatering.

1. 25. september 2026 kl. 16.18 UTCresolved

   Status: Opløst Denne hændelse er blevet løst. Vi vil ikke give yderligere oplysninger i en rapport om en offentlig hændelse. Oversigt over 25 Sep, 2026, fra 14: 19 til 15: 25 UTC, et lille antal konti oplevede rendering fejl og ProxyTimeout fejl, når adgang til VTEX Admin gennem myvtex miljøer. Denne hændelse blev udløst af en intern serviceopdatering. Vi mindskede dens virkning ved at vende opdateringen, genoprette den tidligere stabile adfærd. Vores salgsstrøm var upåvirket under denne hændelse. Vi undskylder for eventuelle ulemper. Berørte komponenter Admin-operationer (operationelle)

Automatisk oversat fra den officielle hændelsesopdatering.

1. 10. september 2026 kl. 14.45 UTCresolved

   Status: Opløst Denne hændelse er blevet løst. Vi vil ikke give yderligere oplysninger i en rapport om en offentlig hændelse. Oversigt Den 10. september 2026, fra 13: 00 UTC til 14: 30 UTC, berørte konti oplevet fejl, når de udfører operationer i kampagnen admin panel og adgang til performance analytics. Hændelsen er blevet afbødet, og platformen er i øjeblikket operationel. Men kunderne kan stadig opleve nogle resterende latency eller lejlighedsvis timeouts indtil slutningen af dagen, som platformen fuldfører sin inddrivelse. Vores salgsstrøm blev ikke påvirket under denne hændelse. Vi undskylder for eventuelle ulemper. Berørte komponenter Admin-operationer (operationelle)

Automatisk oversat fra den officielle hændelsesopdatering.

1. 17. august 2026 kl. 23.28 UTCresolved

   Status: Opløst Denne hændelse er blevet løst. Oversigt På August 17, 2026, fra 22: 38 til 23: 04 UTC, systemer og integration, der har Master Data som en afhængighed oplevet en højere fejlrate end normalt. Under denne hændelse blev vores globale salgsstrøm delvist påvirket, såsom i pickup points scenarier. Vi undskylder for eventuelle ulemper. Berørte komponenter Master Data (Operationel)

Automatisk oversat fra den officielle hændelsesopdatering.

1. 7. august 2026 kl. 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 kl. 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 kl. 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 kl. 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. maj 2026 kl. 14.16 UTCinvestigating

   Vi undersøger i øjeblikket et problem, der påvirker efterkøbsstrømmen. Berørte brugere kan se ordrer sidder fast i en bestemt status, med opdateringer ikke skrider som forventet. Vores team arbejder på at identificere årsagen og gennemføre en løsning. Vi sender en yderligere opdatering inden for de næste 30 minutter, eller så snart vi har mere information at dele.

2. 14. maj 2026 kl. 14.39 UTCmonitoring

   Løsningen for det problem, der påvirker post køb flow er blevet gennemført. Berørte butikker bør ikke længere være fanget i ordrer og behandles nu. Vores hold overvåger, at normal adfærd genetableres. Vi sender en yderligere opdatering inden for de næste 30 minutter, eller så snart vi har mere information at dele.

3. 14. maj 2026 kl. 14.51 UTCresolved

   Denne hændelse er blevet løst. * * Oversigt * * I denne hændelse nogle handlende oplevet problemer i ordrestyring, især i behandling af ordrer status workflow. Shoppers blev ikke direkte påvirket af denne hændelse, kun post-køb ordre behandling blev påvirket. Vi undskylder for eventuelle ulemper.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 14. maj 2026 kl. 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. maj 2026 kl. 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. maj 2026 kl. 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. maj 2026 kl. 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. maj 2026 kl. 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. maj 2026 kl. 16.16 UTCinvestigating

   Vi undersøger et problem, der påvirker adgang til check-out. Salg kan blive delvist påvirket, og et problem er også påvirke butik navigation og session stabilitet for brugere adgang butikker via Legacy Portal. Vi sender en yderligere opdatering inden for de næste 30 minutter eller så snart vi har mere information at dele.

2. 9. maj 2026 kl. 16.49 UTCmonitoring

   Vi overvåger kontroltjenesterne, efter at tilpasningerne er gennemført. På dette tidspunkt, salg kan være delvist påvirket, samt PDP butik navigation, kun for kunder adgang butikker gennem Legacy Portal. Vi sender en yderligere opdatering inden for de næste 30 minutter eller så snart vi har mere information at dele.

3. 9. maj 2026 kl. 17.05 UTCresolved

   Denne hændelse er blevet løst. Oversigt Checkout tjenester blev fuldt normaliseret på 16: 34 UTC og PDP butik navigation (Legacy Portal) tjenester blev fuldt normaliseret på 16: 43 UTC.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 9. maj 2026 kl. 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. maj 2026 kl. 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 kl. 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 kl. 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 kl. 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. marts 2026 kl. 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. marts 2026 kl. 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. marts 2026 kl. 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. marts 2026 kl. 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. marts 2026 kl. 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. marts 2026 kl. 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. marts 2026 kl. 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. marts 2026 kl. 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. marts 2026 kl. 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. marts 2026 kl. 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. marts 2026 kl. 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. marts 2026 kl. 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. marts 2026 kl. 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. marts 2026 kl. 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. marts 2026 kl. 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. marts 2026 kl. 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. marts 2026 kl. 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. marts 2026 kl. 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 kl. 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 kl. 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 kl. 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 kl. 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 kl. 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 kl. 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 kl. 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 kl. 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 kl. 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 kl. 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 kl. 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 kl. 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.