Mission Control › On-Call Schedule

📟 On-Call Schedule

Operator roster, timezone-aware current time, escalation path, and handoff notes. Data persists to localStorage sd_oncall_schedule.

🕐 Current Time Overview

Live clock for each operator timezone — updated every second
UTC
--:--:--
Loading…
Primary TZ
--:--:--
Loading…
Secondary TZ
--:--:--
Loading…

👤 On-Call Roster

Primary and secondary on-call contacts. Changes are saved locally.
Loaded
Primary On-Call

—

● On Call
Name
Channel / Contact
Timezone
Shift Hours (local time)
Secondary On-Call

—

⊙ Standby
Name
Channel / Contact
Timezone
Shift Hours (local time)

🚨 Escalation Path

Standard escalation order for Space Duck platform incidents
1
Primary On-Call Operator See roster above · First response within 15 minutes for P0
2
Secondary On-Call Operator See roster above · Engaged if primary unresponsive after 15 minutes
3
Josh (T-JOSH) — Platform Owner Galaxy governance authority. Required for Lambda promotions, DynamoDB schema changes, IAM changes. Contact via primary channel when P0 unresolved or T-JOSH action required.
4
AWS Support For infrastructure incidents: SES/SNS sandbox issues, DynamoDB throttling, CloudFront outages. Open support case at console.aws.amazon.com/support

📝 Handoff Notes

Shift handoff context for the incoming operator. Persists to localStorage.
—
Not yet saved
Full Handoff Report →