Vtex Outage History

Vtex is up right now

Pingoru has recorded 28 incidents for Vtex: 25 in the last 12 months and 7 in the last 90 days.

Source: status.vtex.com

28incidents recorded
25last 12 months
7last 90 days
2 hourstypical duration
Incidents per month
024AprMayJunJulAugSepOctNov0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOctNov0%
Pingoru began tracking Vtex in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202611 of 720 (0%)
May 202645 of 744 (1%)
June 202611 of 720 (0%)
July 202600 of 744 (0%)
August 202628 of 744 (1%)
September 202622 of 720 (0%)
October 2026418 of 744 (2%)
November 202600 of 184 (0%)

Incidents, newest first

Minor October 27, 2026 Pricing Updates Not Reflected in Production 15h 50m Checkout (Pricing Calculation)

Started Oct 27, 2026, 03:00 AM UTC· resolved Oct 27, 2026, 06:50 PM UTC

  1. identified Oct 27, 2026, 06:22 PM UTC

    We have identified an issue with our Pricing module, where price changes are not being reflected on the storefront. Our incident response team estimates that the fix will be implemented in the next 20 minutes. We will send an additional update in the next 30 minutes, or as soon as we have more information to share.

  2. monitoring Oct 27, 2026, 06:50 PM UTC

    The fix for the issue in our Pricing module has been implemented, and new price changes are now being reflected on the storefront. Prices changed since midnight are still being updated, and our incident response team is working to bring them up to date. Our incident response team is monitoring to ensure 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. monitoring Oct 27, 2026, 07:21 PM UTC

    The fix for the issue in our Pricing module has been implemented, and new price changes are now being reflected on the storefront. Prices changed since midnight are still being updated, and our incident response team is still working to bring them up to date. Our incident response team is monitoring to ensure 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. monitoring Oct 27, 2026, 08:10 PM UTC

    The fix for the issue in our Pricing module has been implemented, and new price changes are now being reflected on the storefront. Prices changed since midnight are still being updated, and our incident response team is still working to bring them up to date. Our incident response team is monitoring to ensure 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. monitoring Oct 27, 2026, 09:00 PM UTC

    The fix for the issue in our Pricing module has been implemented, and new price changes are now being reflected on the storefront. Prices changed since midnight are still being updated, and our incident response team is still working to bring them up to date. Our incident response team is monitoring to ensure normal platform behavior is fully reestablished. We will send an additional update once the correction of affected prices has been completed.

  6. resolved Oct 27, 2026, 11:44 PM UTC

    This incident has been resolved. We will provide further information in a public incident report. Summary On Oct 27, 2026, accounts that changed prices experienced price updates not being reflected on the storefront. This incident was triggered by an internal service update. We mitigated its impact by implementing a fix for the Pricing module and correcting all affected price changes. Our sales flow was not affected during this incident. We apologize for any inconvenience this may have caused.

Read the full incident report →

Critical October 21, 2026 Admin outage 12m Admin (Admin Operations)

Started Oct 21, 2026, 04:53 PM UTC· resolved Oct 21, 2026, 05:05 PM UTC

  1. investigating Oct 21, 2026, 04:53 PM UTC

    We are currently investigating an issue affecting the VTEX Admin. Users may experience a rendering error when trying to access the Admin. 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. monitoring Oct 21, 2026, 05:05 PM UTC

    The fix for the instability in the VTEX Admin has been implemented. Users should no longer be experiencing rendering errors when accessing the Admin. 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. resolved Oct 21, 2026, 05:13 PM UTC

    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.

Read the full incident report →

Minor October 21, 2026 Increase in Master Data errors 31m Developer Tools (Master Data)

Started Oct 21, 2026, 12:03 AM UTC· resolved Oct 21, 2026, 12:34 AM UTC

  1. investigating Oct 21, 2026, 12:03 AM UTC

    We are currently investigating an increase in errors in Master Data. Systems and integrations that have Master Data as a dependency may be experiencing a higher than usual error rate. 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. resolved Oct 21, 2026, 12:34 AM UTC

    On October 21, 2026, from 00:03 to 00:34 UTC, systems and integrations that have Master Data as a dependency experienced a higher than usual error rate. During this incident, our global sales flow was partially affected. We apologize for any inconvenience this may have caused.

Read the full incident report →

Minor October 20, 2026 Increased errors in VTEX IO 1h 39m Developer Tools (VTEX IO)

Started Oct 20, 2026, 07:33 PM UTC· resolved Oct 20, 2026, 09:12 PM UTC

  1. investigating Oct 20, 2026, 07:33 PM UTC

    We are currently investigating an issue in a VTEX IO cluster. Some merchants may be experiencing page loading errors on their storefronts. 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. identified Oct 20, 2026, 08:21 PM UTC

    We have identified the cause of an issue affecting GraphQL queries on some storefronts, which caused page loading errors. Most stores have already returned to normal, and the issue had no significant impact on sales. A small number of stores may still be experiencing the problem, and our team is working to fully resolve it. We will send an additional update in the next 30 minutes, or as soon as we have more information to share.

  3. identified Oct 20, 2026, 08:48 PM UTC

    We are almost returning to pre-incident levels. Our incident response team estimates that gradual recovery will be observed within the next few minutes. We will send an additional update in the next 30 minutes, or as soon as we have more information to share.

  4. monitoring Oct 20, 2026, 09:12 PM UTC

    We are back to normal levels. Merchants should no longer be experiencing errors navigating on their storefronts. 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. resolved Oct 20, 2026, 09:24 PM UTC

    This incident has been resolved. Summary On Oct 20, 2026, some storefronts on VTEX IO experienced elevated errors and page-load failures, and some shoppers experienced errors navigating. Our sales flow was minimal and indirect affected during this incident, impacting some accounts. We apologize for any inconvenience this may have caused.

Read the full incident report →

Minor September 25, 2026 Admin Access Issue 1h 6m Admin (Admin Operations)

Started Sep 25, 2026, 02:19 PM UTC· resolved Sep 25, 2026, 03:25 PM UTC

  1. investigating Sep 25, 2026, 02:50 PM UTC

    We are currently investigating an issue affecting the VTEX Admin. Users may experience a rendering error when trying to access the Admin, receiving a ProxyTimeout error. 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. investigating Sep 25, 2026, 03:20 PM UTC

    We are currently investigating an instability affecting the VTEX Admin. Users may experience a rendering error when trying to access the Admin, receiving a ProxyTimeout error. 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.

  3. monitoring Sep 25, 2026, 03:31 PM UTC

    The fix for the instability in the VTEX Admin has been implemented. Users should no longer be experiencing rendering errors or ProxyTimeout errors when accessing the Admin. 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.

  4. monitoring Sep 25, 2026, 04:03 PM UTC

    The fix for the instability in the VTEX Admin remains in place. Users should not be experiencing rendering errors or ProxyTimeout errors when accessing the Admin. Our incident response team continues 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. resolved Sep 25, 2026, 04:18 PM UTC

    This incident has been resolved. We will not provide further information in a public incident report. Summary On Sep 25, 2026, from 14:19 to 15:25 UTC, a small number of accounts experienced rendering errors and ProxyTimeout 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.

Read the full incident report →

Major September 10, 2026 VTEX Ads outage 52m Admin (Admin Operations)

Started Sep 10, 2026, 01:37 PM UTC· resolved Sep 10, 2026, 02:30 PM UTC

  1. investigating Sep 10, 2026, 01:37 PM UTC

    We are currently investigating an increase in errors in VTEX Ads Operations on the campaign admin panel and performance analytics were affected. Ads continue to be displayed normally. 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. identified Sep 10, 2026, 02:01 PM UTC

    We have identified the contributing factors to the issue in VTEX Ads. Our incident response team is actively working on the fix and expects it to be implemented 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.

  3. identified Sep 10, 2026, 02:21 PM UTC

    The issue affecting VTEX Ads has been mitigated, and customers can now access the campaign admin panel and create new campaigns and related configurations again. Performance metrics are also becoming available, although some data may still appear incomplete while the remaining information is fully restored. The platform is currently operational, but customers may still experience some latency or occasional timeouts during this recovery period. Our incident response team continues to monitor the platform closely and is working to ensure that all data and platform behavior are fully restored. We will send an additional update in the next 30 minutes, or as soon as we have more information to share.

  4. resolved Sep 10, 2026, 02:45 PM UTC

    This incident has been resolved. We will not provide further information in a public incident report. Summary On September 10th, 2026, from 13:00 UTC to 14:30 UTC, affected accounts experienced errors when performing operations in the campaign admin panel and accessing performance analytics. The incident has been mitigated, and the platform is currently operational. However, customers may still experience some residual latency or occasional timeouts until the end of the day as the platform completes its recovery. Our sales flow was not affected during this incident. We apologize for any inconvenience this may have caused.

Read the full incident report →

Minor August 17, 2026 Increase in Master Data errors. 26m Developer Tools (Master Data)

Started Aug 17, 2026, 10:38 PM UTC· resolved Aug 17, 2026, 11:04 PM UTC

  1. investigating Aug 17, 2026, 10:57 PM UTC

    We are currently investigating an increase in errors in Master Data. Systems and integrations that have Master Data as a dependency may be experiencing a higher than usual error rate. 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. monitoring Aug 17, 2026, 11:13 PM UTC

    The fix for the issue in Master Data has been implemented. Stores should no longer be experiencing higher than usual errors in Master Data. 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. resolved Aug 17, 2026, 11:28 PM UTC

    This incident has been resolved. Summary On Aug 17, 2026, from 22:38 to 23:04 UTC, systems and integrations that have Master Data as a dependency experienced a higher than usual error rate. During this incident, our global sales flow was partially affected, such as in pickup points scenarios. We apologize for any inconvenience this may have caused.

Read the full incident report →

Major August 7, 2026 No Observable mesh logs 7h 33m

Started Aug 07, 2026, 03:08 AM UTC· resolved Aug 07, 2026, 10:42 AM UTC

  1. monitoring Aug 07, 2026, 03:08 AM UTC

    [DELETE BEFORE POSTING: Incident template library "Incident template library": https://support.atlassian.com/statuspage/docs/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.

Read the full incident report →

Major June 16, 2026 Faststore service partial outage 1h 20m Storefront (FastStore)

Started Jun 16, 2026, 06:16 PM UTC· resolved Jun 16, 2026, 07:36 PM UTC

  1. investigating Jun 16, 2026, 06:16 PM UTC

    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. monitoring Jun 16, 2026, 07:32 PM UTC

    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. resolved Jun 16, 2026, 07:49 PM UTC

    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.

Read the full incident report →

Major May 14, 2026 Order flow affected post purchase 22m Admin (Order Management)

Started May 14, 2026, 02:16 PM UTC· resolved May 14, 2026, 02:39 PM UTC

  1. investigating May 14, 2026, 02:16 PM UTC

    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. monitoring May 14, 2026, 02:39 PM UTC

    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.

  3. resolved May 14, 2026, 02:43 PM UTC

    This incident has been resolved. Summary In this incident some merchants experienced issues in order management, particularly in processing the orders status workflow. 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.

Read the full incident report →

Major May 14, 2026 Order flow affected post purchase 3h 5m Admin (Order Management)

Started May 14, 2026, 04:49 AM UTC· resolved May 14, 2026, 07:54 AM UTC

  1. investigating May 14, 2026, 04:49 AM UTC

    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. investigating May 14, 2026, 07:09 AM UTC

    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. investigating May 14, 2026, 07:40 AM UTC

    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. monitoring May 14, 2026, 07:54 AM UTC

    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. resolved May 14, 2026, 07:57 AM UTC

    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.

Read the full incident report →

Minor May 9, 2026 Checkout Service Degradation 48m Storefront (Portal/CMS), Checkout (Pricing Calculation), Checkout (Order Placement), Checkout (Shipping Calculation) and 2 more

Started May 09, 2026, 04:16 PM UTC· resolved May 09, 2026, 05:05 PM UTC

  1. investigating May 09, 2026, 04:16 PM UTC

    We are investigating an issue affecting checkout availability. Sales may be partially affected, and an issue is also impacting store navigation and session stability for users accessing stores via the Legacy Portal. We will send an additional update within the next 30 minutes or as soon as we have more information to share.

  2. monitoring May 09, 2026, 04:49 PM UTC

    We are monitoring checkout services after the adjustments have been applied. At this time, sales may be partially affected, as well as PDP store navigation, only for customers accessing stores through the Legacy Portal. We will send an additional update within the next 30 minutes or as soon as we have more information to share.

  3. resolved May 09, 2026, 05:05 PM UTC

    This incident has been resolved. Summary Checkout services were fully normalized at 16:34 UTC and PDP store navigation (Legacy Portal) services were fully normalized at 16:43 UTC.

Read the full incident report →

Minor May 9, 2026 Degraded performance for orders management 26m Admin (Order Management)

Started May 09, 2026, 07:28 AM UTC· resolved May 09, 2026, 07:54 AM UTC

  1. monitoring May 09, 2026, 07:28 AM UTC

    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. resolved May 09, 2026, 07:54 AM UTC

    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.

Read the full incident report →

Minor April 14, 2026 Login Errors 45m Developer Tools (API Integrations)

Started Apr 14, 2026, 09:59 PM UTC· resolved Apr 14, 2026, 10:44 PM UTC

  1. investigating Apr 14, 2026, 09:59 PM UTC

    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. monitoring Apr 14, 2026, 10:32 PM UTC

    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. resolved Apr 14, 2026, 10:44 PM UTC

    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.

Read the full incident report →

Minor March 20, 2026 High error rate in stores 7h 43m Storefront (Store Framework), Storefront (FastStore), Checkout (Order Placement)

Started Mar 20, 2026, 08:48 PM UTC· resolved Mar 21, 2026, 04:31 AM UTC

  1. investigating Mar 20, 2026, 07:38 PM UTC

    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. investigating Mar 20, 2026, 09:19 PM UTC

    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. investigating Mar 20, 2026, 09:56 PM UTC

    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. investigating Mar 20, 2026, 10:28 PM UTC

    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. identified Mar 20, 2026, 10:55 PM UTC

    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. monitoring Mar 20, 2026, 11:05 PM UTC

    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. monitoring Mar 20, 2026, 11:38 PM UTC

    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. monitoring Mar 21, 2026, 12:12 AM UTC

    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. monitoring Mar 21, 2026, 12:51 AM UTC

    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. monitoring Mar 21, 2026, 01:26 AM UTC

    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. monitoring Mar 21, 2026, 02:00 AM UTC

    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. monitoring Mar 21, 2026, 02:40 AM UTC

    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. monitoring Mar 21, 2026, 03:26 AM UTC

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

  14. monitoring Mar 21, 2026, 04:05 AM UTC

    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. resolved Mar 21, 2026, 04:31 AM UTC

    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.

Read the full incident report →

Minor March 6, 2026 FastStore WebOps deployments issues 36m Storefront (FastStore)

Started Mar 06, 2026, 04:06 PM UTC· resolved Mar 06, 2026, 04:43 PM UTC

  1. investigating Mar 06, 2026, 04:06 PM UTC

    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. monitoring Mar 06, 2026, 04:43 PM UTC

    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. resolved Mar 06, 2026, 05:08 PM UTC

    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.

Read the full incident report →

Major February 20, 2026 Intelligent Search outage 1h 33m Developer Tools (API Integrations)

Started Feb 20, 2026, 07:20 PM UTC· resolved Feb 20, 2026, 08:53 PM UTC

  1. investigating Feb 20, 2026, 07:20 PM UTC

    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. monitoring Feb 20, 2026, 07:46 PM UTC

    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. monitoring Feb 20, 2026, 08:25 PM UTC

    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. resolved Feb 20, 2026, 08:53 PM UTC

    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.

Read the full incident report →

Major February 11, 2026 Intelligent Search outage 26m Developer Tools (API Integrations)

Started Feb 11, 2026, 02:14 PM UTC· resolved Feb 11, 2026, 02:40 PM UTC

  1. investigating Feb 11, 2026, 02:15 PM UTC

    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. identified Feb 11, 2026, 02:30 PM UTC

    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. resolved Feb 11, 2026, 03:18 PM UTC

    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.

Read the full incident report →

Major February 2, 2026 Checkout Service Degradation 18m Checkout (Pricing Calculation), Checkout (Order Placement), Checkout (Shipping Calculation), Checkout (Payments Gateway) and 1 more

Started Feb 02, 2026, 07:15 PM UTC· resolved Feb 02, 2026, 07:33 PM UTC

  1. investigating Feb 02, 2026, 07:29 PM UTC

    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. monitoring Feb 02, 2026, 07:41 PM UTC

    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. resolved Feb 02, 2026, 08:15 PM UTC

    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.

Read the full incident report →

Major January 29, 2026 Checkout Service Degradation 26m Admin (Admin Operations), Developer Tools (API Integrations), Admin (Marketplace Connectors), Admin (Content Management) and 14 more

Started Jan 29, 2026, 07:55 PM UTC· resolved Jan 29, 2026, 08:21 PM UTC

  1. investigating Jan 29, 2026, 07:59 PM UTC

    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. resolved Jan 29, 2026, 08:18 PM UTC

    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.

Read the full incident report →

Major January 23, 2026 Orders API considering API keys 39m

Started Jan 23, 2026, 05:22 PM UTC· resolved Jan 23, 2026, 06:02 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Major January 22, 2026 Admin Partial Outage 1h 29m

Started Jan 22, 2026, 12:15 PM UTC· resolved Jan 22, 2026, 01:45 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Critical December 20, 2025 License Manager Auth Failure 1h 58m

Started Dec 20, 2025, 03:01 AM UTC· resolved Dec 20, 2025, 05:00 AM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Major December 13, 2025 Masterdata degradation affecting Checkout 1h 24m

Started Dec 13, 2025, 01:11 AM UTC· resolved Dec 13, 2025, 02:35 AM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor December 8, 2025 Storefront Navigation Issues on VTEX Legacy Portal/CMS –

Started Dec 08, 2025, 06:26 PM UTC· resolved Dec 08, 2025, 06:26 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →