CodeMonster.ai · by Knomatic Status
There is no public status page yet. This is how you hear from us when something breaks, and how to reach a person while it is broken.
This page is not a live health indicator yet — we are choosing a status-page provider. Until it is live, incident notices go by email to the administrative contacts of every licensed organization, and the link lands here the day it exists. The fastest confirmation today is support@codemonster.ai: tell us what you were doing, and we answer with what we know and when the next update lands.
Three things fail independently: the apps you have already deployed, the build-and-promote chain, and the MCP control surface your agent talks to. Every incident notice names which of the three is affected, so you know straight away whether your end users are seeing it.
Last reviewed 14 August 2026. This page carries no uptime figure. Commitments will be published when we can stand behind them contractually; when a public status page is live, its history will be the record.
- Who is told. The administrative contacts on your organization's license, by email, from support@codemonster.ai.
- How to be added. Send the addresses to support@codemonster.ai. A shared inbox or an on-call alias works, and most teams add one.
- What is sent. What is affected, when it started, what we know, and the next update time. Updates continue until the incident is resolved.
- Where it will also appear. On the public status page once a provider is chosen; the link will be placed here.
- Security incidents. Reports reach us through the vulnerability disclosure process. Notification runs directly to affected organizations, and the notification terms — who we tell, and how fast — are in the DPA.
Write to support@codemonster.ai or use the contact form with the support topic. Include your organization name, what you were doing, and — if you were building through your agent — the operation you called and the exact error text.