linkring status

All checks passing

30 days, oldest on the left.

3566 runs between 2026-10-09 and 2026-11-07, 1 of which failed — 100%.

Last checked 2026-11-07 10:39 UTC. The checks run every ten minutes; this page is rebuilt hourly, so it can be up to an hour behind them.

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 database behind the door
The only check that spends a query. `/signin` renders without one, so without this a driver or a database that is gone reads as a perfectly healthy site.
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 addresses the product left behind
Every sign-in email sent before the cut-over points at linkring.to/_/. A 404 here is those people locked out, and nothing else would notice.

Where this comes from

Two monitors make those requests against the live site. A Cloudflare Workers cron runs them every ten minutes from inside the network, which is most of the bars above; a scheduled job in the linkring repository runs the same seven hourly from outside it, which is the only vantage point that can see the domain stop answering altogether. Either one falling silent is reported here as a failure, because a monitor nobody is checking is not a monitor. There is no third-party service behind this: if this page and the site went down together, they went down together.