The Keelnest badge.

A small badge for your site’s footer or your README that says the app is watched — and, if you choose, how often it answered over the last thirty days. It is off until you turn it on, and it never says more than anyone could learn by opening your site.

What it looks like

  • Example badge: Watched by · dark

    Watched by · dark

  • Example badge: Watched by · light

    Watched by · light

  • Example badge: Uptime · dark

    Uptime · dark

  • Example badge: Uptime · light

    Uptime · light

These are examples. Your badge shows your own app’s state.

What each state means

The badge speaks for the five-minute site check alone — the request a browser would make for your production address.

The badge saysWhich means
onlineThe last check got a working page over HTTPS, in time.
degradedThe site answered, but something was off: a slow answer, a redirect to plain HTTP, or an unusual status visitors can still get past.
downThe site could not be reached, answered a server error, or answered a status that leaves a visitor with nothing.
pausedWatching is switched off for this app, or it was archived.
checkingNo check has finished in the last twenty minutes, so the badge does not repeat an old answer as the present one.

The uptime figure is the share of five-minute checks over the last thirty days in which the site was not down. It appears once there is a full day of checks — until then a new app would read 100% on the strength of a few answers, which is not a thing a badge should claim. It is never rounded up: 99.996% reads 99.99%.

What it never shows

Payments, journeys, spend, publishes and incidents. Those are yours, and a badge is public by definition. The badge carries no app name either; the alt text you paste is the only label, and you write it.

Adding it

  1. Open the app in Keelnest and go to Configuration.
  2. Turn on Show a public badge, and pick the style and the ground it will sit on.
  3. Copy the HTML for a web page or the Markdown for a README, and paste it where the badge should appear.

The code looks like this, with your badge’s own address in place of the capitals:

HTML
<a href="https://keelnest.com/?ref=badge" target="_blank" rel="noopener"><img src="https://keelnest.com/badge/YOUR-BADGE-ADDRESS.svg" alt="Watched by Keelnest" height="20"></a>
Markdown
[![Watched by Keelnest](https://keelnest.com/badge/YOUR-BADGE-ADDRESS.svg)](https://keelnest.com/?ref=badge)

Add ?style=uptime for the two-part badge with the thirty-day figure, and ?theme=light for a light ground. The badge links to keelnest.com.

Caching, and turning it off

The picture is cached for five minutes, the same interval the checks run on, so it is never more than a check or two behind. Turning the badge off removes its address: every page still embedding it shows a missing image until the code is taken out. New address does the same to the old address and gives you a new one, for a badge that ended up somewhere it should not be.

The rules behind each state are on What Keelnest checks.

Earn the badge.

Keelnest watches your production app every five minutes and tells you in plain English what broke — with the fix. Free for your first app.