Transparency
System Status
All components operational
Last measurement: 22 Oct 2026 02:05 (Istanbul time). Measurements run every 5 minutes; if a component's last measurement is older than 15 minutes, its status shows "no measurement".
Components
-
SDK delivery
WorkingThe installation code and banner configuration loaded on your sites (loader.js and the configuration file).
- Last measurement
- 22 Oct 2026 02:05
- Response time
- 96 ms
- Last 30 days, operational share of measured time
- 100.00%
-
API
WorkingThe application layer and database behind consent logging, heartbeat and the management API.
- Last measurement
- 22 Oct 2026 02:05
- Response time
- 199 ms
- Last 30 days, operational share of measured time
- 100.00%
-
Dashboard
WorkingThe customer dashboard and sign-in page.
- Last measurement
- 22 Oct 2026 02:05
- Response time
- 197 ms
- Last 30 days, operational share of measured time
- 100.00%
-
Scanning
WorkingThe browser server that runs cookie and accessibility scans, and scan results from the last 24 hours.
- Last measurement
- 22 Oct 2026 02:05
- Response time
- 161 ms
- Last 30 days, operational share of measured time
- 100.00%
no problems at least one failed measurement no measurement
Incident history (last 90 days)
No incidents recorded in the last 90 days.
How it is measured
- Every 5 minutes the cerez.io server requests its own public address: loader.js and the configuration file, the API version endpoint and the dashboard sign-in page must return 200 with the expected content.
- The scanning component checks the separate browser server's health endpoint and counts as having a problem if more than half of at least 3 scans failed in the last 24 hours.
- Two failed measurements in a row open an incident; two successful measurements in a row close it.
- This page cannot show time when the server is completely down: no measurement is possible then and the day stays grey in the bar. This page is not a service level commitment; it shows the measured status.