> For the complete documentation index, see [llms.txt](https://docs.kpnthings.com/kpn-things/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kpnthings.com/kpn-things/building-blocks/devices/routers.md). # Routers If you have a proposition that supports routers and you have a routers subscription, then you can view the status of your routers by clicking on Routers in the menu. ## Routers page The router page shows a list of your wireless routers. The data shown, is retrieved from the Router Management Platform (RMS). The actual router management is done in the RMS, which can be reached using the break-out buttons in the list.

Elements on the page are: * The name of the router * The name of the KPN Things project, this router belongs to * The router model name * The router status (Online, Offline, Pending) * The ICCID of the (primary) SIM-card that is inserted in the router * The IMEI of the the router * The signal strength that is measured by the router (in dBm) * The version of the routers firmware * Information on credits for this router: * Credit Type * Credit Expiry Date --- # 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.kpnthings.com/kpn-things/building-blocks/devices/routers.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.