# Console: Delayed Pod starts and Empty Console Logs

- Provider: [RunPod](https://down.guide/providers/runpod)
- Confidence: Confirmed
- Impact: Degraded
- lasted 4h 41m
- started 2026-05-08 17:08 UTC
- id: DWN-40a453f7c8
- Official page: https://uptime.runpod.io/incident/891339

## Updates from RunPod
### 2026-05-08 17:08 UTC: update
We are experiencing increased times for Pods to start along with console logs not being displayed. We are investigating the issue and will provide an update once we have more information.

### 2026-05-08 21:47 UTC: update
We've identified the issue and are working to incorporate the fix.

### 2026-05-08 21:49 UTC: resolved
The issue has been resolved. Functionality for pod starts and display for logs on the console have returned to normal.

From the builder: does your app depend on RunPod? [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=runpod) detects problems in your own logs without hand-written monitors, and you can ask it in plain language which errors mention RunPod.

---
down.guide reads providers' official status pages every minute and adds its own evidence, always labeled. Free, no account. Agents: MCP at https://down.guide/mcp, REST at https://down.guide/api/v1, feeds at https://down.guide/feed. Built by [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=DWN-40a453f7c8), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.