Resource details
Download availability
2024-04-20
99.4%
2024-04-21
100%
2024-04-22
100%
2024-04-23
100%
2024-04-24
100%
2024-04-25
100%
2024-04-26
100%
2024-04-27
99.7%
2024-04-28
100%
2024-04-29
99.7%
2024-04-30
100%
2024-05-01
100%
2024-05-02
100%
2024-05-03
100%
2024-05-04
99.7%
2024-05-05
100%
2024-05-06
100%
2024-05-07
99.7%
2024-05-08
99.7%
2024-05-09
100%
2024-05-10
100%
2024-05-11
100%
2024-05-12
100%
2024-05-13
100%
2024-05-14
100%
2024-05-15
100%
2024-05-16
99.8%
2024-05-17
100%
2024-05-18
100%
2024-05-19
100%
2024-05-20
100%
Learn more
We test this resource download availability every hour by making an HTTPHEAD
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.
Validation details
✅No error detected
Validation carried out using the current GTFS file and the GTFS-RT the 2024-05-19 at 09:05 Europe/Paris using the MobilityData GTFS-RT validator.
Validate this GTFS-RT nowPrevious validations
Here is a recap of all the error types encountered over the last 30 days.
Error ID | Description | Errors count | Number of occurences |
---|---|---|---|
E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 2 456 | 22 times (73 % of validations) |
W001 | Timestamps should be populated for all elements | 281 | 22 times (73 % of validations) |
E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 26 | 11 times (37 % of validations) |
E004 | All route_ids provided in the GTFS-rt feed must exist in the GTFS data | 26 | 11 times (37 % of validations) |
E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 319 | 11 times (37 % of validations) |
E025 | Within the same stop_time_update, arrival and departures times can be the same, or the departure time can be later than the arrival time - the departure time should never come before the arrival time. | 13 | 9 times (30 % of validations) |
E045 | If GTFS-rt stop_time_update contains both stop_sequence and stop_id, the values must match the GTFS data in stop_times.txt | 81 | 3 times (10 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2024-05-20 at 08:57 Europe/Paris.
service_alerts (0) trip_updates (0) vehicle_positions (0)Entities seen in the last 7 days.
trip_updatesDecoded GTFS-RT feed
See full payload
Here is the decoded GTFS-RT feed Protobuf at 2024-05-20 at 08:57 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfs_realtime_version": "2.0",
"timestamp": "1716188231"
}
}