Maintenance Schedule
A heading and lede over a bordered list of maintenance windows, each row carrying date, UTC time, affected components, impact, and a status chip.
A heading and lede over a bordered list of maintenance windows, each row carrying date, UTC time, affected components, impact, and a status chip.
Search blocks by description or jump to a page.
The source for every Marketing block is included with Basic and Pro. Pick a plan to copy the code.
Already purchased? Log in
Maintenance Schedule turns planned downtime into a courtesy rather than a surprise. Upcoming windows run down a bordered list, each row carrying a date, a UTC time band, the affected components, a plain impact sentence, and a status chip that flips from scheduled to completed. The lede sets the promise the list keeps, every window published well ahead and closed out with what happened.
The windows are one array. The impact line is where the trust lives, reads unaffected, writes paused for under 60 seconds tells an operator exactly what to plan around. Completed rows staying in the list is deliberate, the record of a clean window is as reassuring as the notice of the next one.
Reach for this block on status pages beneath current-status-list, and on trust centers where predictable operations are part of the pitch. Buyers running production on your platform read the maintenance cadence closely, a quiet hour and a fixed notice period signal an operator who respects their uptime as much as yours.
A natural flow around it on a Marketing Pro page:
Before
After
One strong use is the next month of platform maintenance. Other schedules:
Tip: name the quietest hour you scheduled for, choosing 02:00 UTC on purpose reads as care, not coincidence.