> For the complete documentation index, see [llms.txt](https://xnet-mobile.gitbook.io/xnet-mobile-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://xnet-mobile.gitbook.io/xnet-mobile-docs/deploy-connect-earn/quickstart-1/maintain-your-deployments.md).

# Maintain your Deployments

{% embed url="<https://dashboard.xnet.foundation/>" %}
Check on your network stats and maximize your $XNET rewards.
{% endembed %}

### Deployment Maintenance Guide

#### 1. Ensure Clear Line of Sight

* Avoid placing your Access Point (AP) behind thick walls, metal objects, or inside enclosures.
* Mount the AP in an open area with good visibility—especially if it supports outdoor coverage.
* Elevation helps! A higher or ceiling mounted position (e.g., window ledge, wall mount, ceiling or rooftop) improves signal propagation.

***

#### 2. Maintain a Reliable Backhaul Connection

* Your AP needs a consistent internet connection to offload traffic to the XNET network.\
  \&#xNAN;*(min. 100mbps* ⬇&#xFE0F;*, min. 10mbps* ⬆&#xFE0F;*)*
* **Avoid using shared, throttled, or unstable WiFi** as your backhaul—connect via **wired Ethernet** only.
* Check with the ISP to ensure sufficient speeds and **NO** strict data caps.
* Your connection to the main internet (backhaul) is important for handling high data traffic (offload). Consider a dedicated Ethernet line to reduce competition for bandwidth. This can boost network performance drastically and increase revenue in premium locations.
* Conduct speed tests onsite to verify bandwidth capacity if you observe an increase in reject rates.

***

#### 3. Use Your Own Router or Gateway for Visibility

* Consider using your own router, gateway or managed switch for more control over your network and access to live traffic metrics. These devices can be deployed for testing and removed as necessary.
* This allows you to monitor bandwidth, uptime, and simultaneous device connections more precisely.

***

#### 4. Power Cycle Occasionally

* If you notice reduced performance, try rebooting your AP and router.
* This can clear temporary network issues or firmware hiccups.

***

#### 5. Periodically Check the Dashboard and Operator Console

* Visit [dashboard.xnet.foundation](https://dashboard.xnet.foundation/) to:\
  \- View sessions, users, rejects, uptime and reward eligibility\
  \- Claim $XNET Epoch rewards
* Log into your [Operator Console](https://console.xnetmobile.com/)\
  \- Ensure devices and venues are correctly input\
  \- Monitor network status\
  \- Assess device metrics

***

#### 6. Watch for Environmental Changes

* New obstacles (like parked trucks, signage, or seasonal foliage) can impact coverage.
* Reassess AP placement if coverage seems reduced over time.

***

By maintaining your deployment with these simple steps, you help ensure stable coverage for users and maximize your earnings on the XNET Mobile network.


---

# 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://xnet-mobile.gitbook.io/xnet-mobile-docs/deploy-connect-earn/quickstart-1/maintain-your-deployments.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.