Resource details
Information sur l’état du trafic en temps réel
This resource file is part of the dataset Réseau urbain Sylvia.
Download availability
Learn more
HEAD request with a timeout of 5 seconds. If we detect a downtime, we perform subsequent tests every 10 minutes, until the resource is back online.For SIRI and SIRI Lite feeds, we perform a
GET request: a 401 or 405 status code is considered successful. In case of HTTP 500, the feed will be considered unavailable, unless the body appears to contain SOAP.Validation details
❌18 errors, 37 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2026-08-07 at 09:00 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
GTFS-rt agency_id does not exist in GTFS data E034 18 errors
All agency_ids provided in the GTFS-rt alert.informed_entity.agency_id should also exist in GTFS agency.txt
Sample errors
- alert ID DEOBUS:alert:6a6079493704052004f4e855 agency_id DEOBUS does not exist in the GTFS data agency.txt
- alert ID DEOBUS:alert:6a6079493704052004f4e855 agency_id DEOBUS does not exist in the GTFS data agency.txt
- alert ID DEOBUS:alert:6a6079493704052004f4e855 agency_id DEOBUS does not exist in the GTFS data agency.txt
- alert ID DEOBUS:alert:6a6079493704052004f4e855 agency_id DEOBUS does not exist in the GTFS data agency.txt
- alert ID DEOBUS:alert:6a6079493704052004f4e855 agency_id DEOBUS does not exist in the GTFS data agency.txt
Warnings
trip missing trip_id W006 18 errors
trip should include a trip_id
Sample errors
- entity ID DEOBUS:alert:6a6079493704052004f4e855 does not contain a trip_id
- entity ID DEOBUS:alert:6a6079493704052004f4e855 does not contain a trip_id
- entity ID DEOBUS:alert:6a6079493704052004f4e855 does not contain a trip_id
- entity ID DEOBUS:alert:6a6079493704052004f4e855 does not contain a trip_id
- entity ID DEOBUS:alert:6a6079493704052004f4e855 does not contain a trip_id
Header timestamp is older than 65 seconds W008 1 error
The data in a GTFS-realtime feed should always be less than one minute old
Sample errors
- header.timestamp is 4119 min 8 sec old which is greater than the recommended age of 65 seconds
schedule_relationship not populated W009 18 errors
trip.schedule_relationship and stop_time_update.schedule_relationship should be populated
Sample errors
- entity ID DEOBUS:alert:6a6079493704052004f4e855 does not have a schedule_relationship
- entity ID DEOBUS:alert:6a6079493704052004f4e855 does not have a schedule_relationship
- entity ID DEOBUS:alert:6a6079493704052004f4e855 does not have a schedule_relationship
- entity ID DEOBUS:alert:6a6079493704052004f4e855 does not have a schedule_relationship
- entity ID DEOBUS:alert:6a6079493704052004f4e855 does not have a schedule_relationship
Previous validations
Here is a recap of all the error types encountered over the last 30 days.
| Error ID | Description | Errors count | Number of occurences |
|---|---|---|---|
| W008 | The data in a GTFS-realtime feed should always be less than one minute old | 29 | 29 times (100 % of validations) |
| E034 | All agency_ids provided in the GTFS-rt alert.informed_entity.agency_id should also exist in GTFS agency.txt | 54 | 3 times (10 % of validations) |
| W006 | trip should include a trip_id | 54 | 3 times (10 % of validations) |
| W009 | trip.schedule_relationship and stop_time_update.schedule_relationship should be populated | 54 | 3 times (10 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2026-08-08 at 02:55 Europe/Paris.
vehicle_positions (0) service_alerts (0) trip_updates (0)Entities seen in the last 7 days.
service_alertsDecoded GTFS-RT feed
See full payload
Here is the decoded GTFS-RT feed Protobuf at 2026-08-08 at 02:55 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "1.0",
"timestamp": "1786150522"
}
}