Fix log: Via Mobility

A dated record of every data issue this feed has cleared since tracking began. Each entry keeps its own link, so a specific fix can be cited in a board packet, a grant report, or an NTD narrative.

17 verified fixes

8 of 13 trips scheduled during the sampling window had no live predictions. (scorecard_rt_trip_coverage) Reported through 2026-07-08; the 2026-07-09 check verified it gone. What this finding means. Link
3 of 17 sampled vehicle positions were far from their assigned route (worst: 3361 m). (scorecard_rt_vehicles_off_route) Reported through 2026-07-07; the 2026-07-08 check verified it gone. Link
6 of 13 trips scheduled during the sampling window had no live predictions. (scorecard_rt_trip_coverage) Reported through 2026-07-07; the 2026-07-08 check verified it gone. What this finding means. Link
1 of 2 trips scheduled during the sampling window had no live predictions. (scorecard_rt_trip_coverage) Reported through 2026-07-06; the 2026-07-07 check verified it gone. What this finding means. Link
6 of 28 sampled vehicle positions were far from their assigned route (worst: 4908 m). (scorecard_rt_vehicles_off_route) Reported through 2026-07-05; the 2026-07-06 check verified it gone. Link
Foreign key violation (flagged by the MobilityData validator). (foreign_key_violation) Reported through 2026-07-05; the 2026-07-06 check verified it gone. Link
5 of 28 sampled vehicle positions were far from their assigned route (worst: 2984 m). (scorecard_rt_vehicles_off_route) Reported through 2026-07-04; the 2026-07-05 check verified it gone. Link
6 of 14 trips scheduled during the sampling window had no live predictions. (scorecard_rt_trip_coverage) Reported through 2026-07-04; the 2026-07-05 check verified it gone. What this finding means. Link
Some live predictions disagree with the schedule by more than 30 minutes. (scorecard_rt_predictions_implausible) Reported through 2026-07-04; the 2026-07-05 check verified it gone. Link
1 of 8 trips scheduled during the sampling window had no live predictions. (scorecard_rt_trip_coverage) Reported through 2026-07-02; the 2026-07-03 check verified it gone. What this finding means. Link
Some live predictions disagree with the schedule by more than 30 minutes. (scorecard_rt_predictions_implausible) Reported through 2026-06-30; the 2026-07-01 check verified it gone. Link
Some live predictions disagree with the schedule by more than 30 minutes. (scorecard_rt_predictions_implausible) Reported through 2026-06-27; the 2026-06-28 check verified it gone. Link
3 of 16 sampled vehicle positions were far from their assigned route (worst: 1055 m). (scorecard_rt_vehicles_off_route) Reported through 2026-06-24; the 2026-06-25 check verified it gone. Link
2 of 8 trips scheduled during the sampling window had no live predictions. (scorecard_rt_trip_coverage) Reported through 2026-06-24; the 2026-06-25 check verified it gone. What this finding means. Link
Some live predictions disagree with the schedule by more than 30 minutes. (scorecard_rt_predictions_implausible) Reported through 2026-06-24; the 2026-06-25 check verified it gone. Link
Some live predictions disagree with the schedule by more than 30 minutes. (scorecard_rt_predictions_implausible) Reported through 2026-06-21; the 2026-06-22 check verified it gone. Link
6 of 12 trips scheduled during the sampling window had no live predictions. (scorecard_rt_trip_coverage) Reported through 2026-06-19; the 2026-06-20 check verified it gone. What this finding means. Link

Verified means the daily check stopped reporting the finding. A finding that returns and clears again appears as a separate entry.

This log is the end of the guided fix loop: you make a change, republish, and the next run verifies it and records it here as linkable proof for a board packet or NTD narrative.