Status and availability
Live status page
Section titled “Live status page”The address https://api.mirac-ozdemir.com/ shows the platform’s real-time health; it refreshes every 5 seconds:
- Components: status and measured latency for the API, the database, the cache and the website.
- Last 60 minutes: an availability strip, request volume and database latency.
- Traffic summary: requests per minute, error rate and latency percentiles.
The page contains only aggregate and anonymous indicators; no personal data, version or infrastructure details are shared. The values belong to the server process; history is reset on restart.
| Status | Meaning |
|---|---|
| Operational | All components are normal. |
| Partial performance issue | A supporting component (cache, website) is slow or down; calculations keep working. |
| Service outage | A critical component such as the database is not responding. |
Maintenance mode
Section titled “Maintenance mode”When a tool or category is temporarily put under maintenance:
availability: "MAINTENANCE"appears in lists and in the definition.- A calculation request returns with
503 MAINTENANCEand aRetry-Afterheader. - The widget shows a maintenance notice instead of the calculation.
Show the user a “temporarily unavailable” message and retry after the Retry-After duration. See Errors.
Setting up your own monitoring
Section titled “Setting up your own monitoring”To monitor your integration’s health yourself, use a lightweight and cached endpoint:
curl -s -o /dev/null -w "%{http_code} %{time_total}s\n" "https://api.mirac-ozdemir.com/v1/public/categories?locale=tr"200is expected; watch the response time and the error rate.- A few requests per minute are enough; respect the rate limits.
- For a real calculation check, you can call the
calculateendpoint a few times a day with a fixed input and compare the result (results are deterministic for the same tool version andasOf). - If you notice a problem, log the
X-Request-Idvalue and send it to us.