> For the complete documentation index, see [llms.txt](https://docs.plextrac.com/plextrac-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.plextrac.com/plextrac-documentation/master/deployment-and-maintenance-policy.md).

# Deployment and Maintenance Policy

PlexTrac has region-specific deployment and maintenance windows to accommodate international growth and ensure minimal disruption to the global customer base. This approach offers several key benefits:

* **Targeted updates:** PlexTrac can roll out updates during off-peak hours for each geographic area. 
* **Reduced downtime:** Ensures users experience system improvements outside their primary working hours.
* **Improved responsiveness:** This allows PlexTrac to be more agile in addressing region-specific needs or issues.
* **Better resource allocation:** Provides more targeted support and monitoring, ensuring smoother updates.

## Deployment Regions and Timeframes

The start date for each deployment is listed in the [Release Notes](broken://pages/-M2AKcT4uTEz-1vk8jgv). The process begins in North America, followed by Australia/Eastern Asia and Europe/Western Asia the following day.

<table data-full-width="false"><thead><tr><th width="246">Region</th><th width="267">Deployment Timeframe (MDT)</th><th width="268">Deployment Timeframe (UTC)</th><th>Local Timeframe</th></tr></thead><tbody><tr><td><ol><li>Australia/Eastern Asia</li></ol></td><td>09:00 - 12:00</td><td>15:00 - 18:00</td><td>01:00 - 04:00 (SYD)</td></tr><tr><td><ol start="2"><li>Europe/Western Asia</li></ol></td><td>14:00 - 17:00</td><td>20:00 - 23:00</td><td>21:00 - 00:00 (LON)</td></tr><tr><td><ol start="3"><li>North America</li></ol></td><td>21:00 - 00:00 (following day)</td><td>03:00 - 06:00 (following day)</td><td>23:00 - 02:00 (NYC)</td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.plextrac.com/plextrac-documentation/master/deployment-and-maintenance-policy.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.