Status
Operational reliability posture and incident communication policy for Generative Metrics.
Risk
Weak pages usually become visible too late.
Response
Find the blocker, fix it, then rescan with intent.
Control
Use the output to replace guesswork with a decision path.
Current Service Posture
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.
Completion time is often 30-120 seconds depending on page complexity and upstream availability, but 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 contact@generativemetrics.com.
API integration reference is available on /api-docs.
Legal terms for warranties and liability are available on /terms.