linkring status
All checks passing
30 days, oldest on the left.
10 runs between 2026-08-10 and 2026-09-08, 3 of which failed — 70%.
Last checked 2026-09-08 10:11 UTC. Checked every ten minutes. This page is rebuilt by the same run.
Days with a failure
What is checked
- A published page
- The page path end to end: the custom domain, the cache, R2, and the object that was published to it.
- Sign in
- The door. A page that is up while nobody can sign in is not a working product.
- The promises
- The documents render from markdown at build time; a broken build shows up here.
- Click counting
- What a published page's ping posts to. It answers 204 to anyone, so probing it is honest.
- The API refuses a stranger
- A 401 here is the session check working. A 200 would be the outage that matters most.
- The other address
- linkring.co is a signpost, not a second home. A 308 to the same path on linkring.to is the whole of what it does.
Where this comes from
A scheduled job in the linkring repository makes those requests against the live site and fails if one of them is wrong. Every run above is one of those jobs. There is no third-party monitor: if this page and the site went down together, they went down together, and the run history on GitHub is the record that outlives both.