DEV Community

Ciro Cesar Maciel
Ciro Cesar Maciel

Posted on Originally published at blog.myinfrastructure.click

How to get an alert when your website goes down, for free

You find out the site is down when a customer messages you, or worse, when nobody does and the day's sales just do not happen. You want to know first: a message on your phone saying the site stopped answering, without paying for a monitoring tool for a single site.

This is how it works with Monitors, from the Infrastructure line (by Ciro Cesar Maciel, who writes this).

What the free plan includes

Without a subscription, the account has 1 monitor and 1 status page, no card, no expiry. Plans change only how many monitors and status pages you get; everything else is the same on the free plan:

  • the same minimum interval as every plan: 30 seconds for an HTTP check;
  • alerts by e-mail, Telegram, Discord and webhook;
  • incidents opened by confirmation, with history;
  • a "degraded" state when the site answers but slower than agreed;
  • a public status page with groups and the public name you choose for each service;
  • dashboard, API and an MCP server for an AI agent.

Web Performance (Lighthouse audits) and a status page on your own domain are on the Pro and Scale plans.

Step by step

  1. Create the account with the 8-character code sent to your e-mail. No password.
  2. Add the monitor. Paste the address and pick an interval from a closed list: 30 s, 1, 5, 10 or 30 minutes, or 1 hour. The default is 5 minutes.
  3. Define "up". By default, up means answering as expected. You can require a piece of text in the response, to catch a server that answers with an error page.
  4. Choose the alert channel. E-mail is the simplest. Telegram works with your own bot and the chat id. For Discord, the address must be the channel's own webhook.

The monitor runs from the next minute.

Why the alert does not fire on every hiccup

A site can fail one check for a passing reason. If every failure became an alert, you would learn to ignore it. So a downtime incident opens only after 2 failures in a row (configurable per monitor) and closes on the first good check. Slowness has its own, calmer rule: 3 checks in a row over the agreed time before the alert says DEGRADED. It never says DOWN when the site is only slow.

Check now, no account

The free tool "Is my site down?" at https://myinfrastructure.click/en/tools checks an address once, from Cloudflare's network, and shows status, response time and HTTPS. To be warned next time, that is when the monitor comes in.

What this monitor does not do

  • One region. Each check runs from one point of Cloudflare's network.
  • No native SMS, phone calls, Slack or PagerDuty. The webhook is the bridge: point it at an endpoint that forwards to Slack.
  • No TCP port, ping, certificate expiry or DNS checks.
  • No maintenance windows, no on-call rotation: every channel gets the alert at once.

UptimeRobot and Better Stack also have free plans, with other choices of quantity and interval. Compare by what you need: many addresses checked slowly, or one address every 30 seconds with a status page and an API.

Honest notes

  • To check that sign-in or checkout still works, not just that the page opens, there are journeys: a script that drives a real browser through the flow. Minimum interval 5 minutes.
  • Paid plans are priced in Brazilian reais: R$ 29.99, R$ 49.99 and R$ 99.99 a month for 3, 9 and 199 monitors.
  • The Monitors dashboard is in Portuguese for now.

Full reference: https://myinfrastructure.click/products/monitors/llms.txt

Top comments (0)