Skip to main content
Zenovay
Free5 minutesBeginner

Zenovay Status Page

How to read status.zenovay.com, subscribe to incident notifications, and understand maintenance windows and component statuses.

statusuptimeincidentsnotifications
Last updated:

Zenovay's public status page lives at status.zenovay.com. It shows the live health of every customer-facing service, lists current and recent incidents, and announces scheduled maintenance.

What the status page shows

Component statuses

Every customer-facing service has its own status indicator:

ServiceWhat it covers
Dashboard (app.zenovay.com)Logging in, viewing analytics, configuring websites
Tracker ingestion (api.zenovay.com)Events sent from your sites being recorded
APIProgrammatic access via the External API and CLI
Authentication (auth.zenovay.com)Login, signup, MFA, password reset
Documentation (docs.zenovay.com)Public docs, API reference, changelog
Help Center (help.zenovay.com)This help center

A component is operational when its automated health checks pass, degraded when latency or partial errors exceed the alert thresholds, partial outage when only some functionality is affected, and major outage when the service is broadly unreachable.

Incidents

When an incident is open, it appears at the top of the page with:

  • A short title and impact summary
  • The affected components
  • A timeline of updates as the team investigates, identifies, and resolves the issue
  • An auto-resolve note if Zenovay's monitors confirmed recovery

Past incidents stay visible for 90 days so you can verify whether a problem you saw was on our side.

Scheduled maintenance

Planned maintenance windows are announced in advance with the affected components, the expected impact (read-only mode, brief unavailability, etc.), and the start/end times in UTC plus your local time.

Subscribing to notifications

Click Subscribe in the top right of status.zenovay.com to choose how you'd like to be notified:

  • Email — incident creation, status changes, and resolution
  • RSS / Atom feed — for Slack, Microsoft Teams, or any feed reader
  • Webhook — for piping incidents into your own monitoring stack

Subscriptions are scoped per component, so you can opt into only the parts of Zenovay you depend on (for example, Tracker ingestion if you don't use the dashboard).

Status banners inside the dashboard

When an incident is active, a banner appears at the top of app.zenovay.com linking to the relevant incident page. The banner disappears automatically once the incident is resolved.

Reporting an issue

If you're seeing a problem that isn't reflected on the status page, contact Zenovay support — the status page reflects automated health checks plus signals raised by the team, so individual customer-specific issues (e.g. a single misconfigured website) won't always trigger a public incident.

Include the time the issue started, the affected URL, and any x-request-id header values from failing API responses — those let us trace the request end-to-end.

Was this article helpful?