Status & incidents¶
Venturi reports service health through the dashboard, API, and customer communication channels. Incidents are classified by customer impact, affected surface, freshness, and recovery path.
Degradation states¶
| State | Meaning |
|---|---|
| Healthy | Data is current and services are within target. |
| Delayed | Attribution is still correct but freshness is outside target. |
| Partial | One source or pathway is degraded; unknowns may increase. |
| Unavailable | A serving-plane surface is down or cannot complete requests. |
| Recovering | The service is replaying events or rebuilding indexes. |
Customer AI traffic remains fail-open through these states.
Incident lifecycle¶
- Detect the impact through monitoring, customer report, or health checks.
- Classify severity and affected surfaces.
- Communicate status and expected next update.
- Mitigate or fail to a conservative operating mode.
- Recover, verify freshness, and close the incident.
- Publish a post-incident summary where the customer agreement requires one.
What customers can see¶
The product shows degradation state, connector freshness, index freshness, and whether results are estimated, reconciled, stale, or unavailable.