ESXPress system status
Real-time health of the ESXPress platform, backend uptime, queue depth, and the most recent completed conversion.
Degraded performance, some checks are failing
Degraded performance
The following checks are not passing: Conversions (24h).
Conversion service
Slower than usual
Conversion pipeline is degraded
Web app
Online
Live data refreshes automatically
Conversion queue
0 queued
Pending conversions waiting in the worker queues
Database
Oct 18, 2026, 10:23 AM UTC
Most recent completed conversion
System checks
Live from the status endpoint- DatabasePassingSELECT 1 in 186.5 ms
- Redis cachePassingPING in 14.8 ms
- Celery workersPassing4 workers responding
- Conversion queuePassing0 queued
- Disk spacePassing36.3% free
- Conversions (24h)Slower than usual2 ready · 12 failed (24h)
- Error rate (15 min)Passing0% 5xx (0 of 1268 requests)
Backend uptime
2 hrs, 26 min
Process uptime · resets on backend restart
Last conversion
Oct 18, 2026, 10:23 AM UTC
Most recent completed conversion
Poll failures
-
Awaiting the first automatic check…
Live status data
Uptime history
From real site traffic · one bar per day · updated daily
The last 30 measured days of the ESXPress site. 23 of 30 met the 99.5% uptime commitment, and the lowest day was 96.80% on 2026-10-11. Each day is counted from production traffic, not a synthetic probe; the newest measured day is 2026-10-16.
Measured through 2026-10-17 from production traffic. The commitment, credit schedule, and claims process are on the service level agreement.
Degraded performance
One or more live checks are failing (see the panel above). Some conversions may be delayed; new uploads may take longer than usual.
Automatic recovery
This page polls the live status endpoint every 30 seconds and updates automatically when service returns to normal.
What this means
The queue, workers, database, or pipeline may be affected. Check the per-check detail above for exactly which component is failing.
If the panel above says “live metrics temporarily stale,” the rich status feed is briefly unreachable but the platform API is still responding, the tiles show the last known readings with their age. The page reports “unreachable” only when the API itself stops answering. Either way it retries automatically.