Xray
daily rollups 1h 6h 24h 48h 3d 5d 7d 14d 30d ‹
Last 14 days▾
Ends now. Anything up to this cluster's 30-day retention.
Start and end times
Cancel
Interpreted in UTC (change it at the right of this bar). Earliest available: 2026-10-19 16:54:48.
› →|
updated 1d ago
Sample data. This database was generated by scripts/seed_dev_db.py — every service, deploy, person and figure on this page is synthetic. Names are sample.*@seed.invalid and image tags are prefixed SEED-. Nothing here happened.
← findings

x-ray-pulls (x-ray) image pull failing for at least 117 min — 1 pod

critical Pod cannot start master open impact 63 opened 9d ago · last observed 1d ago · observed 1324× · #16917 · 1f6cf4c397611dc317c2

What happened template

Pod cannot start: x-ray-pulls (x-ray) image pull failing for at least 117 min — 1 pod. Facts: namespace x-ray, workload x-ray-pulls, why image pull failing, pending_minutes 117, since 1794904974.

A workload's pods have been unable to start for 10+ minutes — image pull failing, a container config error, or no node that can take them — and are still being reported.

The facts

namespacex-ray
workloadx-ray-pulls
whyimage pull failing
podsx-ray-pulls-6c4fd8ccc7-gg4xp
pending_minutes117
since1,794,904,974
events43
last_messageError: ImagePullBackOff
discriminatorimage pull failing

The story — No deploy or hand change is recorded in the hour before this opened.

History

Check it yourself

Every link carries the finding's own time window, so it shows tomorrow what it shows now.

Actions

Sign in (IAP) to acknowledge, snooze or resolve.

Where the numbers come from

sourcex-ray
noteKubernetes events (logs/events in BigQuery), last 45 min
detectork8s_events