> For the complete documentation index, see [llms.txt](https://docs.os.uk/os-apis/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.os.uk/os-apis/service-and-data-status/service-disruption-and-planned-maintenance.md).

# Service Disruption and Planned Maintenance

This page provides details of service disruption and planned maintenance events affecting the availability of data through the OS APIs.

{% hint style="info" %}

#### API service status <a href="#api-service-status-and-os-ngd-data-issues" id="api-service-status-and-os-ngd-data-issues"></a>

Any live interruptions to the availability of the OS APIs will be documented on the [Service Status Dashboard on the OS Data Hub](https://osdatahub.os.uk/support/status). The dashboard is updated every 10 minutes and shows the status of OS APIs over the last 24 hours to indicate whether they are available, degraded or have interrupted availability.
{% endhint %}

## Resolved service disruption

An issue that affected the availability of the **OS Places API** change only updates (COU) for 6 August 2026 has been successfully resolved.&#x20;

The updates for 6 August 2026 have now been correctly applied as part of the 7 August 2026 release (GMT 17:16).

## Planned maintenance <a href="#os-ngd-planned-maintenance" id="os-ngd-planned-maintenance"></a>

No maintenance events are currently scheduled that will impact the availability of the OS APIs.


---

# 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.os.uk/os-apis/service-and-data-status/service-disruption-and-planned-maintenance.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.