Rubrik Triage

Last updated: October 27, 2026 at 9:19 AM ET

🔴 6 Critical ⚠️ 4 Warnings 🙋 0 Replies 👀 5 Watching

Critical

🔴 Rubrik: htv001wbkrbk001 – periodic task failure CRITICAL

Cluster: htv001wbkrbk001 → Westbrook, ME (WMTW)

Object: htv001wbkrbk001 (node RVMHM188S005351/005414/005439)

Reappeared again 10/27 (Unable to upload snapshot: WMTW-VCSA, WMTW-FILEMOVER). SLA Domain policy violation alerts also seen today for this cluster - noise, not tracked separately.

🔴 Rubrik: htv001wbkrbk001 – NtpClockOffsetSyspeer CRITICAL

Cluster: htv001wbkrbk001 → Westbrook, ME (WMTW)

Object: NtpClockOffsetSyspeer policy (nodes RVMHM188S005414/005439)

Not individually reconfirmed 10/27 (sampling). Last confirmed 10/26. Kept confirmed - only 1 silent day.

🔴 Rubrik: fdbdr-rbkcc-001 – fileset backup failure CRITICAL

Cluster: fdbdr-rbkcc-001 → (fdbdr)

Object: AZRORA2_oraarchive from hbm001azrora2

Reappeared again 10/27 07:09 UTC (Creating snapshot failed - genuine failure, distinct from a separate noise SLA-violation alert also seen today).

🔴 Rubrik: hts001albrbk001 – DIMM correctable error CRITICAL

Cluster: hts001albrbk001 → Albany, NY

Object: DIMM P1-DIMMB1, node RVMHM187S009534

Not individually reconfirmed 10/27 (sampling). Last confirmed 10/26. Kept confirmed - only 1 silent day.

🔴 Rubrik: htv001mlwrbk001 – periodic task failure CRITICALCorroborated

Cluster: htv001mlwrbk001 → Milwaukee, WI

Object: htv001mlwrbk001 (node RVMHM191S004072/004136/004373)

Not individually reconfirmed 10/27 (sampling). Last confirmed 10/26. Corroborates P1 case 01497996.

🔴 Rubrik: hts001dmnrbk001 – backup failure CRITICAL

Cluster: hts001dmnrbk001 → Dayton/DMN

Object: ca-gennews1.ahc.belotechnologies.com volumes

Specific object not reconfirmed 10/27, but cluster was active today with other Critical failures (Unable to upload snapshot, archival connect failure) tracked separately.

Warnings

⚠️ Rubrik: htv001dsmrbk001 – stuck jobs WARNING

Cluster: htv001dsmrbk001 → Des Moines, IA

Object: stuck job (nodes RVMHM187S008994, RVMHM187S009403, RVMHM187S009518)

Not individually reconfirmed 10/27 (sampling). Last confirmed 10/26.

⚠️ Rubrik: htv001wdcrbk001 – stuck jobs WARNING

Cluster: htv001wdcrbk001 → Washington, DC

Object: STAGE_CDM_SOFTWARE_GLOBAL job

Stuck jobs cannot be canceled - confirmed again 10/27 11:06 UTC.

⚠️ Rubrik: hts001lourbk001 – widespread backup unreachable WARNINGCorroborated

Cluster: hts001lourbk001 → Louisville, KY

Object: 20+ hosts (BQLIKEM, Splunk, PBSQL/PBBLD/TBSQL/DBQLIKEM/PBQLIKEM/XBISQL fleets, PBINTSYS114A, CPCSCCMRS104, PBDC74)

Continues through 10/27 (9th+ day). Confirmed again, PLUS new Critical "Creating snapshot failed" events across an overlapping host fleet - same underlying outage. Case #01590660 still open.

⚠️ Rubrik: hts001dalrbk002 – remote cluster unreachable WARNING

Cluster: hts001dalrbk002 → Dallas, TX

Object: remote cluster connectivity (link to htv001wbkrbk001)

Linked a pre-existing Kando card not reflected in tracking.json. Warning seen 2026-10-27 07:32 UTC. Scott should verify true first-seen date.

Support Cases

🔴 Rubrik: P1 Case #01590660 – hts001lourbk001 (Node is Bad) CRITICALCorroborated

Cluster: hts001lourbk001 → Louisville, KY

Object: Node RVMHM191S005366

CONFIRMED this run via widespread Critical/Warning alerts. No new case-update since 10/25 23:59; satisfaction survey sent 10/26 - possible closure soon, Scott to verify.

🔴 Rubrik: P1 Case #01497996 – htv001mlwrbk001 (Node is Bad) CRITICALCorroborated

Cluster: htv001mlwrbk001 → Milwaukee, WI

Object: Node RVMHM191S004072

Not individually reconfirmed 10/27 (sampling). Last confirmed update 10/25 19:57 (still open).

⚠️ Rubrik: NEW P2 Case #01594174 – htv001ftmbk001 (Node is Stale) WARNING

Cluster: htv001ftmbk001 → (site unknown)

Object: —

New proactive case opened 10/26 21:04 UTC. Not corroborated by today's automated alerts. Watching Day 1 - no task created yet.

⚠️ Rubrik: htv001nolrbk001 – P2 Case #01381005 (DIMM errors) WARNING

Cluster: htv001nolrbk001 → New Orleans, LA

Object: —

RESOLVED per Rubrik Support 10/19/26. Kando card left open - Scott's call whether to close. No change this run.

🔴 Rubrik: P1 Case #01308275 – htv001wbkrbk001, Westbrook (Node is Bad) CRITICAL

Cluster: htv001wbkrbk001 → Westbrook, ME (WMTW)

Object: Node RVMHM188S005439

RESOLVED by Rubrik Support 9/13/26. Stale since 9/15 - Scott's call whether to close. No change this run.

Watching

🔴 Rubrik: htv001jksrbk001 – new backup/archival failures CRITICAL

Cluster: htv001jksrbk001 → Jacksonville, FL

Object: msdb (snapshot upload) + Azure archival connectivity

NEW today: Critical archival-connect + snapshot-upload failures, plus Warning host-unreachable alerts on multiple hosts. Day 1 - no task yet.

🔴 Rubrik: hts001fmtrbk001 – network interface down CRITICAL

Cluster: hts001fmtrbk001 → Fort Myers/FMT

Object: Network interface rketh3 (nodes RVMHM187S009048/009415/009418)

NEW today: recurring across 3 nodes. Day 1 - no task yet.

🔴 Rubrik: hts001hourbk001 – archival connect failure CRITICAL

Cluster: hts001hourbk001 → Houston, TX

Object: GCP archival location (sla-3021-sfc-hou-rbk)

NEW today. Day 1 - no task yet.

⚠️ Rubrik: htv001lvlrbk001 – backup service unreachable WARNING

Cluster: htv001lvlrbk001 → Louisville (WLKY)

Object: WLKY-ABX2.companynet.org

NEW today. A separate SLA-violation Critical alert also fired for this cluster - noise, not tracked. Day 1 - no task yet.

Things 3 Changes

Things 3 was unreachable via AppleScript again this run (get-project-todos failed) - no Things creates/updates/completes were attempted. Kando mirror was still updated (notes refreshed on 5 cards; Boston composite card completed/closed after 3 silent days).