# Website Uptime Monitoring — Down to 1-Minute Checks · WPCloudLab > Website uptime monitoring down to 1-minute checks: multi-region probes, instant alerts, incident history and public status pages — for WordPress and any stack. Canonical: https://wpcloudlab.com/features/uptime [Home](/)/Uptime uptime · multi-region · down to 1-minute # When the site goes down, you hear it from us first. Downtime is survivable. Hearing about it from your client first is the part that stings. We check any site with a public URL — WordPress or not — from multiple regions, as often as every minute. When one really is down, the alert reaches your channel and an engineer picks it up, usually inside the hour. [Get started](/signup)[see plans & pricing →](/pricing) 001 / how it works5-min · 1-min · multi-region ## Every 5 minutes. Or every 1. Economy and Standard sites are checked from the public URL every five minutes. Extended drops the interval to one minute and adds instant downtime alerts — for the sites where every minute is money. ## Multiple regions, one verdict. When a check fails from one region, the others get a vote before anyone is paged. A flaky route between one datacenter and your host is not an incident — and it won’t wake you like one. ## Incident history, kept. Every confirmed incident is logged: when it started, when it ended, what we saw. Patterns surface in the history — a host that flakes every night at 2am is a conversation worth having. 002 / alertsyour channel · a human attached alerts that mean something ## An alert should come with an engineer. Downtime alerts go to the channel you actually watch — Telegram, for instance — the moment an incident is confirmed. On Extended they arrive instantly, and a real-time Slack channel with our team comes with the plan. Delivery isn’t the point, though. The point is that a confirmed incident puts an engineer on your site — not a red dot in a dashboard you have to notice, interpret and act on yourself. - 01Downtime confirmed from more than one region before anyone is paged - 02Alerts delivered to the channel you actually watch — Telegram, for example - 03Instant downtime alerts on Extended's 1-minute checks - 04An engineer investigates every confirmed incident — no ticket queue - 05Every incident logged, timestamped and kept in your history 003 / status pagescalm · public · no login ## A status page you can hand to clients. Instead of forwarding screenshots of your monitoring, give each client a public status page: a clean page, no login, that answers “is the site up?” before they email you to ask. It reads calm because it usually is. And when something does go wrong, “we saw it, we’re on it” is a much better client conversation than “let me check.” For the longer story — what was done all month, not just whether it was up — there are [client reports](/features/reports). 004 / beyond uptimeexpiry · risk · links up or down is not the whole story ## “Up” is the lowest bar a site can clear. Uptime is one instrument on a bigger panel. The same service watches for the slower failures — the certificate that expires on a Saturday, the risk building up in an unmaintained plugin stack, the links quietly rotting in old posts. ### SSL & domain expiry Renewal reminders for certificates, domains and plugin licenses before they lapse — included from Standard up. Expiry downtime is the most preventable kind there is. ### Maintenance-risk watch Downtime and maintenance-risk monitoring on every plan — the conditions that precede outages, not just the outages themselves. ### Broken-link scans Scheduled crawls catch the 404s and dead outbound links a downtime check never sees. Findings land in your dashboard — details on the [broken-links page](/features/broken-links). 005 / any stackwordpress or not ## Any site with a URL qualifies. Uptime checks run from the public URL — no agent, no plugin, nothing to install. So the same monitoring covers your Next.js apps, static sites and custom stacks alongside WordPress: uptime, broken links, visual regression and client reports, on the same plans. The scope for those sites is monitoring rather than updates and backups — the honest boundary is drawn on the [non-WordPress page](/for/non-wordpress). 006 / questionsmonitoring, plainly ## Uptime questions, answered. How often do you check my site? Every 5 minutes on Economy and Standard, every minute on Extended. Extended also adds instant downtime alerts, so the notification arrives while the incident is seconds old rather than minutes. How do you avoid false alarms? Checks run from multiple regions, and a failure has to be confirmed from more than one before anyone is alerted. A single flaky network path — the classic source of 3am false pages — doesn't count as downtime. Where do the alerts go? The channel of your choice — Telegram is a popular one. Extended plans also include a real-time Slack channel with our team, so an incident becomes a conversation rather than a notification you deal with alone. Can my clients see uptime for themselves? Yes. You can hand each client a public status page — a clean page with no login that answers “is it up?” before they email you. Incident history also lives in your dashboard, and the monthly report tells the longer story. Do you monitor sites that aren't WordPress? Yes — uptime checks need a URL, not a plugin. Next.js apps, static sites and custom stacks get the full monitoring mode: uptime, broken links, visual regression and client reports, at the same plan pricing. Updates and backups remain WordPress-only. What actually happens when my site goes down? You get the alert — and so do we. An engineer looks at every confirmed incident, usually inside the hour, rather than leaving you a red dot to interpret. If the fix is on the site, we handle it; if it's your host, you get specifics to escalate with instead of guesswork. belov.cloud · hosting by the same family ## Webcare from us. Hosting from our other team. belov.cloud is managed WordPress and Node/Next.js hosting built by the founders of Belov Digital — with an always-on AI copilot that detects, diagnoses and fixes incidents in under a minute. Pair it with your care plan and one family of engineers answers for the whole stack: hosting heals the platform, webcare runs updates, backups and reports. - Self-healing: detect → fixed in under 60s, every remedy reversible - Free migration off any host — WP Engine, Kinsta, GoDaddy, anywhere - Flat price — traffic spikes don't spike the invoice [Explore belov.cloud](https://belov.cloud/?utm_source=wpcloudlab&utm_medium=referral&utm_campaign=crosssell&utm_content=features-uptime) 60-day money-back · runs WordPress and Next.js side by side start today · monthly · cancel anytime ## Know your site is down before the client does. Connect a site in a couple of minutes — WordPress or not. Checks start right away, alerts go where you tell them, and the next incident becomes something you told the client about, not the reverse. [Get started](/signup)[or get a free audit first →](/contact) --- Get started: https://wpcloudlab.com/signup · Talk to an engineer: https://wpcloudlab.com/contact · Full agent index: https://wpcloudlab.com/llms.txt