Skip to content

DISTRO_B_POWER_STATUS_UNAVAILABLE

published Last Updated: Oct 9, 2026 HW: all
Applicable alarms (1)
DISTRO_B_POWER_STATUS_UNAVAILABLE
Likely outcomes (59 missions, 20 issues) — click to expand

Based on 59 missions where this alarm fired in the last 90 days as of 2026-10-13

Grounding vs discrepancy (of 20 ZERP issues filed on these missions)

Grounding 15% (3 of 20 issues) Discrepancy 85% (17 of 20 issues)

Frequently replaced parts

Part P/N Removals
LEFT DOOR ASSY, DROID, P2 21830 18
RIGHT DOOR ASSY, DROID, P2 21827 18
PARALAND ASSY, DROID, P2 18427 14
BATTERY, DROID, P2 24544 12
BRAIN, LRU, DROID, P2 31920 10

Aggregated from fleet operations and refreshed daily. Individual outcomes may vary by site and configuration.

This alarm occurs when Zip Exec has not received a power status reported by Distro B within the watchdog timeout. Often this alarm is caused by Distro B crashing, running at too slow of a rate, or publishing power status too infrequently.

This alarm can also be caused by compute performance, compute bridge, and IPC issues (these cases often see multiple watchdog alarms).

  • DISTRO_B_POWER_STATUS_UNAVAILABLE
1 escalation

Did this guide help you get unblocked?

Open suggestions

There are no open suggestions.

Open pull requests

There are no open pull requests.