We perform various changes and updates throughout the year and some might have some brief impact on the availability of our services. See our schedule for exact dates. This might look like a lot but that is mostly because we have chosen to note every change, even the very small ones with which we are almost certain that it would not result in any downtime.
Network changes
Typically done three times a year and can result in a few minutes downtime and reloading of the web-interface. Depending on the possible impact this is scheduled during office hours or nightly hours CET.
Infrastructure and Hypervisors
This can result in a few hours downtime twice a year depending on what changes need to be applied.
Kubernetes and cluster component
On average between one and five periods of six minute downtime per individual Nextcloud server followed by a few minutes of all services being down.
Application upgrades
Application upgrades are for example Nextcloud, Collabora, Onlyoffice but also Kopano and the Talk High Speed Backend. Two or three short downtime periods of six minutes. Occurring once every 3 months.
OS upgrades
Automaticly scheduled maintenance that runs somewhere between 01:00 and 05:00 CET, which mainly consists of rebooting servers for OS upgrades. Your instance may be down for 6 minutes as it reschedules to a different server. Occurring twice a month.
Small changes
Could in theory result in very brief downtime if something does not go according to plan. (We know stating this in this way might not help the confidence in the availability of our service but these are the facts. Most service providers choose not to mention this we’ve explicitly chosen to be open about this.) We do monitor our infrastructure completely and if something unexpected does happen we know within seconds and solve the problem or reverse the change within minutes
We have published the availability of a few of our services trough external monitoring, which should give you an idea of our uptime numbers. Here's an example of one of our demo environments:
We have published the availability of a few of our services trough external monitoring, which should give you an idea of our uptime numbers. Here’s an example of one of our demo environments:
24/7 access to your files
Now even if our service goes down for a bit and you need guaranteed 24/7 access to your files you can ensure this by downloading the desktop or mobile client and syncing the files to your device. (on the mobile devices it’s the “Set as available offline” option.) After any maintenance or downtime normal service will resume and any changes you made to these files will be synced into your Good Cloud.
If you have any questions please reach out.
Consumer environment upgrades:
Upgrading consumer environments will be executed in batches. All affected main user accounts will receive a notification via Nextcloud (web browser and/or desktop client), the day before the upgrade.
First quarter 2025
| Date | Expecting downtime | Type |
| January 2 | Yes | OS upgrade |
| January 9 | No | Small change |
| January 16 | Yes | Minor upgrade with possible announced downtime |
| January 23 | No | Small change |
| January 30 | Yes | OS Upgrades |
| February 6 | No | Small change |
| February 13 | Yes | Infrastructure & hypervisors AND Kubernetes & cluster components |
| February 20 | No | Small change |
| February 27 | Yes | OS Upgrades |
| March 6 | No | Small change |
| March 13 | Yes | Network |
| March 20 | No | Small change |
| March 27 | No | Small change |
Second quarter 2025
| Date | Expecting downtime | Type |
| April 3 | Yes | OS upgrade |
| April 10 | No | Small change |
| April 17 | Yes | Minor upgrade with possible announced downtime |
| April 24 | No | Small change |
| May 1 | Yes | OS Upgrade |
| May 8 | No | Small change |
| May 15 | Yes | Infrastructure & hypervisors AND Kubernetes & cluster components |
| May 22 | No | Small change |
| May 29 | Yes | OS upgrades |
| June 5 | No | Small change |
| June 12 | Yes | Network |
| June 19 | No | Small change |
| June 26 | No | Small change |
Third quarter 2025
| Date | Expecting downtime | Type |
| July 3 | Yes | OS upgrade |
| July 10 | No | Small change |
| July 17 | Yes | Minor upgrade with possible announced downtime |
| July 24 | No | Small change |
| July 31 | Yes | OS upgrade |
| August 7 | No | Small change |
| August 14 | Yes | Infrastructure & hypervisors AND Kubernetes & cluster components |
| August 21 | No | Small change |
| August 28 | No | Small change |
| September 4 | Yes | OS upgrade |
| September 11 | No | Small change |
| September 18 | Yes | Network |
| September 25 | No | Small change |
Fourth quarter 2025
| Date | Expecting downtime | Type |
| October 2 | Yes | OS upgrade |
| October 9 | No | Small change |
| October 16 | Yes | Minor upgrade with possible announced downtime |
| October 23 | No | Small change |
| October 30 | Yes | OS upgrades |
| November 6 | No | Small change |
| November 13 | Yes | Infrastructure & hypervisors AND Kubernetes & cluster components |
| November 20 | No | Small change |
| November 27 | No | Small change |
| December 4 | Yes | OS upgrade |
| December 11 | No | Small change |
| December 18 | Yes | Network |
| December 25 | No | Small change |