Status

Live indicators for queue health, routing providers, and billing systems. Subscribe inside the app for incident alerts.

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.

Engine routing

All engines responding within SLA.

Operational

Queue processing

Average start time under 45 seconds.

Operational

Wallet + billing

Payments, refunds, and receipts running normally.

Operational

Callbacks & webhooks

Webhook retries delayed ~2 minutes. Investigating.

Degraded

Incidents

2024-06-10

Pika provider latency

Pika queue delays for 34 minutes. Auto refunds triggered for impacted renders.

Resolved