Is Vtex down?

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.