Status
Transparency about the data pipeline: when it last ran, how many API calls it used and whether anything went wrong.
Current state
- Last collection: 2026-11-19 10:27:59 UTC (healthy)
- Data through: 2026-11-17; page generated 2026-11-19 10:28:06 UTC
- Public repositories tracked: 276
Recent runs
| Started | Mode | Fetched | Skipped | API calls | Budget left | Duration | Result |
|---|---|---|---|---|---|---|---|
| 2026-11-19 10:27 UTC | incremental | 0 | 276 | 6 | 4994 | 7s | ok |
| 2026-11-19 03:46 UTC | incremental | 69 | 207 | 272 | 4929 | 61s | ok |
| 2026-11-18 10:18 UTC | incremental | 263 | 12 | 658 | 4992 | 135s | ok |
| 2026-11-17 10:48 UTC | incremental | 62 | 213 | 248 | 4925 | 62s | ok |
| 2026-11-16 09:52 UTC | incremental | 67 | 206 | 266 | 4990 | 61s | ok |
| 2026-11-15 11:31 UTC | full | 269 | 0 | 688 | 4956 | 122s | ok |
| 2026-11-15 10:45 UTC | incremental | 0 | 269 | 6 | 4980 | 3s | ok |
The hourly GitHub API allowance is 5,000 requests per token. Runs stop safely when the remaining budget gets low.
Monitoring
A daily watchdog checks that the published data is fresh. A failed or partial run, a large traffic spike and every finished weekly report create an alert issue in the repository (and an optional Telegram message). See the methodology for how collection works and changelog for releases.