Engine routing
Todos los motores responden dentro del SLA.
Estado
Indicadores en tiempo real de la salud de la cola, proveedores de enrutamiento y sistemas de facturación. Suscríbase dentro de la aplicación para recibir alertas de incidentes.
Status checks refresh continuously from the same telemetry we use to route renders. When an engine moves from “Operational” to “Degraded”, MaxVideoAI automatically shifts traffic to the fastest available region and posts an incident below. If an outage requires customer action we flag it in the incident notes and reference the job IDs that may need a retry or credit refund.
Before contacting support, confirm whether the engine you are using shows a disruption and review the incident history. You can also subscribe to the RSS feed or email digest to receive alerts the moment we downgrade an engine. For urgent escalations, include the job ID and engine name so we can trace the queue instantly.
Quick references
- Render queue latency — typically updates every 60 seconds.
- Incident log — entries include start/end time, root cause, and mitigation steps.
- Support — email [email protected] with incident code + job ID for a priority response.
Operational
Queue processing
Tiempo medio de arranque inferior a 45 segundos.
Wallet + billing
Pagos, reembolsos y recibos operan con normalidad.
Callbacks & webhooks
Reintentos de webhooks con retraso de ~2 minutos. En investigación.
Incidents
2024-06-10
Latencia del proveedor Pika
Retrasos en la cola de Pika durante 34 minutos. Se dispararon reembolsos automáticos para los renders afectados.
Resolved