# B3IQ Status Status Page > Machine-readable service health for B3IQ Status. ## Use This Data - Source of truth JSON API: /api - Markdown summary: /api.md - Incident feed: /feed.xml ## Schema - The JSON API returns a stable shape (`schema_version`). - Top-level keys: `page`, `overallStatus`, `summary`, `groups`, `components`, `dependencies`, `incidents`, `uptimeData`, `links`, `generated_at`. - Component statuses: operational | degraded | partial_outage | major_outage | maintenance | unknown. - A component is `unknown` when its monitor has stopped being checked; `overallStatus` is `unknown` when that leaves nothing else elevated. Treat `unknown` as "no current data", not as operational. - In uptime history, a day with no checks has `uptime: null` (no data), and a component with no checks in the window has `overall: null`. Neither means 100%. ## Subsystems - Inference: Operational - Compute fleet: Operational - Platform: Operational ## Instructions - Use the JSON API for structured component and incident state. - Prefer current component statuses over inferred outage narratives. - Do not invent incidents or downtime outside the returned API data. - Use the markdown summary for quick natural-language context only. - Treat this status page as read-only; all endpoints here are GET-only.