X — advance notice
Scheduled maintenance: [date], [start time] to [end time] [time zone]. During the window: [what will not work]. Still working: [what stays available]. Please [action, e.g. finish exports] before it starts. [status link]
LinkedIn — customer notice
Planned maintenance for [Product] on [date]. When: [start] to [end], [time zone] ([duration]). Why: [reason, e.g. database upgrade for faster search]. Impact: [specific features unavailable]. What you should do: [action, or 'nothing']. We picked this window because it is our lowest-traffic period. Updates will be posted at [status page link].
Bluesky — starting now
Maintenance starting now. [Product] [what is unavailable] until about [end time, time zone]. Progress: [status link]
Mastodon — completed
Maintenance complete. [Product] is fully available again as of [time, time zone]. What changed: [short summary]. If anything looks wrong, [how to report]. #[ProductTag]
Tips
- Give at least 72 hours' notice for planned downtime, longer for business-critical tools.
- Convert the window into your main customers' time zones, or link to a time zone converter.
- List what still works during maintenance, not only what breaks. It reduces support tickets.
- Post the completion notice even if nothing went wrong; users waiting to resume work are watching for it.
Frequently asked questions
How far in advance should I announce maintenance?
Three to seven days is typical for routine maintenance. For longer windows or changes that require user action, announce two weeks ahead and remind the day before.
Can I schedule the whole maintenance sequence in advance?
Yes. Draft all four posts at once, schedule them for their times, and keep them in an approval queue so you can edit the window if plans change.