One high-confidence freshness issue and one matching issue require owner review.
Fictional sample report
24-Hour Rider Information Reliability Scan
This sample shows the report structure, evidence style, and claim discipline used by mobility.rest. All agency names, URLs, incident times, and metrics are fictional demonstration data.
Successful fetches divided by scheduled fetch attempts.
Computed against disclosed scheduled-service denominator.
Only calculated where entity timestamps were present.
Sustained issue, not a single-sample alert.
Advisory warning before static service expires.
01 / Scope and method
Outside-in observation of public feeds.
The scan observed one public GTFS Schedule feed and three public GTFS Realtime endpoints. No private systems, credentials, rider records, or internal logs were accessed.
Included endpoints
- GTFS Schedule ZIP
- Trip Updates protobuf
- Vehicle Positions protobuf
- Service Alerts protobuf
Evidence collected
- Scheduled fetch attempts and outcomes
- Raw payload hashes and parse status
- FeedHeader age and entity timestamp coverage
- Schedule archive checksum and feed shape
02 / Executive summary
Rider-facing realtime reliability degraded during the morning peak.
The public endpoints were mostly reachable, but Vehicle Positions entities became stale while the top-level FeedHeader remained current. That pattern suggests the endpoint was alive while route-level vehicle updates were delayed or missing.
Primary risk:
Arrival displays may have shown stale vehicle locations for route 14 during peak rider demand.
03 / Prioritized findings
Findings are written as evidence, impact, owner, and next action.
High confidence
01
Vehicle entity timestamps were stale during the morning peak.
- Observed fact
- Route 14 vehicle entities exceeded the 90-second freshness target for 63% of observations between 08:42 and 09:31.
- Potential rider impact
- Arrival displays may have shown stale vehicle positions during a high-demand service period.
- Likely owner
- Evidence suggests realtime vehicle export or CAD/AVL handoff. Outside-in observation cannot prove the private-system root cause.
- Recommended next action
- Compare vehicle export logs for route 14 between 08:30 and 09:45 against the public Vehicle Positions feed.
Medium confidence
02
Realtime coverage dropped after the latest Schedule publication.
- Observed fact
- Static-to-Realtime match rate dropped from 91% to 78% after three route identifiers changed in the Schedule feed.
- Potential rider impact
- New or renamed routes may not receive live arrival data in consuming systems until identifiers are aligned.
- Likely owner
- Schedule publishing workflow or realtime ID mapping.
- Recommended next action
- Confirm whether route ID changes were intentional, then stage matching changes across Schedule and Realtime feeds.
Advisory
03
The active Schedule feed expires in 11 days.
- Observed fact
- The latest service date in the active feed is 2026-06-29. No newer publication was observed during the scan window.
- Potential rider impact
- If not republished, downstream systems may lose current service data after the feed expiration date.
- Likely owner
- Agency scheduling or data publishing workflow.
- Recommended next action
- Publish an updated Schedule feed before the current service period ends.
04 / GTFS Realtime evidence
Endpoint success did not equal useful freshness.
06:00
Vehicle position freshness
16:00
| Endpoint | Fetches | Parse status | Freshness evidence | Interpretation |
|---|---|---|---|---|
| Trip Updates | 2871 / 2880 | 99.8% valid | P50 14s, P95 47s | Generally healthy |
| Vehicle Positions | 2872 / 2880 | 99.9% valid | P50 66s, P95 242s | Degraded during peak |
| Service Alerts | 2868 / 2880 | 100% valid | FeedHeader age under 10m | No alert lifecycle issue observed |
05 / GTFS Schedule evidence
Schedule checks anchor the Realtime review.
Raw feed archived by checksum for reproducibility.
Core files present, including service calendar data.
Advisory risk because less than 14 days remain.
Prior snapshot supplied by customer for count comparison.
06 / Technical appendix
Evidence rows preserve denominators and limitations.
| Time | Source | HTTP | Bytes | Hash | Parser |
|---|---|---|---|---|---|
| 08:51:04 | /gtfs-rt/vehicle-positions | 200 | 184,220 | 9c12...af31 | valid protobuf |
| 08:51:05 | /gtfs-rt/trip-updates | 200 | 91,774 | 0f44...91b0 | valid protobuf |
| 03:10:22 | /gtfs/schedule.zip | 200 | 7,421,990 | f178...a130 | parsed archive |
Limitations
- This report does not certify legal, GTFS, or GTFS Realtime compliance.
- This report does not guarantee ingestion by proprietary trip planners.
- Outside-in observation cannot prove private-system root cause.
- A 24-hour window may not represent seasonal, weekend, event, or low-frequency service.
Ready for a real scan?