VTEX logo

Is VTEX Down?

SaaSLive status, outages, and incident history

No. VTEX is up right now.

Every monitored VTEX system is operational as of August 11, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked 29m agoLive, rechecked every 60s
How we know: the official VTEX status page, PulsAPI's own check every 60 seconds, and outage reports from engineers. How PulsAPI monitoring works

VTEX Component Status

The main VTEX systems on this page. All 18 are operational right now.

18operational
3rd Party Apps
Operational
API Integrations
Operational
Admin Operations
Operational

15 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking Catalog Management, Content Management, FastStore, Marketplace Connectors, Master Data, Order Management, Order Placement, Payment Connectors, Payments Gateway, Portal/CMS, Pricing Calculation, Sales App, and 3 more.

Create a free account

Component statuses may change independently during partial outages.

Recent VTEX Outages & Incidents

Incident history from the official VTEX status page, including resolution updates.

Uptime history4 days observed
Aug 896.48% average · 2 days with incidentsAug 11
Pricing database maintenanceResolved Jul 31, 2026 · 247h 20mResolved

Maintenance has started --- [2026-08-03T18:54:36Z] (maintenance_scheduled) **Scheduled for Aug 10, 2025 at 00:30 UTC - 01:30 UTC** We will work on improvements to our platform that require controlled interruptions in price savings in our database.  As we upgrade our Pricing Database, some stores might experience brief periods of increased delays and errors when performing price updates through the Admin, spreadsheet imports and/or API integrations. This is required to increase system reliability during periods of peak traffic and sales. We thank you in advance for your understanding as we upgrade our platform to serve you better, our valued customers and partners.

Faststore service partial outageResolved Jun 16, 2026 · 27 minResolved

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. --- [2026-06-16T19:32:34Z] (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. --- [2026-06-16T19:58:53Z] (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.

Order flow affected post purchaseResolved May 14, 2026 · 26 minResolved

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. --- [2026-05-14T14:39:07Z] (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. --- [2026-05-14T14:16:24Z] (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.

Live VTEX Outage Reports

Problems reported by engineers using VTEX. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total
24h agoNothing reportednow

No VTEX problems reported yet.

Something wrong with VTEX on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About VTEX

VTEX exposes 18 monitored components on its status page at status.vtex.com — API Integrations, Marketplace Connectors and Content Management among them. Follow VTEX downtime, degraded performance and resolved incidents here, with uptime history alongside your other SaaS services.

Over the past 30 days, PulsAPI has measured VTEX uptime at 100.00%. Response times, incident history, and SLA tracking for VTEX are available on the PulsAPI dashboard.

VTEX Status FAQ

Is VTEX down right now?

PulsAPI checks VTEX every 60 seconds. The verdict at the top of this page comes from the latest poll of the official VTEX status feed and refreshes automatically, so you are not looking at a stale cached answer.

What should I do if VTEX is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until VTEX recovers.

How do I check VTEX uptime history?

PulsAPI tracks VTEX uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is 100.00%. A free PulsAPI account unlocks the full 90-day SLA history and incident timeline for VTEX.

How fast does PulsAPI detect VTEX outages?

PulsAPI polls the official VTEX status page every 60 seconds and usually delivers alerts to Slack, Discord, Microsoft Teams, PagerDuty, or email in under 4 seconds after detection. That is often faster than someone on your team notices on their own.

Does PulsAPI track individual VTEX components?

Yes. PulsAPI monitors 18 individual VTEX components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when VTEX goes down?

Yes. Create a PulsAPI account and subscribe to VTEX. Email alerts are included on the free Starter plan. Paid plans add Slack, Discord, Microsoft Teams, PagerDuty, and webhooks whenever VTEX status changes.

How do I report an issue with VTEX to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot VTEX problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor VTEX?

Yes. PulsAPI's Starter plan includes up to 10 monitored services with email alerts, and the 30-day free trial requires no credit card. You can monitor VTEX alongside up to 9 other services at pulsapi.com/signup.

Track VTEX with the rest of your stack

Monitor 2461+ cloud services from one dashboard and get alerts when VTEX status changes.

Start free trial