Uptime windows that match how people actually use the app
Calendar-month availability hides overnight maintenance that never touched a real user. Align the clock with usage.
Many availability reports still score every minute of the month equally. For consumer and B2B applications with clear peak hours in Korea, that math can flatter or punish you for the wrong reasons.
During uptime reliability reviews we rebuild the window from traffic histograms: business hours for office tools, evening peaks for consumer apps, and quiet bands where planned work belongs. The goal is not to hide downtime — it is to measure the downtime users feel.
Alert routing should follow the same shape. A 03:00 probe failure during a scheduled patch window should not wake the same rotation as a 14:00 checkout outage. When the clock and the user disagree, the pager becomes noise.
If your current SLA language only cites calendar uptime, ask whether a usage-weighted window would better reflect the promise you make to customers. That conversation alone often clarifies where recovery investment should go next.