<aside>
Check here before reporting a discrepancy.
This log lists operator-side issues we already know about. If you recognise one of these in a feed, there is nothing extra to report — we are tracking it with the operator.
</aside>
<aside>
NMBS/SNCB Abnormally low matching rate between static and RT
Ongoing
The NMBS-SNCB GTFS feed currently has some ongoing issues with their Static and Real Time data. A low matching rate for the tripUpdates is expected until those are resolved.
</aside>
<aside>
TEC *VehiclePositions: fewer vehicles in the latest feed than in the legacy API*
Ongoing
The TEC latest vehicle positions feed publishes 20 to 35% fewer vehicles than the legacy API. Vehicles that stop reporting remain published with a frozen position until the next drop. This behaviour is present at the source, TEC has been informed and we are waiting for their analysis.
</aside>
<aside>
TEC *fieldValue and recordId dual entries in translations.txt*
Ongoing
The TEC GTFS feed's translations.txt mixes recordId-based and fieldValue-based translations. Both methods are used to identify the record being translated, each living in its own row. This is expected and does not indicate a data conflict.
</aside>
<aside>
GTFS-RT *Last-Modified* header in ISO 8601 instead of HTTP-date
Fixed
The GTFS-RT feed endpoints set the Last-Modified header from the feed header timestamp to an ISO string instead of the HTTP-date format required. The feed content itself is not affected.
The fix will switch the Last-Modified format; no other changes expected.
</aside>