# Maintenance Windows

Dispel performs regular maintenance to keep our platforms working smoothly.

In the event a planned maintenance window will be accompanied by Downtime[^1] **more than** 10 minutes, we will give you at least 48 hours advanced notice. If you are on a private deployment, we will additionally coordinate with you in advance to find a mutually suitable time. In a year, scheduled Downtime won’t exceed 10 hours.

### Maintenance Windows

{% hint style="success" %}
Dispel's regularly scheduled maintenance windows for our platforms are on the following schedule:\
\
[dashboard.dispel.io](https://dashboard.dispel.io): 10 AM EST - 12 PM (noon) EST **every Tuesday.**

[app.dispel.com](https://app.dispel.com): 10 AM EST - 12 PM (noon) EST **every Wednesday**.
{% endhint %}

### **Customer Impact Scores**

When deploying updates to the Dispel platform, the time and effect on users can vary. We score our deployments to help customers understand how the update window will impact their workflow, to what degree, and what they may see during this time.

The below scoring also includes when we expect to notify our customers prior to the update event. We strive to meet our notification lead times and deploy during [regularly scheduled maintenance windows](#maintenance-windows), but we may not always be able to give lead time notifications in the event of an emergency, bug, or vulnerability fix.

{% hint style="info" %}
Notifications are posted on the Dispel Changelog: <https://dispel.com/changelog>
{% endhint %}

<table><thead><tr><th width="170">Impact Score</th><th>Description</th><th>Notification Lead Time</th></tr></thead><tbody><tr><td>1</td><td>Deployed items do not impact workflows or present visible dashboard changes.</td><td>5 business days</td></tr><tr><td>2</td><td>Deployed items may introduce visible changes, but they do not impact Dispel’s most common workflows.</td><td>5 business days</td></tr><tr><td>3</td><td>Deployed items represent new features or updates to existing features that will affect standard customer workflows.</td><td>15 business days</td></tr><tr><td>4</td><td>Deployed items will require Downtime and migration tasks performed by the customer.</td><td>30 business days</td></tr></tbody></table>

### Vulnerabilities and Critical Bug Fixes

In the event of a vulnerability or critical bug fix, Dispel may enter maintenance mode at any time. We will actively communicate with you with as much reasonable notice as possible.

[^1]: “[**Downtime**](/support/support-policy.md)” means a period of time (as determined by a combination of Dispel's internal and external monitoring systems) during which a large number of Users are unable to log into the service, view their dashboard, and reach any asset they have permission to reach and valid current access to.


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://legal.dispel.com/support/maintenance-windows.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.