HTTP 503 Service Unavailable
Collection status
Traceary claims to read 61 sources every five minutes and to publish whatever moved. This page is where that claim can be checked. It reports the collection job, so it names a source only when that source has a problem. How fresh any one product is belongs on that product’s own page, next to the releases it affects.
- Last run
- 11 Oct 2026 today
- Sources
- 61 tracked none failing
- Archive
- 4,704 releases 4,704 pages published
- Run log
- 96 runs since 26 Aug 2026
12 Oct 2025 to 11 Oct 2026
Each square is a day. A column is one week, Monday at the top down to Sunday, so the year stands as 53 columns instead of a line that wraps wherever the page ends. A row is the same weekday across the year. Hovering a square names its date.every source readran with failuresno run recorded
The job ran on 45 of the last 365 days, 39 of those reading every source without a failure, and collected 382 new releases.
Sources failing
None. All 61 sources answered on the last run. A source appears here by name, with the error it returned, from the first day it stops answering.
Incidents recorded
HTTP 503 Service Unavailable
fetch failed
fetch failed
HTTP 503 Service Unavailable
response is not a feed, the URL probably serves an HTML page
fetch failed
Quietest publishers
Full catalogThese sources read cleanly. Their publishers have simply not shipped anything for a while, which is worth knowing on its own and says nothing about the collection job.
What a failure means here
A failed read means the feed or the API did not answer with something usable. The archive keeps what it collected before, so a failing source goes stale rather than empty. Five candidate sources were dropped before launch for exactly this reason, and the about page lists them by name.