> For the complete documentation index, see [llms.txt](https://navixy.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://navixy.com/docs/qna/using-navixy/a-device-is-showing-as-moving-on-the-platform-even-though-it-is-offline.md).

# A device is showing as moving on the platform even though it is offline

Device continues showing its last known status until it comes back online and sends updated location information to the platform

## Question

Why does my device appear to be moving on the platform when it's offline?

![](https://296077121-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5dyjvbUVXEbs60EnxnDz%2Fuploads%2Fgit-blob-50bc911935a732949400a95ae4c29664aab14143%2FUnknown%20image?alt=media)

## Answer

When your device goes offline, the platform continues to show its last known status. If your device was moving when it sent its last update, it keeps showing as "moving" until it comes back online and sends new information.

Think of it like taking a photo - the platform shows you that last "snapshot" of your device's status until it can take a new one. The platform tracks two main things:

* Whether your device is connected (online/offline)
* Whether your device is moving or stationary

For example, if your device last reported that it was moving at 00:08 AM on November 21, 2024, and then went offline, the platform will continue showing it as "moving" since that was its last known state. This happens even though the device itself might have stopped moving after going offline.

## Links

[Connection status](/docs/user/guide/tracking/objects-list/connection-state.md)

[Parking detection widget](/docs/user/guide/devices-and-settings/location-and-movement/parking-detection.md)


---

# 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://navixy.com/docs/qna/using-navixy/a-device-is-showing-as-moving-on-the-platform-even-though-it-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.