Current status
| Component | Status | Description |
|---|---|---|
Analysis API — /v1/analyze | Operational | Image, sound, text and multimodal analysis. |
Index API — /v1/indexes | Operational | Catalog creation, item upsert and retrieval. |
| Visibility platform | Operational | AI answer monitoring, reputation, rank and marketplace tracking. |
| Website | Operational | visibilityzone.com and documentation. |
How this page works. This is a manually maintained status page, updated by our team when an incident or maintenance window occurs. It is not an automated uptime dashboard, and we would rather tell you that than display a graph implying continuous third-party monitoring we do not have in place. Customers with contractual service levels receive incident notifications by email — those do not depend on you checking this page.
Incident history
No incidents affecting customer traffic have been recorded since this page was published on July 26, 2026. Resolved incidents will be listed here with their date, duration, affected components, customer impact and root cause, and will remain published rather than being quietly removed.
Planned maintenance
No maintenance is currently scheduled.
Where maintenance may affect availability we announce it at least 72 hours in advance by email to account owners and on this page. Routine deployments are performed without downtime and are not announced. Breaking API changes are handled separately under our versioning and deprecation policy, which guarantees at least 12 months of notice.
During an incident
- Check this page first — it is updated as the situation develops, not only after resolution.
- Email [email protected] with the subject line Attn: Support. Include the
request_idfrom a failing response — it lets us locate your exact requests immediately. - For transient failures, retry
429,500and503responses with exponential backoff and jitter, as described in the error handling documentation.
After any incident with material customer impact we publish a summary here and send affected customers a post-incident review describing what happened, why, and what we changed to prevent a recurrence.