No known incidents.
This page is a static placeholder, updated by hand. The one live element is the API check below: a health probe from your browser.
- API, checked from your browser
- Not checked: needs JavaScript
- Updated by hand
- Page up since
- Automated monitoring
- in progress
Components
- API api.knownpass.com Not probed: the live check needs JavaScript
- Admin console admin.knownpass.com Not open yet
- Website passwordradar.eu Operational: you’re reading it
The API check calls GET https://api.knownpass.com/v1/health from your browser each time this page loads. A failed check can also mean that your own network blocks the request.
Incident history
No incidents recorded since this page went up on 4 September 2026.
Scheduled maintenance
None scheduled.
Updates
Incident notes are posted on Telegram, t.me/knownpass (opens in a new tab), until this page is automated. Automated monitoring and uptime history are on the roadmap. If something looks down and isn’t listed here, tell us.
Fail open either way. If the API times out (allow 2 seconds, which also covers opening a new connection), can’t be reached, or returns 429 or 5xx, let the flow continue, log that the check was skipped, and check again at the next login or password change. Log a 400, 401 or 403, or any other error, as an error: nothing is screened until it’s fixed. The docs show how.