Downtime at checkout is just revenue.
Every minute the checkout is down is an order that went somewhere else. UptimeStatus watches the whole funnel and the quiet failures around it.
The failures that cost a store money.
Checkout and cart, every 30 seconds
Point monitors at the endpoints that take money: cart, checkout, payment callbacks. Checks run at intervals down to 30 seconds on Pro, so an outage is minutes old when the alert lands, not hours.
Learn moreDead product pages, found daily
A daily crawl follows every internal link, flags anything that 404s, and cross-checks your sitemap for pages nothing links to anymore. Discontinued products stop lingering in search results as dead ends.
Learn moreSlow pages lose carts
Every 10 minutes, the last hour's p95 response time is compared to your 7-day baseline. When a page runs twice as slow as normal, an incident opens, even while the site is technically still up.
Learn moreNo expired certificate on payday
An expired certificate turns your store into a full-screen browser warning at the worst possible moment. Expiry alerts arrive weeks ahead, not the morning of.
Learn moreSEO scores, tracked between deploys
Lighthouse performance and SEO scores are recorded over time, so the redesign that quietly tanked your rankings gets noticed while the deploy is still fresh in memory.
Learn moreOrder emails that actually arrive
A blocklisted sending domain means order confirmations land in spam and customers open disputes. Blocklist checks alert you the moment your domain shows up on one.
Learn moreMonitor the funnel, not just the homepage.
A green homepage tells you nothing about the cart API. Give each step of the purchase path its own HTTP monitor, so "the site is up but nobody can pay" stops being a thing you learn from support tickets.
For the pages where a 200 status is not proof of anything, AI checks load the page and verify a customer would actually see products, prices, and a working buy button.
The daily crawl catches what no uptime check can.
Once a day, a crawler walks your store link by link, up to 200 pages, respecting robots.txt. It records every 404, flags each http:// image or script that breaks the padlock on an https page, and cross-checks your sitemap for pages that fail even though nothing links to them anymore.
When it finds something, an incident opens and your channels are notified, the same as any outage. See broken-link monitoring.
Your uptime history is yours.
UptimeStatus is MIT-licensed open source. Your monitors, incident history, and crawl results live behind a plain JSON API you can export from any time, and if you would rather run the whole thing on your own infrastructure, you can clone it and do exactly that.
Store questions, answered.
Can I monitor the checkout flow?
You can monitor each step of it: an HTTP monitor per endpoint (cart, checkout, payment callback), plus AI checks that load a page and verify the content a customer should actually see. What we do not do is scripted multi-step browser transactions, so we will not fill a form and click "Pay" for you. In practice, per-step checks catch the same outages without the flakiness.
How does the broken-link crawl work?
Once a day, a crawler starts at your monitor's URL and follows same-origin links breadth-first, up to 200 pages, respecting robots.txt. Every page that returns a 400+ status is recorded as a broken link, and your sitemap.xml is cross-checked for URLs that fail even though nothing links to them. If issues are found, an incident opens and your notification channels fire.
What counts as mixed content?
Any image, script, or stylesheet loaded over plain http:// from a page served over https://. Browsers respond by breaking the padlock or blocking the resource, which is exactly the trust signal you do not want at checkout. The daily crawl flags each offending resource and the page it was found on.
Will I know when the site gets slow, not just when it goes down?
Yes. Every 10 minutes, each monitor's p95 response time over the last hour is compared against its own 7-day baseline. If it is at least 2x slower, an incident opens in a "monitoring" state: informational, because the site is often still up, just degrading.
What does this cost for a small store?
The Free plan covers 5 monitors, 1 status page, and 5-minute check intervals, which is enough for a storefront, checkout, and a couple of APIs. Pro is $9/month for 100 monitors, 10 status pages, and 30-second intervals.
Start monitoring in under 2 minutes.
No credit card required for the self-hosted, open-source version.