Docs Find and fix real problems
Website down? Find out before your customers do
Add an uptime monitor so Relia checks your site from outside every minute, alerts you when it stops answering, and can tell your customers on your status page.
When your whole site stops answering, your app can't report anything: there is no request to record. So Relia also checks your site from outside, the way a customer would, and tells you when it doesn't answer.
The example is Relia's demo shop: one afternoon the storefront stops answering for fourteen minutes.
Before you start: add a monitor
- Open Uptime & checks in the menu.
- Click Add a monitor.
- Paste your site's address (for example
https://shop.example.com), or a health address of your API. - Choose How often to check (every minute by default) and click Add monitor.
Free has 5 monitors, Growth 20, Pro 50. Monitors only reach public addresses.
Tip: watch Uptime monitoring and synthetic checks for your website (2 min).
What you'll see
One failed check could be a blip, so Relia waits for a second. Two failed checks in a row and your site is down:
- You get an e-mail at once (and Slack, ClickUp or Jira on Growth and Pro, if you set them up). You get one more when the site recovers.
- Home says something needs you, for example shop.example.com is unreachable. The chip says Outside: Relia saw it from outside, like your customers.
- Uptime & checks shows Needs you. On the monitor's bar each block is one check; the red ones are the outage.
A site that is down is always Needs you.
Find the cause
- Open the incident. What happened says the site is down and how it failed: no response, a timeout, or an error status such as
HTTP 502. - Read Do this next: check that the server is running and reachable: the process, the port, DNS, the TLS certificate and the firewall.
- Look at the evidence from inside. If Relia's SDK runs on that server, the incident also shows what failed inside at the same time (errors, a database that stopped answering, a full disk). No data at all from inside usually means the process or the machine is down.
Common causes: the app crashed and didn't restart, a deploy failed halfway, the server ran out of memory or disk, an expired TLS certificate, a DNS change, or your hosting provider is down.
Tell your customers
If you have a public status page, Relia can post the outage for you in plain words, for example Storefront is unavailable. We are looking into it. It never shows internal details like routes, servers or error counts.
- With Post outages automatically switched on in the status page setup, Relia posts by itself.
- Otherwise Relia asks you first.
When the site answers again, the post turns to resolved and the page says all systems are operational. See Create a status page.
Tip: watch Create a public status page with your own domain (2 min).
Fix it
Fix what stopped the site (restart the process, roll back the deploy, renew the certificate, free disk space), then make it less likely next time:
- run the app under a process manager or platform that restarts it when it crashes,
- monitor a health address that checks your database too, not only that the web server answers,
- set up on-call so someone is paged at night.
Check the fix worked
You don't need to do anything. Relia keeps checking: as soon as the site answers again you get the "recovered" message, and the incident closes on its own 30 minutes after the last failed check. It then says how long the site was down, for example was down for 14 min. Home's This week lists it.
Next
Last checked against the product: 1 Nov 2026