> For the complete documentation index, see [llms.txt](https://docs.rtkdata.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rtkdata.com/get-started/network.md).

# NTRIP Server Settings: Hosts, Port, Mountpoints

RTKdata NTRIP connection reference: regional hostnames, IP fallbacks, port 2101, the AUTO mountpoint and how GGA selects your nearest base station.

RTKdata operates a global RTK corrections network with **20,000+ reference stations** and **99.99% uptime** at the NTRIP endpoints. Under open-sky conditions, most users achieve RTK FIX in **5 to 20 seconds**.

***

## Connection Basics

All devices connect using the **NTRIP** (or NTRIPv2) protocol on **port 2101**. Your network must allow **outbound TCP on port 2101**. Firewalls, VPNs, and some mobile carriers can block this port -- see [Troubleshooting](/support/troubleshooting-and-faq.md) if you have connection issues.

You need NTRIP credentials from the [RTKdata Dashboard](https://rtkdata.com/my-account/rtk-credentials/), not your website email and password. See [Account & Credentials](/get-started/account-and-credentials.md).

***

## Regional Servers

Choose the server closest to your work area. All three servers share the same global base station network; the difference is routing latency.

| Region            | Hostname (preferred) | IP Fallback     | Port   |
| ----------------- | -------------------- | --------------- | ------ |
| **Europe**        | `eu.rtkdata.com`     | `3.73.41.96`    | `2101` |
| **North America** | `rtk.rtkdata.com`    | `13.56.117.10`  | `2101` |
| **Australia**     | `aus.rtkdata.com`    | `54.206.56.130` | `2101` |

**When to use the IP fallback:** Some older Android controllers, tablets, and embedded systems cannot resolve DNS hostnames. If your device fails to connect using the hostname, enter the IP address instead.

***

## Mountpoints

Mountpoint names are **case-sensitive** and must be entered in **ALL CAPS**. Use **`AUTO`** unless your project specifically requires a global reference frame. A local coordinate system name is not a mountpoint: entering something like `OSGB36` or `ETRS89` in that field returns no corrections at all.

| Mountpoint          | Description                                                                                                                         |
| ------------------- | ----------------------------------------------------------------------------------------------------------------------------------- |
| **`AUTO`**          | **Recommended.** Delivers corrections in your region's local datum (e.g., NAD83 in the US, ETRS89 in Europe, GDA2020 in Australia). |
| **`AUTO_ITRF2020`** | ITRF2020 at the current epoch                                                                                                       |
| **`AUTO_ITRF2014`** | ITRF2014 at current epoch                                                                                                           |
| **`AUTO_WGS84`**    | WGS84(G2139) at mid-year epoch                                                                                                      |

If your NTRIP client browses the caster, use `AUTO` from the list. It is the mountpoint this documentation covers and the right choice for virtually every workflow.

For the full list of regional datums delivered by `AUTO` per country, see [Coordinate Systems & Datums](/get-started/coordinate-systems-and-datums.md).

### How AUTO Selects a Base Station

When your device connects and sends its approximate position (via NMEA GGA), the RTKdata caster identifies the nearest reference station and begins streaming corrections from it. If you move across a coverage area, the system can hand off to a closer station automatically. This is why **GGA output must be enabled** -- without your position, the caster cannot assign a base station and you will receive no data. See [NTRIP & GGA Essentials](/integration-hub/ntrip-clients-and-field-software/ntrip-and-gga-essentials.md) for details.

***

## Heights

All corrections are delivered with **ellipsoidal heights**. If you need orthometric (mean sea level) elevations, apply a geoid model in your rover software or during post-processing. See [Understanding Heights](/get-started/understanding-heights.md) for guidance.

***

## Quick Reference

```
Host:       eu.rtkdata.com / rtk.rtkdata.com / aus.rtkdata.com
Port:       2101
Mountpoint: AUTO
Username:   (from RTKdata dashboard, starts with "rtk")
Password:   (from RTKdata dashboard)
GGA:        ON (required)
```


---

# 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.rtkdata.com/get-started/network.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.