← 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 2026-10-07 19:47 UTC, direct liveness state covers 2474 current feed records.

Checking clean: 2334 (latest direct check succeeded)
Recent check failure: 18 (1–29 consecutive direct checks failed)
Flagged unreachable: 122 (30 or more consecutive direct checks failed)

Currently checking clean: 94.3% of tracked feed records.

The latest direct checks range from 1.0 to 4.0 hours old. The median is 1.1 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. A separate full validation is scheduled once daily for every registered feed. The latest-run section below records what that daily work completed.

Check	Cadence	Applies to
Priority	one direct liveness check every 3 hours	feeds with measured realtime data, and any feed in the expiry danger or recovery window (expiring soon, or recently lapsed)
Standard	one direct liveness check in each 6-hour period, on a stable per-feed schedule that spreads requests across the period	every other tracked feed
Full Validation	one full validation each day	every registered feed

When a check fails

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

If a fetch fails, the last successful scorecard remains available. The pipeline recalculates only its calendar-based freshness and expiry fields. It never rewrites an older snapshot.
A feed whose calendar has been past its expiry date for more than 365 days is labeled 'stale' rather than 'lapsed', which changes how it is described but not whether it is served.
A configured feed URL is labeled 'unreachable' after 30 consecutive direct checks fail (roughly a week at standard cadence). This is separate from an expired calendar.
These observations do not guarantee an agency's GTFS host will stay online. The status page records what the pipeline observed and when.

This section is generated from the same liveness state used by the intraday refresh. 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 5 hours ago (2026-10-07 14:24 UTC). The run attempted 2495 feed records across 48 of 48 shards. The current catalog contains 2474 feed records.

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

Scored (fresh data this run): 2009
Reused (feed unchanged since last check): 397
Unreachable (all attempted records): 89
Unreachable records still in the current catalog: 68
Fell back to the Mobility Database mirror: 83
Validator cache hits: 1551

Show per-shard breakdown

Outcome counts by CI shard
Shard	Scored	Reused	Unreachable	Mirrored	Cache hit	Wall clock
0	63	12	3	4	48	1772s
1	63	14	1	2	49	1639s
10	63	11	4	4	53	1637s
11	64	13	1	2	43	1459s
12	60	16	2	1	44	1760s
13	65	11	2	4	53	1930s
14	65	10	3	5	50	1605s
15	65	8	4	2	52	1798s
16	61	11	5	4	50	998s
17	59	15	3	3	44	1547s
18	61	12	4	6	45	1486s
19	63	9	5	4	47	1578s
2	62	14	2	3	49	1404s
20	65	9	3	3	50	1569s
21	58	15	4	3	47	1612s
22	59	17	1	2	47	1909s
23	63	14	0	2	49	1190s
24	62	14	1	1	49	1673s
25	63	11	3	2	46	1197s
26	64	10	3	2	48	1675s
27	65	7	5	1	50	1399s
28	63	13	1	1	52	1313s
29	57	15	5	2	47	1575s
3	58	18	2	5	45	1357s
30	61	11	5	2	43	1434s
31	69	8	0	1	49	2033s
32	1	0	0	0	0	1304s
33	1	0	0	0	0	230s
34	1	0	0	0	0	145s
35	1	0	0	0	0	214s
36	1	0	0	0	1	58s
37	1	0	0	0	1	330s
38	1	0	0	0	0	192s
39	1	0	0	0	0	220s
4	64	14	0	1	50	1554s
40	1	0	0	0	0	128s
41	1	0	0	0	1	474s
42	1	0	0	0	0	391s
43	0	0	1	0	0	28s
44	0	0	1	0	0	23s
45	1	0	0	0	0	286s
46	1	0	0	0	1	108s
47	1	0	0	0	1	56s
5	60	17	1	1	44	1228s
6	63	11	4	4	52	1531s
7	60	13	5	3	48	1691s
8	60	14	4	1	50	1427s
9	67	10	1	2	53	1688s

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.

21 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 2474 tracked feed scorecards, grouped by snapshot age.

Show snapshot-age table

Feed scorecard count by snapshot age
Snapshot age	Feed scorecards
under 1 day	2012
1-2 days	7
3-7 days	422
over 7 days	33

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.

Reviewed feed records100%760 of 250

Reviewed records by countryNo single country may hold more than 40% of the cohort.

France50.8%386 records
Ireland10.5%80 records
Lithuania6.8%52 records
United Kingdom5.4%41 records
Germany4.6%35 records
Spain4.2%32 records
Italy3.9%30 records
Norway3.9%30 records
Finland2.6%20 records
Portugal1.6%12 records
Cyprus0.9%7 records
Poland0.8%6 records
Belgium0.4%3 records
Czechia0.4%3 records
Hungary0.4%3 records
Latvia0.4%3 records
Austria0.3%2 records
Bulgaria0.3%2 records
Switzerland0.3%2 records
Estonia0.3%2 records
Greece0.3%2 records
Denmark0.1%1 record
Croatia0.1%1 record
Iceland0.1%1 record
Luxembourg0.1%1 record
Netherlands0.1%1 record
Slovenia0.1%1 record
Slovakia0.1%1 record

Readiness criteria

Current European beta measures compared with release thresholds
Measure	Current	Threshold	Status
Reviewed European GTFS Schedule feed records	760	at least 250	Met
Countries represented	28	at least 12	Met
Largest single-country share	50.8%	at most 40%	Not met
Scorecards retrieved within the inclusive seven-day window	98.4%	at least 95%	Met
Translation publication measured	99.6%	at least 100%	Not met
Valid portable country and subdivision pair	99.6%	at least 100%	Not met
Feed identity reviewed	100%	at least 100%	Met
Feature finder discloses its feed-record denominator	Yes	equals Yes	Met

Exceptions

Coverage-gate exceptions by reason
Reason	Count
No published directory record	3
Scorecard is older than the seven-day freshness window	9
No feature-finder record	3
Translation publication has not been measured	3
Portable country and subdivision pair is incomplete or invalid	3

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.