Status

What each check means

• Redirects — whether scanning a code sends people where it should. This is the one that matters most; everything else can fail without affecting a single printed code.
• Database — code lookups and scan recording.
• Storage — uploaded files and exports. A failure here does not affect redirects.
• Billing — reachability of our payment processor. A failure here means new subscriptions may not complete. Existing codes are unaffected.

Recent incidents

How we monitor

A scheduled job calls our health endpoint every ten minutes from outside our infrastructure. Two consecutive failures open an issue and email us. Server errors are grouped by fingerprint, and a genuinely new kind of error emails us the first time it happens rather than on every occurrence.

You can call the same endpoint we do: https://scanmeplz.com/api/health.

What an outage would and would not affect

Worth being precise, because “the site is down” and “your codes are down” are very different events, and only one of them matters much.

Redirects are served by a single indexed database lookup at whichever Cloudflare edge location is nearest the person scanning. That path does not touch our billing system, our email provider, our file storage or the dashboard. If any of those fail, every printed code in the world keeps resolving and keeps recording scans — the status above will say degraded rather than down.

The only failure that stops redirects is the database itself becoming unreachable. That is the single dependency we have deliberately kept the redirect path down to, and it is why the health check reports it separately from everything else.

Our commitments

• Planned maintenance that could affect redirects is announced here in advance.
• Incidents are posted here while they are happening, not afterwards.
• We do not offer a contractual uptime guarantee on any plan, and we would rather say so than publish a number we have not earned yet. See the terms.