DockerUniverseEnvironments
staging-us8 Running0 Restarting0 UnhealthyCPU 12%MEM 1.1/8 GBUptime 1d 1hLast seen now

Environment Health Report

staging-us, live, last 30 days

Stability
97.3%
Computed from crash and uptime ratio
Total Crashes
3
Stored in SQLite event history
OOM Events
1
0.6 avg restarts/day

Per-Container Health

ContainerStatusUptimeRestartsLast CrashStability
nginx-proxyRunning 3d 14h3d 14h0Never100%
api-serviceRestarting2m146/6/2026 (OOM killed)72%
postgresRunning 21d21d 7h0Never100%
redis-cacheExited (137)--36/5/2026 (SIGKILL, often OOM)94%
worker-queueRunning 7d7d 2h15/30/2026 (Application error)98%

Crash Feed

Jun 6, 03:12 AM
api-serviceExit 137OOM killed
Container killed after exceeding 256 MB memory limitDuration 2d 4h
Jun 5, 10:44 PM
redis-cacheExit 137SIGKILL, often OOM
Received SIGKILLDuration 22h 30m
May 30, 01:44 AM
worker-queueExit 1Application error
Application returned non-zero exit codeDuration 12h 1m

Recommendations

api-service
OOM events detected
Last 3 crashes are OOM related. Increase the memory limit from 256 MB to 512 MB or reduce heap usage.
redis-cache
SIGKILL exit code 137
Exit 137 can mean OS-level memory pressure. Check host memory before restarting this service.

DevOps Health Metrics

MetricSourceFrequencyCurrent Value
Container uptimedocker inspect State.StartedAt60s4d 12h
Creation timedocker inspect Createdsnapshot2026-05-31
Restart countdocker inspect RestartCount60s18 total
Exit codedocker events diereal-time137, 1
OOM kill flagdocker events oomreal-time3 events
Last crash timestampdocker eventsreal-timeToday 03:12
Crash reasonexit code tableon eventOOM killed
Crash durationcomputed runtimeon event2d 4h
Health check statusdocker inspect State.Health30s1 unhealthy
CPU usagedocker stats5s34%
Memory usagedocker stats5s6.2 / 16 GB
Network I/Odocker stats5s2.3 MB/s up
Block I/Odocker stats5s41 MB read
Stability scorecomputed60s97.3%