Zenovay checks whether your site is reachable on a schedule and emails you when it goes down, so you find out before your visitors do.
How it works
Once your tracking script is installed and your domain is verified, Zenovay automatically starts checking your site. There's nothing extra to set up: every verified website you own is monitored.
- Automatic checks: Zenovay requests your homepage on a schedule from the Cloudflare edge.
- Status detection: a site counts as "up" when the request succeeds with the expected status code (any 2xx–4xx by default; you can require an exact code).
- SSL tracking: Zenovay watches your certificate's expiry date and chain validity (Pro and above).
- Incident detection: repeated failures open an incident automatically and email you; recovery closes it.
- History: availability percentage and response times are tracked over time.
Info
Uptime monitoring runs for verified websites. If you haven't installed the tracking script and verified your domain yet, start with the Quick Start.
Opening the Uptime tab
- Go to Domains and open the website you want to inspect.
- In the sidebar, under Behavior, select Uptime.
You'll see the current status, an availability chart, a response-time chart, the per-period uptime table, and (on Pro and above) incident, status-code, and SSL detail cards.
Configuring a monitor
On Pro and above, click the gear in the Uptime tab header to open the monitor settings.
Monitor settings
Check interval: How often Zenovay checks the site
Expected status: The HTTP status code that means "up" (default 200)
Keyword check: Optional text that must appear in the response body
Alert threshold: Consecutive failures before an incident opens (default 3)
Alert channels: Email (Slack and webhooks coming soon)
SSL monitoring: Track certificate expiry and chain validity
Keyword check is useful when your site returns a 200 even though something is broken (for example, an error page that still loads). Zenovay fetches the page and confirms the text you specify is present; if it's missing, the check is marked as down.
Check intervals by plan
The minimum check interval depends on your plan:
| Plan | Minimum interval |
|---|---|
| Free | 10 minutes |
| Pro | 5 minutes |
| Scale | 1 minute |
| Enterprise | 1 minute |
You can choose any interval at or above your plan's minimum (1, 5, 10, 15, 30, or 60 minutes). Tighter intervals are shown locked with an upgrade prompt.
Alerts
When a site fails the configured number of consecutive checks (3 by default), Zenovay opens an incident and emails the workspace owner. When the site recovers, the incident is resolved and a recovery email is sent.
- Email alerts are sent to the workspace owner. Make sure email is enabled in the monitor settings.
- Slack and webhook channels are listed in settings but are not active yet ("coming soon").
The alert email includes the affected domain, the status code or error, when the incident started, and a link straight to the Uptime tab.
Incidents
Incidents appear in the incident feed inside the Uptime tab (Pro and above).
- Auto-detected incidents open after the consecutive-failure threshold is reached and close automatically when the site recovers. The duration is calculated for you.
- Manual incidents can be created and updated if you want to log something the automatic checks didn't catch. Each incident moves through
investigating→identified→monitoring→resolved.
Incident: example.com is down
Started: 10:15:00
Status: investigating → resolved
Duration: 8 minutes
Detail: Site returned HTTP 503
SSL certificate monitoring
On Pro and above, with SSL monitoring enabled, Zenovay tracks your certificate so an expiry never catches you off guard.
SSL certificate
Issuer: Let's Encrypt
Valid until: 2026-09-12
Days remaining: 91
Chain valid: Yes
Grade: A
The grade drops as expiry approaches (A above 30 days, B above 7, C in the final week, F once expired or the chain is invalid). SSL is checked periodically as part of the uptime run.
Response times and status codes
The Uptime tab also tracks how your site responds, not just whether it's up:
- Response time: median (p50) plus p95 and p99 percentiles over the selected window.
- Status-code breakdown: the share of checks returning 2xx / 3xx / 4xx / 5xx, so you can spot a site that's "technically up" but increasingly erroring.
A rising p95/p99 or a growing share of 5xx responses is often an early warning before full downtime.
Viewing windows by plan
How far back the Uptime tab lets you look depends on your plan:
| Plan | Uptime history |
|---|---|
| Free | 7 days |
| Pro | 30 days |
| Scale | 90 days |
| Enterprise | 90 days |
Raw individual checks are kept for 7 days; daily availability summaries are retained longer so the longer windows still show a continuous trend.
Best practices
- Set an expected status code if your homepage should always return a specific code (for example, 200). Otherwise any response below 500 counts as up.
- Add a keyword check for pages that can fail "softly" while still returning a 200.
- Tune the alert threshold so a single transient blip doesn't page you, but a real outage does. Three consecutive failures is a sensible default.
- Enable SSL monitoring so a forgotten certificate renewal never becomes an outage.
- Keep email alerts on for the workspace owner so downtime reaches a human.
Troubleshooting
I'm not seeing any uptime data
- Confirm the website is verified (tracking script installed). Only verified sites are monitored.
- New monitors need a few check cycles to populate. Give it one or two intervals.
I'm not getting alert emails
- Open the monitor settings and confirm the Email channel is enabled.
- Alerts go to the workspace owner's email address.
- An incident only opens after the configured number of consecutive failures, so a single brief blip won't alert.
SSL data is missing
SSL is checked periodically during the uptime run, not on every single check. If you just enabled it, wait for the next cycle. SSL monitoring is a Pro and above feature.