Issue
Private or internal IP addresses (e.g., 10.x.x.x) are repeatedly appearing in your Segment event or session data instead of accurate client IP attribution. This impacts analytics, location enrichment, or reporting that relies on accurate client IP addresses.
Product
Twilio Segment
Environment
Segment Console
Cause
Your source is likely configured to use a deprecated regional endpoint. When the apiHost setting is pointed to a regional endpoint rather than the default endpoint, it can cause internal IP addresses to be captured instead of the actual client IP.
Resolution
To fix this issue, you must check your endpoint configuration and contact Support to make the necessary updates if you cannot directly change the Host Address in the Segment Console.
- Go to your Segment Console and locate the affected source.
-
Access the source’s CDN settings file by navigating to
https://cdn.segment.com/v1/projects/<writekey>/settingsin your browser. -
Search for the setting name
"apiHost"in the file. -
If the value is a regional endpoint (such as
in.eu2.segmentapis.com/v1), contact Segment Support. -
Request that the Host Address be updated to the default endpoint (
api.segment.io/v1). - After Support confirms the change is made, monitor your event data to verify that correct client IP addresses are being captured.
Additional Information
- The Host Address setting may not be visible in the UI and requires support intervention.
- For more details, refer to Segment’s documentation on regional endpoints and IP attribution.
- If you continue to see unexpected IP addresses after the change, reach out to Segment Support for further assistance.