Uptime monitoring with 1-minute checks and instant alerts
Watch your website, API endpoints, and SaaS dependencies from multiple regions. We ping every minute on paid plans (every 5 minutes on the free plan) and email you the moment something breaks — and again the moment it recovers.
1-minute interval checks
Lite, Pro, and Business plans probe every 60 seconds from multiple regions. Free plan checks every 5 minutes from a single region. HTTP/HTTPS, custom headers, expected status codes, body content match.
Email alerts on state change
We confirm with 3 consecutive failures before paging you (so blips don't spam) — then email immediately. Recovery alerts when the site comes back.
Multi-region probes
Paid plans run checks from up to 10 regions across the Americas, Europe, and Asia-Pacific simultaneously. Distinguish real outages from regional networking blips. Free plan probes from a single region.
Uptime monitoring is a commodity — the basics (HTTP check, email alert, status page) are available from a dozen vendors for under $10/month. UptimeRobot, Better Stack, and Pingdom all do this well. So why bundle uptime into Nevision?
Because correlation matters. When a monitor fires, the next questions are always: did this affect real users? what errors did they see? is the API actually down or is the frontend broken? With a standalone uptime tool, those answers live in three other dashboards. With Nevision, you click the alert, you see the spike in 5xx errors, the spike in JavaScript exceptions, and the affected user sessions, all on the same timeline.
What we check, in detail
Each monitor performs an HTTPS request from probes in US-East, EU-West, and AP-Southeast. You can configure: expected status code (default 2xx), required response headers, required body substring, custom request method (GET/HEAD/POST), custom request headers (for authenticated endpoints), and timeout (default 10s). Failures are aggregated across regions — if 1 region fails but 2 succeed, we log it but don't alert. If all 3 fail consecutively for 3 cycles, you get an email.
Plan limits
Free: 3 monitors at 5-minute intervals from 1 region. Lite ($12/mo): 10 monitors at 1-minute intervals from 3 regions. Pro ($39/mo): 25 monitors at 1-minute intervals from 5 regions. Business ($99/mo): 75 monitors at 1-minute intervals from 10 regions. Higher limits available — contact us.
How it works
Add a monitor
Paste a URL, set the check interval, optionally configure expected status code, headers, or response body match.
We probe from 3+ regions
Every check runs from US, EU, and Asia in parallel. Results are aggregated and stored as time-series data.
Alert on confirmed downtime
After 3 consecutive failures across regions, you get an email. Same when the monitor recovers. Status pages auto-update.
How Nevision compares
| Feature | Nevision | UptimeRobot | Better Stack | Pingdom |
|---|---|---|---|---|
| Free monitors | 3 (5 min) | 50 (5 min) | 10 (3 min) | — |
| Paid plan starts at | $9/mo | $8/mo | $24/mo | $15/mo |
| Min check interval | 1 min | 1 min | 30 sec | 1 min |
| Multi-region probes | Pro+ | |||
| Includes session replay | — | — | — | |
| Includes error tracking | — | — | — | |
| Includes RUM | — | — | ||
| Public status pages | Coming soon |
Comparison based on publicly listed pricing and features as of May 2026.
Frequently asked questions
How quickly will I get alerted if my site goes down?+
On Lite/Pro/Business with 1-minute checks: typically within 3-4 minutes (we wait for 3 consecutive failures across regions to avoid false positives). On the free 5-minute plan: up to ~15 minutes worst case.
What protocols are supported?+
HTTP and HTTPS today. TCP, ICMP (ping), and DNS checks are on the roadmap.
Can I monitor authenticated endpoints?+
Yes. Configure custom request headers per monitor (e.g. Authorization: Bearer …). The header is encrypted at rest.
Do you support status pages?+
Public status pages are launching Q2. In the meantime, the dashboard shows live status, response time charts, and incident history per monitor.
What if my service is just slow, not down?+
Set a max response time threshold per monitor. Responses slower than the threshold count as failures, even if the status code is 200.