Website over HTTP(S)
We request your page and record the status code and response time. Choose the method, send headers, and expect a specific code.
Monitoring
Website uptime monitoring with fewer false alarms
Website uptime monitoring gives you a way to check availability without refreshing every client site yourself. MonitoraWeb checks websites on a schedule, confirms repeated failures, and keeps a history you can review when a site becomes unavailable.
How website uptime monitoring works
Add the sites that matter to your business
Start with your company website, an online store, or the client sites you maintain. Use one dashboard to keep track of their availability rather than testing each URL by hand.
Choose the right check interval
Free checks websites every five minutes. Pro and Agency check every 60 seconds. A one-minute interval describes check frequency, not a promise to alert you within one minute.
Confirm failures before declaring an outage
MonitoraWeb currently checks from a single location. It requires three consecutive failures and retries each failed check after ten seconds before confirming downtime. This reduces reactions to isolated errors without claiming multi-region verification.
10:42:03 tienda-ejemplo.com 200 214 ms 10:43:03 tienda-ejemplo.com 503 failure 1 of 3 — no alert 10:44:03 tienda-ejemplo.com 503 failure 2 of 3 — no alert 10:45:03 tienda-ejemplo.com 503 CONFIRMED → alert sent 10:52:03 tienda-ejemplo.com 200 198 ms 10:53:03 tienda-ejemplo.com 200 RESOLVED → 8 min down
What else you can monitor
API with JSON assertions
Beyond the status code and timing, we read the response: up to 10 rules on JSON fields (exists, equals, contains, greater or less than, regular expression…). If “status” stops saying “ok”, you hear about it even when the API returns 200.
Keyword
We check that a piece of text still appears. If “Add to cart” disappears, the store loads but can't sell, and a monitor that only reads the status code won't notice.
Ping, TCP and UDP ports
For services that don't speak HTTP: a mail server, a database, or a service on its own port. Over UDP we send a packet and wait for the answer, as with your own DNS, NTP, or VoIP. We check that it answers and how long it takes.
DNS records and domain
A DNS monitor queries a record (A, AAAA, CNAME, MX, NS, TXT, SOA, or CAA) and alerts you if it stops answering, changes, or no longer says what it should. We also watch the domain expiration date.
Cron jobs and heartbeats
The other way round: we wait for your job to call us. If the nightly backup stops running, you find out the next day.
SSL certificate
Through the monitor's channels we warn you before it expires, with the lead time you choose for each monitor. The WhatsApp and email lists only speak up when 3 days are left or it has already expired, so they don't repeat the same thing every morning.
Slow responses and repeat alerts
Set a limit in milliseconds: if the average of the last three checks goes over it, we alert you once, and again if it happens after recovering. While an outage lasts, you can repeat the alert at the interval in minutes you choose.
Maintenance and automatic pauses
Set a maintenance window with a start and an end: no alerts go out and the status page says “maintenance”. If a site hasn't loaded for 30 days or lost its domain, we pause it; if it comes back, it resumes by itself.
More detail on cron job monitoring and WordPress uptime monitoring.
Send a useful alert, not just a notification
After a confirmed outage, route the alert through channels enabled by your plan. Email is included with Free. Paid options include native WhatsApp through Meta's official API, Slack, Microsoft Teams, Discord, Telegram, and HMAC-SHA256 signed webhooks. WhatsApp and email wait until a site has been down for 15 minutes (30 if the server does not respond), so a one-minute blip wakes nobody. Use incident history to understand what happened after a site recovers.
A practical workflow for client websites
Agencies and freelance developers need more than a single green or red indicator. Review multiple client websites, keep a record of incidents, and share availability through branded status pages. Paid plans also provide a monthly PDF report of monitored websites, and SSL expiration notifications are included on every plan.
Uptime monitoring is not a browser-based checkout test, real-user monitoring, or application performance monitoring. MonitoraWeb does not currently provide those products.
Frequently asked questions
What is the fastest monitoring interval?
Paid plans check every 60 seconds. Free checks every five minutes. There is no 15- or 30-second interval today.
Does MonitoraWeb verify outages globally?
No. From a single point: our server. Outages are checked and confirmed from there, not from a network of regional probes.
Can it monitor a complete checkout transaction?
No. MonitoraWeb does not run synthetic browser transactions or real-user monitoring. It can check that a text such as “Add to cart” still appears on the page.
How long is uptime history retained?
Free keeps 30 days, Pro keeps one year, and Agency includes unlimited history.
Can I let customers see availability?
Yes. Create status pages to share relevant monitoring information. Page limits vary by plan.