Real-time monitoring & alerts

Know the moment your website breaks.

Alertly watches your WordPress sites and webshops around the clock โ€” errors, security, WooCommerce, hosting, Cloudflare and Google โ€” and pings your team on Telegram before your customers notice.

No lock-in. Cancel anytime with prorated refund.

  • < 1sAlert latency
  • 90+Checks per site
  • 24/7Always watching
The cost of finding out late

Checkout dies at 03:14 and you find out at 09:00.

InnoDB deadlock on wp_postmeta locks the order table. By the time support emails land, hours of revenue are gone.

Payment gateway silently rejects orders in a currency it never supported.

Legacy acquirer + wrong-currency = every order fails with acquirer_integration_error, buried under card-decline noise. Weeks of lost revenue.

Cloudflare Dev Mode left on after a Black Friday debug session.

Origin gets slammed for three hours, hosting bill spikes, TTFB tanks. Nobody notices until the invoice arrives.

UpdraftPlus stopped running 63 hours ago and no email went out.

The daily-run notification fires; the failure-run one doesn't. You only find out when you need to restore.

A rogue admin disabled Wordfence 2FA while you were on vacation.

No badge on the dashboard, no email. First sign of trouble is the bruteforce hit two weeks later.

Disk quota hit 96% and cPanel started rejecting media uploads.

Content editors think the site is broken. Backups get truncated. You find out on Monday when someone messages Slack.

SSL cert expiring in 3 days, auto-renew has been stalled for a week.

Let's Encrypt renews at ~30d before expiry. If both attempts fail, you get one warning email โ€” usually into spam.

01How it works

Live in three steps.

01

Create your account

Sign up in seconds and add your first site from the dashboard.

02

Install the plugin

Drop the lightweight Alertly plugin on your WordPress site and paste one key.

03

Get alerts in Telegram

Errors, security events and sales land in your Telegram โ€” instantly.

02Why Alertly

Purpose-built for the WordPress operator.

Built for WordPress, not against it.

Every check runs inside the plugin. Understands WooCommerce order states, Wordfence events, RankMath redirects, Cloudflare zones โ€” not a generic uptime pinger with a WP badge.

Telegram, not another email digest.

Real-time push where your team already is. Threaded per site, so on-call knows exactly which shop is bleeding without opening a dashboard.

Your data, in the EU.

Self-hosted on EU infrastructure. GDPR sub-processor list published. Signed DPA on request. No US analytics pixels on the marketing pages.

Per-site pricing. No seat games.

One flat price per monitored site. Add your whole team, all your clients, no tier upsell. Cancel anytime with prorated refund.

Parses InnoDB deadlocks and names the killer thread.

Not "check your logs" โ€” the alert body ships the exact SQL of the waiter, the blocker, and the "kill thread N" command you should run.

Payment failures split operator-fault from customer-fault.

acquirer_integration_error โ†’ page you. insufficient_funds โ†’ silent. Classifier reads Reepay/Frisbii meta and routes accordingly.

Every alert names the responsible plugin.

PHP fatal? Alert body says "source: elementor-pro/v3.19.2". Not a wp-content absolute path for you to parse at 3 AM.

Change history is signed and searchable.

Every plugin install, deactivation, update, and delete lands in a timeline with actor + version + timestamp. Post-mortem-ready.

Alert noise is a fixed problem, not a config game.

Non-outage stuff stays in the dashboard + monthly PDF. Site-breaking + money-loss pages Telegram. You can override per-site.

One plugin, thirty integrations.

Errors + security + Woo + hosting + Cloudflare + GA + Ads + Search + PageSpeed + Merchant + Meta + cPanel. One key, one dashboard.

Real client incidents, not hypothetical dashboards.

Same tool the Webkonsulenterne agency runs on 60+ live WordPress sites. Every check exists because a real client incident demanded it.

The dashboard is boring on purpose.

No dark-mode-glow chart theatre. Read the alert, click through to the site, fix it, close the tab. Nothing to demo to your boss.

03Real incidents caught

Concrete wins from the past few weeks.

CRITICAL

InnoDB deadlock โ€” checkout collision

Analytics rollup collided with a webhook UPDATE on the order-items table. Alertly parsed SHOW ENGINE INNODB STATUS, named both conflicting queries and the blocker thread ID, and pinged before support tickets landed.

  • 47sstall โ†’ Telegram push
  • 0customer complaints
  • ~15k / moorders on affected shop
WARNING

Lock-wait storm โ€” cron + webhooks fighting

SmartReplyPro cron acquired postmeta locks, then a Reepay webhook queued behind it for 82 seconds. Alertly joined innodb_lock_waits with processlist and surfaced the idle-in-transaction blocker with the exact "kill thread N" command.

  • 82sblocker age when caught
  • 209row-lock waits / hour
  • 1kill command in the alert body
CRITICAL

Payment gateway silently rejecting orders

Legacy acquirer agreement did not support SEK on a Swedish shop. Every order failed with acquirer_integration_error. Card-decline noise buried it. Alertly's payment classifier separated operator-fault from customer-fault, alerted immediately.

  • ~20operator-fault failures caught
  • DKK 40k+estimated recovered revenue
  • same dayescalation to acquirer
04Everything Alertly watches

Ninety-plus checks. One plugin. One dashboard.

Grouped by category so you can see exactly what fires โ€” and what doesn't. Every item is a live check running today on ~60 client sites.

PHP errors & crashes

5
  • PHP fatal errors with plugin/theme blame attribution
  • Uncaught exceptions with request context (URI, method, UA, IP, referer)
  • file:line dedup so shutdown+handle_error don't double-fire
  • Peak memory + memory_limit + max_execution snapshot
  • REST 500s with route + Body-size context

WooCommerce

8
  • Payment failures classified operator-fault vs customer-fault
  • Reepay/Frisbii gateway error codes surfaced verbatim
  • Refund failures with acquirer message
  • Chargeback / dispute opened
  • Stock validation errors at checkout
  • Add-to-cart flood detection (per-IP + UA + rDNS)
  • No-recent-orders heartbeat (sales pulse)
  • Order restore corruption (missing itemmeta)

Security

10
  • New admin user created (with IP + geo + business-hours check)
  • Admin login geolocation change
  • Wordfence daily digest (client-friendly rewording)
  • Wordfence 2FA disabled
  • Wordfence missing / deactivated
  • File tampering on wp-config, .htaccess
  • Critical files deleted (robots.txt, wp-config, .htaccess)
  • Inactive admin accounts
  • Default login credentials still present
  • Failed-login bruteforce spike

Database health

6
  • InnoDB deadlocks with waiter + blocker queries
  • Lock-wait storms with process attribution
  • Idle-in-transaction detection ("kill thread N")
  • Innodb_row_lock_waits hourly delta
  • wc-logs/ directory bloat (>100 MB)
  • Autoloaded options bloat (top offenders)

WordPress health

13
  • Maintenance mode left on
  • Plugin auto-updates enabled (list of offenders)
  • Permalink structure changed
  • HPOS disabled after WC 8 upgrade
  • Thumbnail fallout after image plugin change
  • wp-cron missed for N hours
  • WP All Import failure runs
  • Max input vars misconfig
  • Web fonts hosted vs Google-embedded
  • CTX Feed / product feed changes
  • AcyMailing version out of date
  • FastAdmin plugin drift
  • Billwerk configuration

Backup & restore

3
  • UpdraftPlus backup overdue (>48h)
  • UpdraftPlus schedule changed
  • Backup restore corrupted (WooCommerce item meta)

SEO

12
  • Sitemap unreachable
  • robots.txt tampering
  • Missing SEO meta (title / description / canonical / og) per URL
  • SEO issues per URL (multi-check)
  • Duplicate content (fingerprint + slug + title, GSC-enriched)
  • RankMath broken redirect targets
  • Redirection plugin rule drift
  • Frontpage noindex accidentally set
  • Yoast schema removed
  • 404 rate weekly delta
  • Frontpage image formats (WebP/AVIF Content-Type verified)
  • Legacy JPEG/PNG image detector

Uptime & probes

6
  • Uptime down (โ‰ฅ60s sustained)
  • Uptime recovered
  • Sitemap probe
  • Font asset probe
  • Robots-blocked probe
  • Heartbeat missed (wp-cron pulse)

Cloudflare

19
  • 5xx error rate with per-status breakdown
  • 4xx error rate with per-status breakdown + top 404 URLs
  • Threat volume (firewall events)
  • Bandwidth spike (uncached share)
  • Cache hit-rate low
  • Cache bypass ratio high
  • 404 weekly delta
  • SSL certificate expiry
  • Under Attack Mode on
  • Zone paused / not active
  • Challenge / block rule drift
  • Rate limit breach
  • Dev Mode on
  • Rocket Loader on
  • Old TLS still accepted
  • Bot challenge on Googlebot
  • HTTPS not forced
  • Zone settings drift
  • Billing anomalies

Google Analytics 4

4
  • Traffic drop (WoW / DoD)
  • Stream config changed
  • Stream config disabled
  • Realtime anomaly

Google Ads

2
  • Zero conversions
  • Account status flagged / suspended

Google Search Console

3
  • Crawl errors
  • Coverage issues
  • Manual action

Google PageSpeed

5
  • Score regression
  • LCP threshold breach
  • CLS threshold breach
  • TBT threshold breach
  • Weekly report

Google Merchant Center

5
  • Product disapproval spike
  • Feed error
  • Price mismatch (feed vs storefront)
  • Performance drop
  • Account issue

Meta Commerce

1
  • Product disapproval

cPanel / WHM

7
  • Disk usage %
  • Inode usage %
  • WP Toolkit issues
  • CPU sustained breach (LVE / CloudLinux)
  • Memory sustained breach (LVE)
  • IO sustained breach (LVE) with cause attribution
  • Staging site cron probe

Plugin lifecycle

5
  • Plugin activated
  • Plugin deactivated
  • Plugin installed
  • Plugin updated (with source version)
  • Plugin deleted

Email delivery

3
  • Email send failed (with SMTP conversation)
  • DKIM / SPF / DMARC misalignment
  • Recovery-detected (backup SMTP succeeded)

Cache activity

2
  • Cache flush events with source attribution (Elementor, LiteSpeed, W3 Total Cache, WP Rocket)
  • Weekly cache-purge digest
05At a glance

Everything worth watching, in one place.

๐Ÿ›

Instant error alerts

PHP fatals, failed emails and plugin changes pushed to Telegram the moment they happen.

๐Ÿ›ก๏ธ

Security & uptime

Admin-login geolocation, new-admin detection, file-tamper checks and heartbeat monitoring.

๐Ÿ›’

WooCommerce aware

Order, payment-failure and add-to-cart-flood alerts โ€” with optional Cloudflare IP blocking.

๐Ÿ“Š

Cloudflare & Google

Pull-based monitors for Cloudflare, Search Console, Analytics, PageSpeed and Merchant Center.

๐Ÿ–ฅ๏ธ

Hosting health

cPanel disk & inode usage, sitemap reachability, cache status and stale-backup detection.

๐Ÿ””

Rules you control

Per-site alert rules with throttling โ€” your own Telegram bot and chats, on your terms.

06Compared to the alternative

Alertly vs the pieced-together stack.

CapabilityUptime pinger + WP plugin + email digestAlertly
Understands WooCommerce order states + payment gateway metaโ€”Native
Separates operator-fault from customer-fault payment errorsManual triageAuto-classified
Real-time push to where your team already isEmail digestTelegram
Parses InnoDB deadlock + lock-wait + process attributionโ€”Built-in
Errors + security + Woo + hosting + CF + Google + cPanel3โ€“5 toolsOne dashboard
Per-site flat pricing, unlimited team seatsSeat / tier upsellsFlat
GDPR sub-processor list + DPA + EU-hostedVariesPublished
Auditable plugin-change timelineGuess from gitSigned history
07Pricing

Simple, per-site pricing.

One subscription per monitored site. No tiers, no surprises.

  • EU-hosted infrastructure
  • GDPR sub-processor list published
  • Cancel anytime, prorated refund
  • Signed DPA available on request

Stop finding out from your customers.

Set up in minutes. Cancel anytime with prorated refund. Your team, all your clients, one flat price per site.