> For the complete documentation index, see [llms.txt](https://knowledgebase.fabricdata.com/fabric-knowledge-base/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.fabricdata.com/fabric-knowledge-base/support/releases/environment-availability-and-uptime.md). # Environment Availability & Uptime ## Environment releases & deployments Fabric's approach to environment releases and deployments aim to minimise disruption to users and maintain maximum availability for client production environments. Fabric's deployment process typically does not cause any downtime during production releases. In situations where a change has the potential to cause disruption to users, Fabric proactively communicates with clients to arrange a suitable release window before deploying to production environments. To ensure seamless and efficient deployment, Fabric adheres to **Bitbucket's best practices for deployments**. This approach helps to ensure that code changes are thoroughly tested and validated before being deployed to production, reducing the risk of errors or bugs that may result in downtime or performance issues for clients. * **Test Deployments:** QA deployments are thoroughly before releasing code changes to production environments. This includes functional testing, performance testing, and regression testing. Clients will also have 2 weeks following their QA environment release to flag any issues or concerns they would have with promoting their QA environment → Live/Production environment. * **Monitor Deployments:** Fabric Monitors deployments and production environments to detect and address issues quickly. Bitbucket Pipelines are designed with alerts and notifications for failed deployments, errors, and performance issues. * **Rollbacks:** Fabric has detailed rollback plans in place in the case of a failed deployment or unexpected issues. We use Bitbucket Pipelines to automate rollback procedures and ensure that backups are in place. Fabric has a monthly release cadence for production environments to ensure the scope of the changes are always manageable. All releases including times and dates will be communicated with clients via email, the [website](https://www.fabricdata.com/release-notes), and with the clients customers project or customer success managers. {% hint style="info" %} Customers can implement a code freeze if they wish to ensure their environment has no changes during a particular time period. {% endhint %} ## ## Environment stability & architecture To maintain maximum client environment stability, Fabric implements a range of best practices and processes. The below measures are aimed at minimising the risk of downtime or service disruptions. ### **1. High Availability Architecture** Fabric’s [architecture](/fabric-knowledge-base/support/infrastructure/architecture-overview-diagrams-and-components.md) is designed with redundancy built-in at every layer. Fabric uses load balancers, multiple servers, and redundant databases to minimize single points of failure. ### **2. Continuous Monitoring** Fabric runs continuous system monitoring using a combination of tools such as log analysis, application performance monitoring (APM), and network monitoring to detect and flag issues early to ensure proactive remediation. ### **3. Automated Recovery and Failover** Fabric uses automatic recovery and failover mechanisms for critical software components. Including automated backups, auto-scaling, and automated failover to other servers in the event of an outage. ### **4. Practice Disaster Recovery** Fabric has a comprehensive [disaster recovery plan](/fabric-knowledge-base/support/infrastructure/disaster-recovery.md) in place and runs practice drills to test its effectiveness. ### **5. Support Desk** Fabric’s [support desk](/fabric-knowledge-base/support/service-desk.md) is also available for all customers in the event of an outage or failure with technical & incident response teams available. ***
Related Articles * [Change & Release Management](/fabric-knowledge-base/support/releases/change-and-release-management.md) * [Security](/fabric-knowledge-base/support/security.md) * [Infrastructure](/fabric-knowledge-base/support/infrastructure.md)