Status
Current operational state from a live service check, plus the incident communication policy and reliability expectations for Generative Metrics.
Server-rendered status: the public status page is online. The live check below runs in your browser and requires JavaScript; it refreshes every 60 seconds. Without JavaScript, use the service expectations and incident policy on this page as the current statement.
Current status
Checking…
Last checked --:--:--
Shallow check of the public web app. It does not verify the audit worker, queue, or database.
Refreshes automatically every 60 seconds.
Service expectations
Generative Metrics runs on an asynchronous queue-backed architecture. That gives the platform room to finish harder work, but it also means users should expect results to arrive asynchronously rather than instantly.
Audits usually complete in about a minute (typically 30–120 seconds depending on page complexity). Completion time is not guaranteed.
During this early public-launch period, no formal uptime SLA is guaranteed. Teams that need certainty should treat this as an operational signal, not a contractual promise.
Incident Update Policy
When something goes wrong, status updates are short and specific so teams do not have to guess what changed. Updates include:
- Current state: Investigating, Identified, Monitoring, or Resolved
- Impact summary: affected endpoints and expected behavior
- Start time (UTC)
- Next update ETA
- Mitigation guidance (for example, retry with backoff)
Support
For incident questions, reliability requirements, or SLA discussions, contact [email protected].