Xray
1h 6h 24h 48h 3d 5d 7d 14d 30d ‹
Last 1 hour▾
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-20 23:23:38.
› →|
updated 2d 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

advpsvc (tilda) image pull failing for at least 116 min — 1 pod

critical Pod cannot start nexus open impact 52 opened 14d ago · last observed 2d ago · observed 1943× · #16250 · d90d2669b9502e1f30dd

What happened template

Pod cannot start: advpsvc (tilda) image pull failing for at least 116 min — 1 pod. Facts: namespace tilda, workload advpsvc, why image pull failing, pending_minutes 116, since 1794905080.

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

namespacetilda
workloadadvpsvc
whyimage pull failing
podsadvpsvc-7bc4f8f568-z2n6n
pending_minutes116
since1,794,905,080
events44
last_messageError: ImagePullBackOff
discriminatorimage pull failing

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

History

  • 2026-11-14 20:25:58 UTCescalated x-ray · severity=critical was=warning title=advpsvc (tilda) image pull failing for at least 36 min — 1 pod level=high was_level=high finding={'id': 16250, 'fingerprint': 'd90d2669b9502e1f30dd', 'kind': 'pod.cannot_start', 'severity': 'critical', 'cluster': 'nexus', 'subject': 'tilda/advpsvc', 'title': 'advpsvc (tilda) image pull failing for at least 36 min — 1 pod', 'facts': {'namespace': 'tilda', 'workload': 'advpsvc', 'why': 'image pull failing', 'pods': ['advpsvc-7bc4f8f568-z2n6n'], 'pending_minutes': 36, 'since': 1794685774, 'events': 52, 'last_message': 'Error: ImagePullBackOff', 'discriminator': 'image pull failing'}, 'evidence': [{'label': 'Kubernetes events', 'href': '/logs?cluster=nexus&from=1794684358&to=1794687958&source=events&q=advpsvc'}, {'label': 'Pods', 'href': '/pods?cluster=nexus'}], 'provenance': {'source': 'x-ray', 'note': 'Kubernetes events (logs/events in BigQuery), last 45 min'}, 'impact': 47.1, 'status': 'open', 'first_seen': 1793843849, 'last_seen': 1794687958, 'resolved_at': None, 'acked_by': None, 'acked_at': None, 'snoozed_until': None, 'occurrences': 1540, 'narrative': 'Pod cannot start: advpsvc (tilda) image pull failing for at least 23 min — 1 pod. Facts: namespace tilda, workload advpsvc, why image pull failing, pending_minutes 23, since 1794685774.', 'narrative_kind': 'template', 'discriminator': 'image pull failing', 'level': 'high', 'told_level': None, 'episode_at': 1794242648, 'chat_thread': None, 'kind_label': 'Pod cannot start', 'group': 'Pods', 'age_s': 844128, 'stale_s': 19}

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