> For the complete documentation index, see [llms.txt](https://docs.verifone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verifone.com/support-nordics/t650/how-tos/how-to-check-the-network-information.md).
# How to Check the Network Information
Check a T650 terminal's network status, IP address, connectivity type, and SIM.
{% hint style="info" %}
**Use this when** you need to check a T650 terminal's network details — its network status, Device IP, connectivity type, and preferred SIM.
{% endhint %}
## Check the network information
{% stepper %}
{% step %}
### Open the App Launcher
Slide down on the payment screen from the top, then tap the **9-box grid** symbol at the top next to the Wi-Fi icon.
{% endstep %}
{% step %}
### Open Diagnostics
Select **Diagnostics**.
{% endstep %}
{% step %}
### Open Network Information
Select **Network Information**.
{% endstep %}
{% step %}
### View the network information
You'll be able to view the **network status**, **Device IP**, **connectivity type**, and **preferred SIM**.
{% endstep %}
{% endstepper %}
Keywords
Also called: network information, network info, network status, device IP, connectivity type, check connection, network information check. Search terms: network, IP address, device IP, connectivity, SIM, status, diagnostic.
---
# 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.verifone.com/support-nordics/t650/how-tos/how-to-check-the-network-information.md?ask=&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.
