Bindery status

App

binderypdf.com
GET / · 40 ms
100%
App code
GET /app.js · 26 ms
100%

Accounts

Sign-in (Supabase Auth)
GET /auth/v1/health · 525 ms
100%
Account data (REST + row-level security)
GET /rest/v1/ with the publishable key · 92 ms · HTTP 401
0.00%
Pro checkout (billing function)
POST {} without a session → expects 401 · 210 ms
100%

Brokers

Signature requests
POST {} → expects a 4xx rejection · 244 ms
100%
Encrypted handoff links
POST {} → expects a 4xx rejection · 220 ms
100%
Timestamp proxy
GET → expects 405 · 118 ms
100%
Trusted timestamp authority (end to end, hourly)
POST one RFC 3161 request for a fixed hash · 401 ms
100%

Incidents

How this is measured

A Cloudflare Worker runs these checks from Cloudflare's network every five minutes and keeps ninety days of per-day pass counts. Each bar is one day: green when every check passed, amber when at least 95% did, red below that. An incident opens after 2 consecutive failures and closes on the next pass; the owner is alerted at both edges. No check ever sends a document: the brokers are asked for a rejection, and the timestamp authority is given one fixed SHA-256 hash an hour. The app itself processes PDFs on your device — this page only proves the optional services around it are answering. The raw numbers are at /status.json.