Service status

We check the redirect and the API every minute and show the numbers here, even when they are not pretty.

Redirect go.kvikqr.com

Unknown

What happens when someone scans a dynamic code and is sent on.

Uptime, 90 days
–
Typical response
–
Last check
–

API api.kvikqr.com

Unknown

The public REST API and what the dashboard is built on.

Uptime, 90 days
–
Typical response
–
Last check
–
  • No downtime
  • Short downtime
  • Longer downtime
  • No checks

How we measure

  • Every minute a job fetches /healthz on both services from Supabase in the EU. Anything other than 2xx, or no answer within 10 seconds, counts as downtime.
  • A minute without a check counts as API downtime, because the API is what runs the checks. So an outage can never look good.
  • We store only the service, time, HTTP status and response time, never anything about visitors, and delete checks after 90 days.

Raw numbers (JSON)