Last checked
Vtex status
Composable complete commerce platform for modernizing tech stack.
Experiencing an issue?
¿Vtex no funciona?
Degraded performance
Source: official status page
Having issues with Vtex?
Share your experience to help others stay informed.
Vtex service health graph
Service status and report activity over the last 24 hours, in 15-minute intervals. Early warnings and official incidents are shown separately.
Vtex activity
Loading reports… · Last 24 hours
Download
- No problems detected
- Possible problems
- Problems detected
- Early warning
- Official incident
Tap a bar to keep its details open. With the chart focused, use Left and Right to move between intervals, Home or End to jump, and Escape to close. Full data is available in the table below.
View chart data
| Start | End | Reports | Status |
|---|
Latest activity
Last 24 hoursOfficial status checked
Vtex is experiencing issues
Official provider statusOfficial incident active
No Observable mesh logs — **[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.
Official provider status
Vtex outage reports
0 outage reports in the last 24 hours.
Mapa de fallas de Vtex
Approved reports from the last 24 hours, grouped by country. Markers show country-level locations, not precise locations or confirmed affected infrastructure.Mapa de fallas de Vtex
Loading report locations…
Vtex status history
Official status observations, not measured service uptime.
Last 60 daysDaily history
Loading history…
- Operativo
- Problemas
- Falla
- Mantenimiento
- Sin datos
Vtex components
Vtex incident history
Official incidents, early warnings and community reports are identified separately. Early warning history covers only the last 24 hours. Dates use your time zone.
| Incident name | Duration | StartedUTC | Acknowledged | Severity |
|---|---|---|---|---|
| 768h 7mOngoing | Yes | Unknown | ||
| 27m | Yes | Major | ||
| 27m | Yes | Major | ||
| 1h 20m | Yes | Major | ||
| 49m | Yes | Minor | ||
| 27m | Yes | Minor | ||
| 45m | Yes | Minor | ||
| 7h 44m | Yes | Minor |
Discusión de la comunidad
Comparte tus pensamientos sobre Vtex
Sin comentarios aún
¡Sé el primero en comentar!
Acerca del monitoreo de Vtex en Uptimus
Uptimus monitorea Vtex mediante su fuente oficial y normaliza incidentes, mantenimiento y componentes en un estado consistente.
Esta página incluye actualmente 18 componentes monitoreados, 26 incidentes, 0 mantenimientos y 4 días de historial conocido.
Uptimus es un servicio independiente y no está afiliado con Vtex. Un estado saludable no garantiza que todos los usuarios, dispositivos o regiones estén libres de problemas.
Cómo monitorea Uptimus Vtex
Recibe alertas cuando Vtex o uno de sus componentes supervisados informa de una interrupción grave o crítica. Las alertas pueden enviarse por los canales activados en el espacio de trabajo, incluidos correo, push e integraciones configuradas. El historial disponible contiene 26 incidencias indexadas y aporta contexto más allá del estado actual. Una incidencia reciente indexada fue «No Observable mesh logs».
Recibe alertas sobre rendimiento degradado, impacto parcial e incidencias que no representan una interrupción completa. Uptimus supervisa actualmente 18 componentes de Vtex: API Integrations, Marketplace Connectors, Content Management, VTEX IO. Las alertas pueden enviarse por los canales activados en el espacio de trabajo, incluidos correo, push e integraciones configuradas.
