TL;DR: if shipping logs to the Logz.io EU endpoint returns `401: Logging token is not valid` even with a fresh token, your account probably lives in the US region. The listener URL depends on where your account lives, not where you are. Accounts default to US; if your app URL contains `app.logz.io` your account is US and you must ship to `listener.logz.io:8071`, not `listener-eu.logz.io:8071`. A genuine EU-region account has to be requested through sales/support.

```text
401: Logging token is not valid
```

## Steps

1. Check your Logz.io app URL. If it contains `app.logz.io`, your account is US-region.

2. Point your shipper at `listener.logz.io:8071` instead of the EU listener.

   Expected: logs flow. Success check: entries appear in your Logz.io account.

3. If you truly need EU residency, request an EU-region account through sales/support; you cannot self-serve it.

## When to use this

- 401 on listener-eu.logz.io:8071 with a token that works on listener.logz.io:8071.
- Default (US) Logz.io account.

## When NOT to use this

- The token fails on both listeners; the token itself is the problem.
- You already have a genuine EU account; check the token and config.

## Compatibility

- Logz.io log shipping, all regions.

## Variant phrasings

- "logz.io 401 logging token not valid EU"
- "logzio listener-eu unauthorized"

## Root cause

Tokens are region-scoped to the account, so a US token presented to the EU listener is correctly rejected as invalid.

## Edge cases

- Being physically in Europe does not make your account EU-region; only the account's home region matters.