> For the complete documentation index, see [llms.txt](https://docs.ndi.video/all/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ndi.video/all/faq/ndi-tools/why-does-my-ndi-connection-stay-active-once-the-source-is-offline.md).

# Why does my NDI connection stay active once the source is offline?

NDI as a protocol is designed for  easy and seamless connections. However, as NDI is also designed to be used across a wide variety of user-implemented networks, the video stream may go offline for to a number of reasons i.e. a pulled cord, lost power, user-caused 'stop' on the device, etc.&#x20;

When a connection is suddenly lost, NDI will handle that as being 'improperly closed'. The receiving end will attempt to keep the sending NDI IP and port number open and available for a number of minutes in case the issue is resolved, so the user won't need to re-discover the NDI source.  By default, it's a 75 minute timeout. If there's been no re-advertisement to renew the time to live, it'll be removed after 75 minutes. Due to this, NDI is designed to hold onto the last frame that was sent as a still within the receiver's buffer and no other image or video signal can use that same IP and Port.


---

# 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.ndi.video/all/faq/ndi-tools/why-does-my-ndi-connection-stay-active-once-the-source-is-offline.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.
