# Status > Platform status, incident history and maintenance windows, hosted outside our own cluster so that it survives the outages it reports. A status page that goes down with the outage is not a status page. Ours runs outside our own infrastructure, so it can tell you the truth on the day it matters. https://status.cmdz.com · Per region · Incident history and post-mortems ## Per component, per region ### API and portal Availability and latency of the control plane. ### Deploy pipeline Build queue depth and release success rate. ### Managed services Databases, cache, object storage, per region. ### Ingress and DNS Edge, certificates and the authoritative nameservers. ## What we publish afterwards. Every incident that affected customers gets a written post-mortem: what happened, what the impact was, what the cause turned out to be, and what changed as a result. We publish them whether or not the cause reflects well on us, and we do not quietly stop publishing them in a bad quarter. You can subscribe to updates per region, so a Frankfurt customer is not paged about Rotterdam maintenance. ``` ● all systems operational 12 Jul nl-rtm-1 degraded build queue 42 min cause: builder cache volume full fix: headroom alarm at 65% 03 Jun all API latency p99 > 2 s 11 min cause: unindexed query on usage rollup fix: index + query budget in CI ``` [Open the status page](https://status.cmdz.com)