White / empty pages
Nearly blank HTML, no real title — site looks “up” but shows nothing.
Website & uptime monitoring
Aepto does more than “is the HTTP status 200?”. You get multi-region uptime, AI Content Monitoring that catches MySQL/database failures, WordPress critical errors, white screens, and defacement — plus Slow Response Alerts when latency degrades against your site’s own baseline.
Three layers of protection
- Uptime checks — Probe your URL from the regions you pick, on the interval you set. Downtime and recovery emails go to your website monitoring contacts.
- Content Monitoring — Reads the page body. A site can return HTTP 200 and still show a blank page, a MySQL error, or “There has been a critical error on this website.” Content Monitoring is built for that gap.
- Slow Response Alerts — Watches response time against your historical baseline and alerts on significant slowdowns, not only hard downtime.
Open Monitoring → Monitoring Dashboard, or turn the Website switch on a domain card under Domains → All Domains.
Content Monitoring (AI)
Catches failures classic uptime tools miss — when the origin still answered “OK” but the page is broken. Combines fast pattern checks with AI analysis.
Enable Content Monitoring
On add/edit for a domain monitor
Content Check Interval
How often the page body is read
Content Monitoring Contacts
Separate from uptime contacts if you want
What it catches
Database & MySQL errors
Connection failures, “Error establishing a database connection”, raw DB dumps.
Critical & fatal errors
WordPress critical screens, PHP fatal/parse errors, stack traces.
Server error pages
500/503-style failure content even when something still responds.
Suspension / lockouts
Account suspended or parked-style messages from the host.
Hack / defacement
Obvious “hacked by” or vandalized content in the visible body.
Maintenance / broken
Pages that indicate the site is not serving normal content.
The first content check analyzes the page right away (it does not wait for the page to change), and checks work behind caching CDNs. When an issue is found, Aepto opens a content incident and notifies your content monitoring contacts. When the page looks healthy again, you get a recovery-style notice. Rapid switches (for example white page → critical error) are treated as new problems, not ignored.
Plans & credits: Content Monitoring is available on paid plans. Scheduled automatic checks use AI without burning your user AI credits; manual content checks can consume AI credits — see AI credits.
How downtime is decided
- Every plan gets downtime alerts. A site that stops answering (server down, expired domain, connection refused) is reported as down, including on the free plan with a single check location. An alert goes out after two failed checks in a row, so one lost packet does not wake anyone.
- Several locations must agree. With multiple regions, a site is declared down only when enough of your locations could not reach it, and recovery is confirmed from your locations before the incident closes.
- A redirect to an error page is not “up”. A page that redirects to an error (for example a 301 that lands on a 500) is shown as down.
- Uptime percentages for 24 hours and 7 days reflect real time down, not the number of checks.
- Planned maintenance scheduled on your status page does not trigger downtime alerts for the services it covers.
- Plan limits apply to settings. Check interval, regions and content monitoring stay within what your plan includes. If a payment is outstanding, your existing limits are not reduced.
- Monitor targets must be public. Addresses that point at private, loopback or internal networks are rejected.
- Removing a domain removes its monitors. Monitors of a deleted domain (or an account that is deleted) stop, so no alerts are left without a recipient.
PageSpeed
PageSpeed scores for each domain are refreshed automatically once a day. Check now still runs one immediately. Set a threshold on the domain card to be notified when the score falls below it.
Slow Response & performance alerts
Under the monitor settings, enable Enable Slow Response Alerts (labeled Performance Alerts (Slow Response) on the detail page).
- Aepto compares current response times to your site’s baseline — not a single global “slow” number for every website.
- You do not have to pick a manual millisecond threshold for the default anomaly behavior; the product watches for significant degradation.
- When slow-response alerts are on, the monitor detail view can show Performance Anomalies and Hosting Reliability context based on observed patterns.
- Alerts can also reach webhooks as
monitoring.slow_response— see Alert webhooks.
Use this when the site is “up” but feels broken for customers: TTFB spikes, hosting contention, or regional latency that never trips a pure downtime check.
Add a monitor
- Open Monitoring → Monitoring Dashboard and click Add Monitoring (or turn Website on for a domain under Domains → All Domains).
- Choose Monitoring Type:
- Domain Monitoring — tied to a portfolio domain (supports Content Monitoring)
- API Endpoint, IP Address, Additional Domain/Sub-domain, Port-Based Service — extra components
- API Rate Limits — redirects you to add a quota monitor (see API Rate Limits)
- Fill Monitoring URL (or select domain), Check Interval, Timeout (seconds), and Alert Contacts.
- Under Monitoring Regions, select the locations that should probe the URL.
- Optional: check Check SSL Certificate for certificate expiry awareness on that monitor.
- Optional (recommended): enable Enable Content Monitoring, set Content Check Interval, and choose Content Monitoring Contacts.
- Optional (recommended): enable Enable Slow Response Alerts for latency / performance degradation.
- Click Enable Monitoring.
Day to day
- On the dashboard, use Check Now for an immediate probe, or Refresh to reload status.
- Click a monitor row to open its detail page for uptime history, incidents, content monitoring status, and (when enabled) performance anomalies.
- Keep contacts verified on Contacts. Assign both website monitoring and content monitoring types as needed. For Slack/Zapier-style delivery, use Alert webhooks.
Public status for customers: Status pages. Broader product questions: FAQ.
FAQ
Why do I need Content Monitoring if uptime already says “up”?
Uptime checks whether the URL responds. Many real outages still return HTTP 200 with a white screen, MySQL error, or WordPress critical error page. Content Monitoring reads the page and alerts on those failure states.
What kinds of errors can Content Monitoring catch?
White/empty pages, database and MySQL connection errors, PHP fatal/critical/parse errors, server error pages (500/503-style content), hosting suspension messages, obvious hack/defacement text, and other “site is not serving normal content” states — with AI used to interpret ambiguous pages.
Does Content Monitoring use my AI credits?
Automatic scheduled content checks use AI without consuming your user AI credit balance. Manual “check now” style content analysis can consume credits. Details: AI credits.
How do Slow Response Alerts work?
With Enable Slow Response Alerts on, Aepto watches response time against your monitor’s historical baseline and notifies you on significant slowdowns — even when the site never goes fully down.
Can I use different contacts for uptime vs content?
Yes. Set Alert Contacts for uptime and Content Monitoring Contacts for content issues. On the Contacts page, enable the matching notification types for each person.
Is Content Monitoring available on every monitor type?
Content Monitoring is for Domain Monitoring. API, IP, subdomain, and port monitors use uptime (and optional slow-response) without the page-content AI layer.
More answers: FAQ hub.