Sage DPW Cloud: 10-minute maintenance window set for 19 November 2026
Sage's notice sets a ten-minute DPW Cloud maintenance window for 19 November 2026, though its own timings disagree by an hour at the end point.
Sage has scheduled ten minutes of planned maintenance on its DPW Cloud service for 19 November 2026. The operative window is 19:00 to 19:10 UTC, which is 20:00 to 20:10 MEZ across central Europe. Sage's status notice, logged at 12:20 UTC that day, marks the event as maintenance rather than an incident. One English sentence in the notice contradicts its own header on timing, and that contradiction is why a ten-minute window is worth reading twice.
When exactly does the window run?
Three renderings of the timing sit in one notice, and they do not agree.
The header gives 19:00 to 19:10 UTC. The German text of the same notice gives 20:00 to 20:10 MEZ, the same ten minutes, because MEZ runs one hour ahead of UTC.
The English sentence reads differently. It states the range as "between 20:00 CET and 20:10 UTC", pairing two zones in a single span. Read literally, that covers 19:00 UTC to 20:10 UTC, seventy minutes.
Two of the three renderings agree on ten minutes, so we treat the header's window, 19:00 to 19:10 UTC, as the operative one. The disagreement is a single hour at the end point. Read as 20:10 MEZ rather than 20:10 UTC, the English sentence would match the other two.
For a job you cannot afford to interrupt, the literal sentence supplies the safe span. Stay clear from 19:00 to 20:10 UTC and every reading of the notice is covered.
Sage's wording and posting time
"The service may not be available during the scheduled maintenance window," the notice states. The German text is more direct: the service will be unavailable for ten minutes because of maintenance work.
Sage posted the item under its own name, signed "The Sage Team", at 12:20 UTC on 19 November. That is six hours and forty minutes before the window opens, enough notice to move evening jobs clear of the gap.
Planning around the window
Treat DPW Cloud as unavailable for the full ten minutes, 19:00 to 19:10 UTC. Move anything scheduled against the service, batch runs included, to before 19:00 or after 19:10 rather than through the gap.
The window sits at 20:00 across the MEZ zone, per the notice's own German rendering, so it lands in the European evening. Check your schedulers for anything booked into that hour before you sign off for the day.
Consider the service back only when Sage's status page records recovery, not when the clock passes 19:10 UTC.
Details the notice leaves out
The notice does not describe the work itself. There is no version number, no component list, and nothing to indicate whether this is a restart, an upgrade, or a hosting change. It names no region. It offers no guidance on sessions in flight when the service drops, or on jobs queued against it.
The status notice is also the only source for this report. Until Sage publishes more, the scope of the work and the true end of the window remain open.