The PTV Layer Delivery Server (LDS) is now only reachable at lds.ptvlogistics.com. The old URL lds.ptvgroup.com is no longer available from 16 November 2026. If your PTV Content Update Service (CUS) still points to the old URL, your PTV xServer no longer receives dynamic content such as current traffic incidents and toll updates.
What has changed
| Old | New (mandatory) | |
|---|---|---|
| Host | lds.ptvgroup.com | lds.ptvlogistics.com |
| Protocol | HTTP or HTTPS | HTTPS only |
Who is affected
- All PTV xServer on-premise installations (API version 1 and 2) that use dynamic content via the CUS, for example traffic incidents or toll updates.
- Installations running a CUS version earlier than 2.34.0. These versions still contain the old URL in their configuration.
- CUS 2.34.0 and later already contain the new URL. No change is required, provided the file contentupdateservice.conf has not been modified or replaced by an older configuration file.
Option A (recommended): Update the Content Update Service
The latest version contains the new LDS URL and current security fixes, so updating is the preferred path in every case.
- Log in to the PTV xServer Customer Area (https://account.myptv.com/) and switch to the product "PTV xServer on-premise customer area".
- Download the latest version of the PTV Content Update Service.
- Back up your current CUS installation and configuration files.
- Install the new version as described in the section "Using Content Update Service" of the PTV xServer Administrators guide.
- Start the CUS and check the connection (see "Check the connection" below).
Option B (temporary): Adjust the configuration of a running CUS 2.x.x
Use this option only if an update is not possible at short notice. It restores the connection to the LDS but does not fix known security vulnerabilities in older CUS versions. Please plan the update described in Option A as soon as possible.
Applies to PTV Content Update Service 2.x.x earlier than 2.34.0, configuration file contentupdateservice.conf.
- Locate the file contentupdateservice.conf in the configuration directory of your CUS installation.
- Create a backup copy of the file.
- In the provider section, replace every occurrence of ptvgroup.com with ptvlogistics.com. Make sure that both URLs (rest.url and broker.url) use https://.
- Save the file and restart the PTV Content Update Service so that the change takes effect.
- Check the connection (see below).
Configuration after the change:
provider {
ptvlogistics-lds {
rest.url = "https://lds.ptvlogistics.com/lds/rest"
broker.url = "https://lds.ptvlogistics.com/ldsbroker"
polling {
enabled = true
interval = 120s
}
}
}Change only the host names and the protocol. Keep all other settings, such as polling, as they are in your current configuration.
Check the connection
- Outbound HTTPS connections (port 443) from the CUS host to lds.ptvlogistics.com are permitted by your firewall and, if used, your proxy server.
- No configuration file of the CUS still refers to lds.ptvgroup.com.
- After the restart, the CUS log files show no connection errors to the LDS.
- New dynamic content, for example the Traffic Incidents Feature Layer, is received and available in the PTV xServer.
Further information
PTV xServer Blog: Urgent migration update: New URL for dynamic content (https://xserver-blog.ptvlogistics.com/2026/01/28/urgent-migration-update-new-url-for-dynamic-content/)
Still not working?
Please contact PTV Support and include your CUS version and the relevant lines from the CUS log file.
Comments
0 comments
Please sign in to leave a comment.