Vtex Outage History

Vtex is up right now

Vtex had 22 outages in the last 2 years totaling 30h 39m of downtime — averaging 0.9 incidents per month.

There were 22 Vtex outages since October 5, 2025 totaling 30h 39m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.vtex.com

Minor September 25, 2026

Admin Access Issue

Detected by Pingoru
Sep 25, 2026, 04:18 PM UTC
Resolved
Sep 25, 2026, 04:18 PM UTC
Duration
—
Affected: Admin Operations
Timeline · 5 updates
  1. investigating Sep 25, 2026, 02:50 PM UTC

    Status: Investigating 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. Affected components Admin Operations (Degraded performance)

  2. investigating Sep 25, 2026, 03:20 PM UTC

    Status: Investigating 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. Affected components Admin Operations (Degraded performance)

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

    Status: Monitoring 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. Affected components Admin Operations (Operational)

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

    Status: Monitoring 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. Affected components Admin Operations (Operational)

  5. resolved Sep 25, 2026, 04:18 PM UTC

    Status: Resolved 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. 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)

Read the full incident report →

Minor September 10, 2026

VTEX Ads outage

Detected by Pingoru
Sep 10, 2026, 02:45 PM UTC
Resolved
Sep 10, 2026, 02:45 PM UTC
Duration
—
Affected: Admin Operations
Timeline · 4 updates
  1. investigating Sep 10, 2026, 01:37 PM UTC

    Status: Investigating 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. Affected components Admin Operations (Partial outage)

  2. identified Sep 10, 2026, 02:01 PM UTC

    Status: Identified 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. Affected components Admin Operations (Partial outage)

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

    Status: Identified 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. Affected components Admin Operations (Degraded performance)

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

    Status: Resolved 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. Affected components Admin Operations (Operational)

Read the full incident report →

Minor August 17, 2026

Increase in Master Data errors.

Detected by Pingoru
Aug 17, 2026, 11:28 PM UTC
Resolved
Aug 17, 2026, 11:28 PM UTC
Duration
—
Affected: Master Data
Timeline · 3 updates
  1. investigating Aug 17, 2026, 10:57 PM UTC

    Status: Investigating 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. Affected components Master Data (Degraded performance)

  2. monitoring Aug 17, 2026, 11:13 PM UTC

    Status: Monitoring 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. Affected components Master Data (Operational)

  3. resolved Aug 17, 2026, 11:28 PM UTC

    Status: Resolved 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. Affected components Master Data (Operational)

Read the full incident report →

Major August 7, 2026

No Observable mesh logs

Detected by Pingoru
Aug 07, 2026, 03:08 AM UTC
Resolved
Aug 07, 2026, 10:42 AM UTC
Duration
7h 33m
Timeline · 1 update
  1. monitoring Aug 07, 2026, 03:08 AM UTC

    Status: Monitoring [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 →

Minor June 16, 2026

Faststore service partial outage

Detected by Pingoru
Jun 16, 2026, 07:49 PM UTC
Resolved
Jun 16, 2026, 07:49 PM UTC
Duration
—
Affected: FastStore
Timeline · 3 updates
  1. investigating Jun 16, 2026, 07:22 PM UTC

    Status: Investigating 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. Affected components FastStore (Partial outage)

  2. monitoring Jun 16, 2026, 07:32 PM UTC

    Status: Monitoring 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. Affected components FastStore (Operational)

  3. resolved Jun 16, 2026, 07:49 PM UTC

    Status: Resolved 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. Affected components FastStore (Operational)

Read the full incident report →

Minor May 14, 2026

Order flow affected post purchase

Detected by Pingoru
May 14, 2026, 02:43 PM UTC
Resolved
May 14, 2026, 02:43 PM UTC
Duration
—
Affected: Order Management
Timeline · 3 updates
  1. investigating May 14, 2026, 02:16 PM UTC

    Status: Investigating 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. Affected components Order Management (Partial outage)

  2. monitoring May 14, 2026, 02:39 PM UTC

    Status: Monitoring 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. Affected components Order Management (Operational)

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

    Status: Resolved 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. Affected components Order Management (Operational)

Read the full incident report →

Minor May 9, 2026

Checkout Service Degradation

Detected by Pingoru
May 09, 2026, 05:05 PM UTC
Resolved
May 09, 2026, 05:05 PM UTC
Duration
—
Affected: Portal/CMSPricing CalculationOrder PlacementShipping CalculationPayments GatewayPayment Connectors
Timeline · 3 updates
  1. investigating May 09, 2026, 04:16 PM UTC

    Status: Investigating 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. Affected components Portal/CMS (Degraded performance) Shipping Calculation (Degraded performance) Payment Connectors (Degraded performance) Order Placement (Degraded performance) Payments Gateway (Degraded performance) Pricing Calculation (Degraded performance)

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

    Status: Monitoring We are monitoring checkout services after the adjustments have been applied. At this time, sales may be partially affected, as well as store navigation and session stability, 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. Affected components Pricing Calculation (Degraded performance) Portal/CMS (Degraded performance) Shipping Calculation (Degraded performance) Payment Connectors (Degraded performance) Order Placement (Degraded performance) Payments Gateway (Degraded performance)

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

    Status: Resolved This incident has been resolved. Affected components Order Placement (Operational) Payments Gateway (Operational) Pricing Calculation (Operational) Portal/CMS (Operational) Shipping Calculation (Operational) Payment Connectors (Operational)

Read the full incident report →

Minor May 9, 2026

Degraded performance for orders management

Detected by Pingoru
May 09, 2026, 07:54 AM UTC
Resolved
May 09, 2026, 07:54 AM UTC
Duration
—
Affected: Order Management
Timeline · 2 updates
  1. monitoring May 09, 2026, 07:28 AM UTC

    Status: Monitoring 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. Affected components Order Management (Degraded performance)

  2. resolved May 09, 2026, 07:54 AM UTC

    Status: Resolved 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. Affected components Order Management (Operational)

Read the full incident report →

Minor April 14, 2026

Login Errors

Detected by Pingoru
Apr 14, 2026, 10:44 PM UTC
Resolved
Apr 14, 2026, 10:44 PM UTC
Duration
—
Affected: API Integrations
Timeline · 3 updates
  1. investigating Apr 14, 2026, 09:59 PM UTC

    Status: Investigating 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. Affected components API Integrations (Degraded performance)

  2. monitoring Apr 14, 2026, 10:32 PM UTC

    Status: Monitoring 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. Affected components API Integrations (Degraded performance)

  3. resolved Apr 14, 2026, 10:44 PM UTC

    Status: Resolved 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. Affected components API Integrations (Operational)

Read the full incident report →

Minor March 6, 2026

FastStore WebOps deployments issues

Detected by Pingoru
Mar 06, 2026, 05:08 PM UTC
Resolved
Mar 06, 2026, 05:08 PM UTC
Duration
—
Affected: FastStore
Timeline · 3 updates
  1. investigating Mar 06, 2026, 04:06 PM UTC

    Status: Investigating 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. Affected components FastStore (Degraded performance)

  2. monitoring Mar 06, 2026, 04:43 PM UTC

    Status: Monitoring 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. Affected components FastStore (Operational)

  3. resolved Mar 06, 2026, 05:08 PM UTC

    Status: Resolved 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. Affected components FastStore (Operational)

Read the full incident report →

Minor February 20, 2026

Intelligent Search outage

Detected by Pingoru
Feb 20, 2026, 08:53 PM UTC
Resolved
Feb 20, 2026, 08:53 PM UTC
Duration
—
Affected: API Integrations
Timeline · 4 updates
  1. investigating Feb 20, 2026, 07:20 PM UTC

    Status: Investigating 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. Affected components API Integrations (Partial outage)

  2. monitoring Feb 20, 2026, 07:46 PM UTC

    Status: Monitoring 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. Affected components API Integrations (Partial outage)

  3. monitoring Feb 20, 2026, 08:25 PM UTC

    Status: Monitoring 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. Affected components API Integrations (Partial outage)

  4. resolved Feb 20, 2026, 08:53 PM UTC

    Status: Resolved 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. Affected components API Integrations (Operational)

Read the full incident report →