Status

Headlark has no live status dashboard yet. This page says how we watch the service and how you hear about problems.

How we check

An automated check runs every hour from GitHub Actions. It confirms that the snippet is served from the CDN and that the API answers. A failed check alerts us right away. Failed and stuck batches alert us too.

Incidents

When an incident affects your site, we email the address you sign in with. To report a problem or ask about one, write to headlark.info@gmail.com.

What an outage means for your site

• Your visitors are never affected by our API. Nothing runs when someone views your page: tags from the build step are already in your HTML, and the snippet reads a cached file.
• If the API is down during a build, the CLI leaves each page as it was and the build continues. With --strict the build fails instead.
• A deploy or publish webhook that fails can be repeated by deploying or publishing again. Unchanged pages come from cache.

Past changes are in the changelog.