> For the complete documentation index, see [llms.txt](https://help.verkada.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.verkada.com/transportation/configuration/add-a-transportation-gateway-to-command/transportation-gateway-status-leds.md).

# Transportation Gateway Status LEDs

Learn more about the Verkada KGX61 Ruggedized Transportation Gateway status LEDs

Use this article to learn about different LED characteristics and what they mean for your Transportation gateway. 

***

## KGX61 status LEDs

### Regular operation

The LED status light consists of the following states:

* **Solid orange**—KGX61 is on and booting up
* **Flashing orange**—KGX61 is updating firmware
* **Solid blue**—KGX61 is running and online
* **Flashing blue**—KGX61 is running and offline

<div align="left" data-with-frame="true"><figure><img src="https://3615485688-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5H765ijhDtsUdXyNltrP%2Fuploads%2F4NZBCduMyfiZEIVVEK7t%2FScreenshot%202026-08-14%20at%2010.40.46%E2%80%AFAM.png?alt=media&amp;token=1981bd79-9d82-4c90-add7-0dd19fb49378" alt=""><figcaption></figcaption></figure></div>

### SIM card operation

The LED status light consists of the following states:

* **No light**—No SIM detected
* **Solid white**—SIM card detected
* **Flash white**—SIM card detected and running

<div align="left" data-with-frame="true"><figure><img src="https://3615485688-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5H765ijhDtsUdXyNltrP%2Fuploads%2FQN7Y5VWMniR3SyEIBJpz%2FScreenshot%202026-08-14%20at%2010.40.54%E2%80%AFAM.png?alt=media&amp;token=2b5ae841-8990-497c-bf0a-df93019e3c73" alt=""><figcaption></figcaption></figure></div>

### Signal strength LEDs

The KGX61-HW has two sets of four signal strength LEDs on the port panel, labeled **5G** and **Wi-Fi**.

* **Four lights**—Optimal signal
* **Fewer lights**—Weaker signal
* **No lights**—No signal

<div align="left" data-with-frame="true"><figure><img src="https://3615485688-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5H765ijhDtsUdXyNltrP%2Fuploads%2FL9eLmQ4mSSnyBtYHzlt1%2FScreenshot%202026-08-14%20at%2010.40.50%E2%80%AFAM.png?alt=media&amp;token=d41b79ec-7156-4549-bb3b-78b6ed631578" alt=""><figcaption></figcaption></figure></div>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.verkada.com/transportation/configuration/add-a-transportation-gateway-to-command/transportation-gateway-status-leds.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 `build a script that syncs our docs to a CMS` 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.