[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"glossary-maintenance-window::en":3,"gloss-cluster-maintenance-window::en":23,"gloss-next-maintenance-window::en":9},{"slug":4,"category":5,"name":6,"definition":7,"meta_desc":8,"faq":9,"schema_markup":9,"related":10},"maintenance-window","cloud","Maintenance Window","A maintenance window is a period agreed in advance during which a service may be disrupted for planned work: an upgrade, a migration, a hardware replacement, a schema change that cannot be made online. The point of naming it is that the disruption stops being an incident. Customers were told, the work has an owner and a rollback, and the hours were chosen rather than arrived at. Two properties of the window matter more than its length. The first is who it belongs to. A provider's window is a right they reserved in the contract, and it may fall in the middle of your busiest hours because their busiest hours are elsewhere; if that matters, it is a negotiation to have before signing rather than a surprise to absorb later. The second is whether availability commitments exclude it. Planned maintenance is very often carved out of the promise, which means a service can be unavailable to you, entirely legitimately, without the figure on the page moving at all. That is not a trick, but it is a reason to read the exclusion list rather than the headline. The practice degrades in a predictable way. Windows that are never used stop being scheduled; windows that are used for everything become the only time anything ships, which makes each one large and risky; and a global product eventually discovers there is no hour that is quiet everywhere, so the window becomes a choice about which customers absorb the disruption. The honest response is to shrink what needs a window at all — doing more work in a way that keeps the service up — and to keep the remaining windows small, frequent, and announced far enough ahead that a customer can plan around them rather than react to them. It is also worth keeping a list of the windows your providers reserve, not only the ones you declare, because a dependency that takes its window at the same hour you take yours turns two routine pieces of work into one unplanned outage.","A maintenance window turns planned disruption into an announced event. Who the window belongs to, and why availability promises usually exclude it.",null,[11,14,17,20],{"slug":12,"name":13},"blue-green-deployment","Blue-Green Deployment",{"slug":15,"name":16},"runbook","Runbook",{"slug":18,"name":19},"sla","Service-Level Agreement (SLA)",{"slug":21,"name":22},"status-page","Status Page",[24,28,32,35,38,41,45,48,51,54,57,60],{"slug":25,"category":5,"name":26,"updated_at":27},"air-gapped-deployment","Air-Gapped Deployment","2026-09-09T03:30:02+00:00",{"slug":29,"category":5,"name":30,"updated_at":31},"autoscaling","Autoscaling","2026-09-08T21:32:36+00:00",{"slug":33,"category":5,"name":34,"updated_at":31},"availability-zone","Availability Zone (AZ)",{"slug":36,"category":5,"name":37,"updated_at":31},"block-storage","Block Storage",{"slug":39,"category":5,"name":40,"updated_at":27},"bring-your-own-cloud","Bring Your Own Cloud (BYOC)",{"slug":42,"category":5,"name":43,"updated_at":44},"budget-alert","Budget Alert","2026-09-08T21:32:37+00:00",{"slug":46,"category":5,"name":47,"updated_at":27},"change-freeze","Change Freeze",{"slug":49,"category":5,"name":50,"updated_at":27},"control-plane","Control Plane and Data Plane",{"slug":52,"category":5,"name":53,"updated_at":44},"cost-allocation-tag","Cost Allocation Tag",{"slug":55,"category":5,"name":56,"updated_at":44},"cost-chargeback","Cost Chargeback",{"slug":58,"category":5,"name":59,"updated_at":44},"cost-observability","Cost Observability",{"slug":61,"category":5,"name":62,"updated_at":31},"disaster-recovery","Disaster Recovery"]