## TL;DR
Fix this in geolocation enrichment by acting on the exact message first: add a private-range check before the geolocation call so addresses in private ranges are tagged internal with the site or VPN gateway location, and only public addresses go to the geo provider. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one item, then rerun the full scope and reconcile the counts.

```text
geolocation enrichment error private IP marked external
```

## Use this when
- The operation in geolocation enrichment fails with this exact message: geolocation enrichment error private IP marked external.
- The same failure repeats on retry with unchanged inputs.
- A review, export or check is blocked until this item completes.

## Not for this skill when
- The message is a permission or outage notice from the platform. Resolve that first, then return here if this error remains.
- The operation completes and you only disagree with its output. That is a quality review, not this failure.

## Steps
1. Reproduce the failure with the smallest scope that still shows it in geolocation enrichment, and copy the full message plus the alert, incident or enrichment record involved into the run notes. Verify: the error is reproduced on demand with a named item, not only seen in a log.
2. Apply the specific fix for this error: add a private-range check before the geolocation call so addresses in private ranges are tagged internal with the site or VPN gateway location, and only public addresses go to the geo provider. Verify: a test alert with a private source address is tagged internal and public test addresses still geolocate.
3. Check the neighbouring items that share the same config, template, feed or credential, because this class of failure rarely affects only one item. Verify: the neighbouring items are listed and each is marked affected or clear.
4. Compare the result counts, decisions or alerts against the source in geolocation enrichment so a silent partial success is caught before sign off. Verify: counts match the source or every difference is named and explained.
5. Rerun the original operation in geolocation enrichment on the previously failing scope, watching for the same message rather than assuming success from a quiet log. Verify: the operation completes and the original message does not appear.
6. Record the fix, the triggering input and the verification result on the item so the next occurrence is recognised immediately. Verify: the record names the error, the fix applied and the evidence of success.

## Why it happens
the enrichment sent every address to the geo provider without a range check, and the provider returned a misleading external location for private addresses.

## Variant phrasings

### geolocation enrichment error private IP marked external
The verbatim form searchers paste from the terminal or console. Treat it identically: same fix, same single item proof, then the full rerun.

### How to fix: how to fix geolocation enrichment error private IP marked external failure
The how-to phrasing for the same failure in geolocation enrichment. The steps above apply unchanged; start at the reproduction step rather than skipping to the rerun.

### geolocation enrichment troubleshooting for this failure
The symptom-first phrasing used when the console hides the full message. Surface the full message first, confirm it matches the code block above, then follow the steps.

Compatibility: geolocation enrichment at current versions, plus the platform API or console the query names; no extra tooling beyond a text editor and the source system access needed to verify counts.

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_XrddnyFisjRJk6hmS9On0Q