> For the complete documentation index, see [llms.txt](https://docs.korewireless.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.korewireless.com/kore/supersim/into-production/super-sim-network-timeouts.md).

# Super SIM Network Timeouts

Learn about the timeouts applied by Super SIM's mobile core to internet traffic

Super Core, KORE's cloud-native mobile core that connects your Super SIM connected devices to the internet, makes use of inactivity timers when devices establish internet connections through it. These timers depend on the communications protocol in use — TCP or UDP — and are initiated when the device stops transmitting data via the specified protocol. If the device transmits more data before a timer fires, Super Core's NAT (Network Address Translation) unit will continue to route relevant packets to the device's network IP address. If the timer expires, the NAT can release the address translation resource.

These NAT timeouts are separate from any inactivity timeout a visited network may apply to the device's PDP context, the data connection the device establishes via the local carrier network. Such timeouts are set by the carrier, not Super Core, and may depend on whether the network knows the device's location. On some networks, known-location devices are allowed longer inactivity periods because there is less or no likelihood that the inactivity is the result of the device moving to another cell or network.

The current inactivity timeout values are as follows:

| NAT Timer    | Default Value            |
| ------------ | ------------------------ |
| TCP          | 6 hours (21,600 seconds) |
| UDP          | 30 seconds               |
| UDP (stream) | 12 seconds               |


---

# 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.korewireless.com/kore/supersim/into-production/super-sim-network-timeouts.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.