status.gf.cx Azure datacenter card — surface optimal transfer windows

DARE.CO.UK · PARKED SKETCH · 2026-06-06

Mirrored from ~/.claude/.../memory/parked_sketch_status_datacenter_azure_card_2026-06-04.md. This is a design sketch parked for future build — read for context, not as a current deliverable.

Parked sketch — status.gf.cx card surfacing the xlab.studio tenant’s datacenter timezone, current traffic band, and countdown to next off-peak window, so transfer scheduling stops fighting APAC peak hours unintentionally

Add a card to status.gf.cx showing the xlab.studio tenant datacenter state (Singapore / Hong Kong / Malaysia — APAC, UTC+8), so transfer scheduling decisions are made with the cap-window visible instead of inferred.

Why: the per-tenant cap in azure_tenant_cap_microsoft_graph_2026-06-04.md showed that ~50% of observed throughput loss is from running during APAC peak hours, which (counter-intuitively) is Florida overnight. Dan’s mental model of “off-peak = overnight” is inverted when the tenant lives 12 hours away. A card that shows “DC time now 14:47 SGT — peak hours” or “DC time now 03:12 SGT — off-peak, 3h remaining” makes the right scheduling call visible at a glance.

How to apply: - Card lives on status.gf.cx (probably under an “external services” or “Azure / xlab.studio” section) - Show: tenant DC region name, current DC local time, traffic band (peak / shoulder / off-peak — color-coded), countdown to next off-peak window - Traffic-band heuristic: APAC peak = local 08:00-22:00, shoulder = 22:00-00:00 + 06:00-08:00, off-peak = 00:00-06:00 (refine with empirical data) - Optional v2: latest observed throughput from a daily synthetic-probe transfer (e.g. gvr-tenant-throughput-probe.sh uploads 100 MB to gvr-admin: at midnight Florida-time, logs MB/s) - Optional v3: “schedule a transfer for the next off-peak window” button that fires a wrapper script with at(1) or launchd

Pre-req fact-finding (DONE 2026-06-04): - xlab.studio tenant region = Asia Pacific (VERIFIED via admin.microsoft.com → Settings → Org settings → Organization profile → Data location · all 5 services Exchange/Teams/OneDrive/SharePoint show Current Geography = Asia Pacific · no Advanced Data Residency commitment to override). 12-hour offset from EDT confirmed. - Microsoft 365 doesn’t expose datacenter load directly via Graph; the off-peak window is heuristic, not measured.

Trigger to build: next time Dan kicks off a multi-hour bulk transfer to OneDrive and the question “is this the right time” comes up.

Related: azure_tenant_cap_microsoft_graph_2026-06-04.md (full report) · feedback_xlab_studio_tenant_naming_taxonomy_2026-06-02 (ingest-user pattern) · project_florida_trip_remote_ops_window_2026-06-03 (dashboards as control plane)