SERVICE STATUS · LIVE CHECK

Is ogshot operational?

This page calls the same deployed application that serves renders, account requests, and cached images. It reports the current check honestly; it does not manufacture a historical uptime percentage.

Checking the API…

Requesting /healthz from this deployment.

What this check covers

Application

The Fastify process is reachable and able to answer requests.

Account surface

The status page ships from the same application as sign-in and billing routes.

Image delivery

Cached image responses share the same deployment and response pipeline.

What it does not prove

A health response does not test every target site, third-party OAuth, Stripe, or every Chromium render path.

If a render is failing

Check the machine-readable error first. Policy blocks, target timeouts, invalid HTML, and quota failures can occur while the service itself remains healthy.