Pricing
Status historyRSS updatesStatus API

Powered by Uptimus

    Vtex outage history

    32 recorded Vtex incidents since September 2025, with official updates, affected components, duration and resolution information.

    Back to current status

    Admin outage

    Started October 21, 2026 at 5:13 PM UTC · 0m

    IssuesMinor incident
    1. October 21, 2026 at 5:13 PM 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)

    Increase in Master Data errors

    Started October 21, 2026 at 12:34 AM UTC · 0m

    IssuesMinor incident
    1. October 21, 2026 at 12:34 AM UTCresolved

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

    Increased errors in VTEX IO

    Started October 20, 2026 at 9:24 PM UTC · 0m

    IssuesMinor incident
    1. October 20, 2026 at 9:24 PM UTCresolved

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

    Admin Access Issue

    Started September 25, 2026 at 4:18 PM UTC · 0m

    IssuesMinor incident
    1. September 25, 2026 at 4:18 PM UTCresolved

      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 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)

    VTEX Ads outage

    Started September 10, 2026 at 2:45 PM UTC · 0m

    IssuesMinor incident
    1. September 10, 2026 at 2:45 PM UTCresolved

      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)

    Increase in Master Data errors.

    Started August 17, 2026 at 11:28 PM UTC · 0m

    IssuesMinor incident
    1. August 17, 2026 at 11:28 PM UTCresolved

      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)

    No Observable mesh logs

    Started August 7, 2026 at 3:08 AM UTC · Ongoing

    Pending
    1. August 7, 2026 at 3:08 AM 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.

    Faststore service partial outage

    Started June 16, 2026 at 7:22 PM UTC · 27m

    OutageMajor incident
    1. June 16, 2026 at 7:22 PM 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. June 16, 2026 at 7:32 PM 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. June 16, 2026 at 7:49 PM 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.

    Order flow affected post purchase

    Started May 14, 2026 at 2:16 PM UTC · 27m

    OutageMajor incident
    1. May 14, 2026 at 2:16 PM 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. May 14, 2026 at 2:39 PM 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.

    3. May 14, 2026 at 2:51 PM UTCresolved

      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.

    Order flow affected post purchase

    Started May 14, 2026 at 6:36 AM UTC · 1h 20m

    OutageMajor incident
    1. May 14, 2026 at 6:36 AM 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. May 14, 2026 at 7:09 AM 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. May 14, 2026 at 7:40 AM 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. May 14, 2026 at 7:54 AM 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. May 14, 2026 at 8:06 AM 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.

    Checkout Service Degradation

    Started May 9, 2026 at 4:16 PM UTC · 49m

    IssuesMinor incident
    1. May 9, 2026 at 4:16 PM UTCinvestigating

      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. May 9, 2026 at 4:49 PM UTCmonitoring

      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. May 9, 2026 at 5:05 PM UTCresolved

      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.

    Degraded performance for orders management

    Started May 9, 2026 at 7:28 AM UTC · 27m

    IssuesMinor incident
    1. May 9, 2026 at 7:28 AM 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. May 9, 2026 at 7:54 AM 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.

    Login Errors

    Started April 14, 2026 at 9:59 PM UTC · 45m

    IssuesMinor incident
    1. April 14, 2026 at 9:59 PM 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. April 14, 2026 at 10:32 PM 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. April 14, 2026 at 10:44 PM 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.

    High error rate in stores

    Started March 20, 2026 at 8:48 PM UTC · 7h 44m

    IssuesMinor incident
    1. March 20, 2026 at 8:48 PM 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. March 20, 2026 at 9:19 PM 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. March 20, 2026 at 9:56 PM 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. March 20, 2026 at 10:28 PM 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. March 20, 2026 at 10:55 PM 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. March 20, 2026 at 11:05 PM 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. March 20, 2026 at 11:38 PM 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. March 21, 2026 at 12:12 AM 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. March 21, 2026 at 12:51 AM 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. March 21, 2026 at 1:26 AM 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. March 21, 2026 at 2:00 AM 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. March 21, 2026 at 2:40 AM 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. March 21, 2026 at 3:26 AM UTCmonitoring

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

    14. March 21, 2026 at 4:05 AM 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. March 21, 2026 at 4:31 AM 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.

    FastStore WebOps deployments issues

    Started March 6, 2026 at 4:06 PM UTC · 1h 2m

    IssuesMinor incident
    1. March 6, 2026 at 4:06 PM 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. March 6, 2026 at 4:43 PM 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. March 6, 2026 at 5:08 PM 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.

    Intelligent Search outage

    Started February 20, 2026 at 7:20 PM UTC · 1h 33m

    OutageMajor incident
    1. February 20, 2026 at 7:20 PM 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. February 20, 2026 at 7:46 PM 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. February 20, 2026 at 8:25 PM 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. February 20, 2026 at 8:53 PM 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.

    Intelligent Search outage

    Started February 11, 2026 at 2:49 PM UTC · 29m

    OutageMajor incident
    1. February 11, 2026 at 2:49 PM 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. February 11, 2026 at 2:57 PM 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. February 11, 2026 at 3:18 PM 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.

    Checkout Service Degradation

    Started February 2, 2026 at 7:29 PM UTC · 46m

    OutageMajor incident
    1. February 2, 2026 at 7:29 PM 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. February 2, 2026 at 7:41 PM 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. February 2, 2026 at 8:15 PM 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.

    Checkout Service Degradation

    Started January 29, 2026 at 8:18 PM UTC · 0m

    OutageMajor incident
    1. January 29, 2026 at 9:15 PM 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.

    2. January 29, 2026 at 9:15 PM 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.

    Orders API considering API keys

    Started January 23, 2026 at 5:22 PM UTC · 39m

    OutageMajor incident
    1. January 23, 2026 at 5:22 PM UTCinvestigating

      We are currently investigating an issue in Orders API considering API keys. 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. January 23, 2026 at 5:53 PM UTCmonitoring

      The fix for the issue has been implemented, we're monitoring. Our incident response team is monitoring to guarantee that normal platform behavior is fully reestablished.

    3. January 23, 2026 at 6:02 PM UTCresolved

      This incident has been resolved. We will provide further information in a public incident report.