CFTS Documentation

Maintenance and Change Notices

This page explains how planned maintenance, emergency maintenance, and client-requested changes are normally handled.

Scheduled Maintenance

CFTS may perform scheduled maintenance to preserve platform reliability, security, and operational continuity.

Scheduled maintenance may include:

  • infrastructure patching
  • security updates
  • storage maintenance
  • network maintenance
  • monitoring updates
  • platform upgrades
  • capacity adjustments

Where practical, reasonable notice will be provided before planned maintenance.

Emergency Maintenance

Emergency maintenance may be required where delay could create security, stability, continuity, or operational risk.

Emergency maintenance may be performed with reduced notice or without prior notice where operationally required.

Examples include:

  • urgent security remediation
  • failing infrastructure component
  • active abuse or compromise
  • storage or network protection action
  • power or environmental risk
  • upstream provider issue requiring immediate routing change

Maintenance Impact

Maintenance may result in:

  • no visible impact
  • brief interruption
  • degraded performance
  • service restart
  • temporary access restriction
  • planned failover

The expected impact will be communicated where known and practical.

Change Notices

Maintenance or change notices may include:

  • affected service
  • reason for change
  • planned date and time
  • expected duration
  • expected impact
  • client action required
  • rollback or recovery notes where relevant

Client-Requested Changes

Clients should request changes in advance where practical.

Examples include:

  • DNS changes
  • firewall changes
  • access changes
  • storage expansion
  • backup retention changes
  • migration windows
  • operating system or application changes under managed scope

Requests should include desired timing, business impact, rollback expectations, and technical details.

SLA Treatment

Scheduled maintenance windows are excluded from uptime calculations under the Infrastructure SLA.

Emergency maintenance required to preserve infrastructure stability or security may also be excluded from SLA calculations according to the SLA terms.

Client Preparation

Before planned changes, clients should:

  • confirm business impact
  • notify internal users where needed
  • pause risky application activity during the window
  • ensure recent data exports exist where appropriate
  • identify a validation contact
  • confirm any application checks needed after completion