Status
Latchkey status
This page will report whether each part of Latchkey is serving, and carry the record of any incident. Monitoring is not connected yet, so every row below is marked not yet monitored, which is the only honest thing a page like this can say before it is wired up.
Components this page will report
One row per part of the system a customer can feel, taken from the architecture rather than from a marketing grouping. Each will get a current condition and a 90-day history once the heartbeat feed is connected.
- Not yet monitored
Widget delivery
The versioned widget bundles on the CDN, and the per-site config endpoint the loader requests on a visitor page view.
- Not yet monitored
Remediation manifests
The signed per-URL manifests the widget applies in the page, and the API that serves them. The widget runs no model in the browser; if manifests stop serving, remediation stops and the interface keeps working.
- Not yet monitored
Marketing site and free scanner
This website, and the public scan form that queues a scan without an account.
- Not yet monitored
Customer portal
Sign-in, licences and site keys, the install and customisation screens, reports and the billing pages.
- Not yet monitored
Scan and crawl workers
The Chromium workers that run the axe-core 4.10 engine, capture screenshots and compile manifests, plus Flow crawls, scheduled audits and the retention purge.
- Not yet monitored
Inference
The off-box model endpoint behind alt-text and control-label suggestions, and the refusal gate in front of it. When it is unavailable, deterministic fixes are unaffected and inferred ones are declined.
- Not yet monitored
Email delivery
Trial and licence notices, scan reports and the monthly digest.
Services we rely on
These are not Latchkey infrastructure. We will report what we can measure from our own side and nothing more: a checkout canary for the first row, and the age of unprocessed webhook events for the second. We will publish no uptime percentage for someone else’s platform, because we cannot audit it, and each row will link to their own status page so you can escalate where the incident actually is.
- Not yet monitored
Billing and checkout (Dodo Payments)
Dodo Payments is the merchant of record for subscriptions. When checkout is unavailable, new purchases and plan changes are what fail: nobody loses access and no widget stops serving.
- Not yet monitored
Entitlement webhooks (Dodo Payments to Latchkey)
The confirmations that switch a licence on after a payment. A late confirmation delays entitlement on a new purchase; a missing event is a delivery problem, so it never revokes a licence that is already active.
Where this page’s data will come from
Worker heartbeats
The same check that already pauses the scan form on the free scanner when a worker is unreachable. That check exists today; what is missing is the history behind it, so the two surfaces cannot disagree about the same outage.
The widget’s own beacon
Widget error rate comes from the widget’s own beacon, which is cookie-free and stores nothing on the visitor’s device. It is the same count that measures traffic for plan caps, so an error rate here is a number we already hold rather than a new tracker.
The incident record
One incident model with timestamped updates in UTC, generating the page, the email notifications and the feed, so the wording cannot diverge between channels.
A machine-readable endpoint
Uptime percentages will be computed from the same heartbeat and incident data that drives the banner, never typed in by hand, and exposed as JSON so the product’s own maintenance notices read from it rather than from a second source.
Incident history
No incident record to publish
Incidents will be listed here in reverse order with a timestamped update log, grouped by month. Until the record exists, the absence of an entry on this page is not evidence that nothing happened. It only means nothing has been recorded here yet.
Seeing something wrong right now?
Until this page can tell you first, you telling us is the fastest route. Include the site, what you were doing and roughly when: a scan that never finished, a widget that did not appear, a licence that has not switched on after a payment.