Skip to content

For online shops

Know that your shop is selling — even at 3 a.m.

Lynx Heartbeat checks your shop from four locations every minute, watches the server behind it from the inside and notifies the right person when the checkout stops working — not only when the home page is down.

What keeps shop operators awake

  • The home page loads, but nobody can check out

    A broken payment step, an empty cart page or a maintenance mode that answers with status 200: a simple “is it up?” check sees none of that.

    How Lynx helps

    Point a monitor at your cart or checkout page and require a text that only appears when the page works — or a text that must not appear, such as an error message. Custom headers and basic or bearer authentication are supported.

    Website monitoring in detail

  • A failed check is not always a failed shop

    One network path can fail while your customers reach the shop without trouble. Alerts for every hiccup teach the team to ignore them.

    How Lynx helps

    Four check locations in Nuremberg, Helsinki, Ashburn (USA) and Singapore fetch the page. An incident opens only when every location that is reporting sees the error, twice in a row.

    Alerts and escalation in detail

  • Certificate or domain expired over the weekend

    Browsers block a shop with an expired certificate, and an expired domain takes the shop and its email with it.

    How Lynx helps

    Lynx warns 14 and 3 days before a certificate expires and 30 and 7 days before a domain does — for every top-level domain whose registry publishes the date. The registry for .de does not.

    Website monitoring in detail

  • Slow at peak times: database and PHP-FPM

    During a sale or after a newsletter, PHP-FPM runs out of processes or MySQL out of connections. The shop gets slow long before it goes down.

    How Lynx helps

    The agent measures every minute: PHP-FPM pools, MySQL connections, Apache workers, CPU, memory and disks — and flags a pool at its limit or a database that refuses connections.

    Server monitoring in detail

  • The disk fills up before the next sale

    Logs, sessions, product images and a growing database fill a disk slowly — until the shop can no longer write orders.

    How Lynx helps

    Every hour Lynx reads the trend of each file system. Less than seven days until full is a warning, less than two days is serious — during working hours, not at night.

    Disk full soon

  • Nobody notices at night

    An outage at 2 a.m. is found by the first customer in the morning — or not at all, because the orders simply stop coming in.

    How Lynx helps

    Notifications by push, Telegram or email. Quiet hours can let serious incidents through, and if nobody acknowledges an incident, Lynx notifies the next step after 15 and 30 minutes.

    Alerts and escalation in detail

Which plan fits

Start · Team

A shop on a few servers fits into the smallest plan. Team adds Slack, Microsoft Teams and webhook, status pages on your own domain and the AI summary in the alert.

Compare all plans

How to get started, step by step

The plans that fit, side by side
IncludedStartTeam
Servers included315
Monitors included1050
Status pages13
Alerts by email, Telegram and pushincludedincluded
Alerts to Slack, Microsoft Teams and webhooknot includedincluded
Status pages on your own domainnot includedincluded
AI summary in the alert, with your own keynot includedincluded

Questions

Can Lynx check my checkout page?

Yes, any page that is reachable over HTTPS. Lynx fetches it, checks the status code and whether an expected text is there or a forbidden text is absent. It does not click through a purchase: choose a page that only shows the right content when the shop and its database work.

Do I need access to the server?

Not for the checks from the outside — they work for any shop that is reachable from the internet, whatever it runs on. To see the server from the inside (PHP-FPM, MySQL, disks), the agent runs on it: Ubuntu 20.04 to 26.04 with systemd.

Will a short blip wake me up?

No. A check has to fail twice in a row, and a check from the outside only counts as failed when every location that is reporting sees it. A check that keeps changing its state produces one notification, not a dozen.

Can my customers see whether the shop is working?

Yes, with a status page. It shows the monitors you choose, announced maintenance and the availability of the last 90 days — no server details, versions or causes.

Is anyone watching your shop tonight?

Add your shop as a monitor and install the agent on its server — one command per server.