Effective February 18th 2026, a change has been implemented for the maxTimeout in the Hinterland Container Notification (HCN) tracking API. This change contributes to the stability and reliability of the service. The software vendors affected by this change have already been notified. Below, we explain why you will not experience any negative impact. If you use Hinterland Container Notification via the web screens, you can ignore this update.
The maxTimeout determines how long a request for new updates remains pending. We’ve adjusted this limit in the tracking API. This limitation reduces the number of requests and thus the delay.
This has been adjusted in the tracking API
As of February 18th 2026, a soft limit of 10 seconds has been implemented for the maxTimeout. This means that we will accept requests of <10 seconds, but we will treat them the same as with a maxTimeout of 10 seconds.
A longer maxTimeout doesn’t delay the response. As soon as an update is available, it’s delivered immediately, and a new update request is automatically initiated. This way, the data remains available in real time, and we work together to provide stable and reliable service for all users.
