← Home

Service status

This page shows whether configured feed URLs are responding, whether scheduled scoring completed, and whether the bounded European beta criteria are met. Direct liveness checks and the mirror-assisted daily run are reported separately because they measure different things. Machine-readable at /api/v1/status.json, /api/v1/run-status.json, and /api/v1/global-coverage.json.

Monitoring status and schedule

The schedule is the service commitment. The liveness record shows what the pipeline observed at each configured feed URL. Machine-readable at /api/v1/status.json.

Current feed URL liveness

As of , direct liveness state covers 2493 current feed records.

Checking clean
2394 (latest direct check succeeded)
Recent check failure
10 (1–6 consecutive direct checks failed)
Flagged unreachable
89 (7 or more consecutive direct checks failed)

Currently checking clean: 96.0% of tracked feed records.

The latest direct checks range from 18.4 to 330.5 hours old. The median is 18.5 hours.

Direct liveness calls each configured feed URL without a mirror. The daily full scoring run can use the Mobility Database mirror, so the liveness counts here and the run totals below answer different questions.

Scheduled checks

Each feed belongs to one of two direct-liveness tiers, and both are checked once a day. A separate full validation is scheduled once daily for every registered feed. The latest-run section below records what that daily work completed.

CheckCadence Applies to
Priorityone direct liveness check each dayfeeds with measured realtime data, and any feed in the expiry danger or recovery window (expiring soon, or recently lapsed)
Standardone direct liveness check each dayevery other tracked feed
Full Validationone full validation each dayevery registered feed

When a check fails

The scorecard keeps the last successful evidence available and makes the degraded state visible:

This section is generated from the liveness state the daily check keeps. It reports only observations the pipeline recorded.

Latest full scoring run

This section reports one completed scoring run. It separates all attempted records from records that remain in the current catalog and shows the age of each published score. Machine-readable at /api/v1/run-status.json.

Run summary

Run completed Recorded 17 hours ago (2026-11-21 13:58 UTC). The run attempted 2512 feed records across 48 of 48 shards. The current catalog contains 2493 feed records.

The badge describes this scoring run, not agency feed availability. Current direct-URL liveness is reported above.

Scored (fresh data this run)
1614
Reused (feed unchanged since last check)
315
Unreachable (all attempted records)
583
Of those, not fetched because of robots.txt
507
Unreachable records still in the current catalog
564
Fell back to the Mobility Database mirror
0
Validator cache hits
1285
Show per-shard breakdown
Outcome counts by CI shard
ShardScored ReusedUnreachableMirrored Cache hitWall clock
055617044974s
1567150461174s
104811190391078s
114713180431206s
124613190331672s
13441816034931s
144514190391004s
1548921035977s
1651621040998s
174815150401086s
18499200401243s
1948921041885s
24120170291089s
20564180491243s
21431619034849s
22547170471104s
23604140471370s
24548160461470s
25489210411161s
265610120421432s
27575160431141s
28507210361244s
29543210391355s
3549150421072s
30575160451498s
315411130421699s
320010014s
330010019s
341000163s
3510000241s
360010017s
370010014s
380010012s
3910000180s
45010180391333s
400010017s
4110001518s
4210000351s
430010017s
440010014s
4510000236s
461000190s
471000158s
54311240351072s
6451023037930s
7501216039819s
8501117037951s
94513200381103s

Feed records unreachable this run

The pipeline could not fetch or validate these currently published feeds in that run; each continues to show its last successful scorecard. A feed host outage is one possible cause, but this evidence does not diagnose why a check failed.

19 additional records were part of this run's attempted set but are outside the current published catalog. They remain in the run totals without being named or linked here.

Catalog freshness

Age of the most recent successful score behind each current scorecard. A score can be older than this run when its source was unchanged or could not be fetched.

Snapshot age distributionAll 2493 tracked feed scorecards, grouped by snapshot age.
Show snapshot-age table
Feed scorecard count by snapshot age
Snapshot ageFeed scorecards
under 1 day0
1-2 days1619
3-7 days7
over 7 days867

Built from the run-status API, refreshed after each completed scoring run. See how to read a scorecard for what the grades themselves mean.

European beta readiness

Not ready The reviewed cohort currently contains 760 GTFS Schedule feed records across 28 countries.

This is a bounded European GTFS Schedule beta gate based on feed records with reviewed reuse evidence. It is not a claim of coverage for all European public transport, and it does not assess NeTEx coverage.

Progress toward the record thresholdReviewed European feed records as a share of the release threshold.
  1. Reviewed feed records100%760 of 250
Reviewed records by countryNo single country may hold more than 40% of the cohort.
  1. France50.8%386 records
  2. Ireland10.5%80 records
  3. Lithuania6.8%52 records
  4. United Kingdom5.4%41 records
  5. Germany4.6%35 records
  6. Spain4.2%32 records
  7. Italy3.9%30 records
  8. Norway3.9%30 records
  9. Finland2.6%20 records
  10. Portugal1.6%12 records
  11. Cyprus0.9%7 records
  12. Poland0.8%6 records
  13. Belgium0.4%3 records
  14. Czechia0.4%3 records
  15. Hungary0.4%3 records
  16. Latvia0.4%3 records
  17. Austria0.3%2 records
  18. Bulgaria0.3%2 records
  19. Switzerland0.3%2 records
  20. Estonia0.3%2 records
  21. Greece0.3%2 records
  22. Denmark0.1%1 record
  23. Croatia0.1%1 record
  24. Iceland0.1%1 record
  25. Luxembourg0.1%1 record
  26. Netherlands0.1%1 record
  27. Slovenia0.1%1 record
  28. Slovakia0.1%1 record

Readiness criteria

Current European beta measures compared with release thresholds
MeasureCurrent ThresholdStatus
Reviewed European GTFS Schedule feed records760at least 250Met
Countries represented28at least 12Met
Largest single-country share50.8%at most 40%Not met
Scorecards retrieved within the inclusive seven-day window49.6%at least 95%Not met
Translation publication measured99.6%at least 100%Not met
Valid portable country and subdivision pair99.6%at least 100%Not met
Feed identity reviewed100%at least 100%Met
Feature finder discloses its feed-record denominatorYesequals YesMet

Exceptions

Coverage-gate exceptions by reason
ReasonCount
No published directory record3
Scorecard is older than the seven-day freshness window380
No feature-finder record3
Translation publication has not been measured3
Portable country and subdivision pair is incomplete or invalid3

A feed record can appear under more than one reason. The JSON lists the affected record identifiers.

Read the auditable global coverage JSON or the global expansion methodology. Counts are feed records, not agencies, operators, routes, or services.