Service status
Is it working?
Is it working?
Measured, not asserted.
Every component below is checked when you load this page. Nothing here is typed in by hand: if we cannot measure something, it does not appear.
Checking…
contacting the status service
What each component means
| Component | What is actually checked |
|---|---|
| API | The service answers and can reach its database. Everything else depends on this. |
| Consent ledger | Not that records exist, but that the hash chain is continuous across the most recent entries. Each artefact carries the hash of the one before it, so a break means an entry was altered or removed: the one failure that would invalidate the evidence. |
| Consent banner delivery | The script every customer site loads is being served. |
| Website | This site. |
| Consent dashboard | consent.trytrustable.com, where customers manage notices and read their ledger. |
| Compliance platform | app.trytrustable.com, the full platform. |
How to read it
- Operational: answered normally.
- Slow: answered, but took longer than 2.5 seconds. Working, worth knowing.
- Not responding: no usable answer within four seconds.
- Unverified: the check itself could not run. We show this rather than assume the component is fine.
Results are cached for up to 45 seconds, so a reload may show the same timestamp. Probes run from our API in asia-south1; a surface may be faster or slower from where you are.