Monitor · Detect · Notify
RanchAlerts watches public websites, hosts, mail ports, DNS, domains, and scheduled jobs from nine cities. When something fails, we confirm it from somewhere else, then email — and can text — the people you choose.
No credit card for beta. Existing testers sign in at portal.ranchalerts.com.
Who it is for
You do not need to be a network engineer to add a website and get an email when it fails. If you are an engineer, the confirmation rules, polling cities, and public-only target checks are documented in the product.
For everyone
Give the monitor a name you recognize. Paste a public website, host, or job. Pick who should get the message. RanchAlerts keeps checking in the background.
When it is down, you get one clear incident — not a flood of mail for every failed probe. When it recovers, those same people hear that too.
Walk through a first monitor →For IT
HTTP, PING, TCP ports, DNS records, registered domains, and inbound heartbeats. A down waits for two other healthy cities when three or more pollers are live. Private RFC1918 and cloud metadata targets are rejected on purpose.
Email is always available. SMS is a package option, with quiet hours, monthly caps, and STOP handling.
Read the platform notes →Monitor types
Add a monitor, pick a method, and RanchAlerts schedules it from the city you prefer. Package options can add heartbeats, DNS, domain watches, and text alerts.
Open a public website or health URL. Optional keywords, redirects, and slow-site warnings. TLS expiry is a warning, not a fake outage.
Ask a public hostname or IP if it answers. Use this when you care that the host is reachable, not that a page loads.
Connect to public TCP ports such as 443, 25, 143, or 22. RanchAlerts checks that the port accepts a connection. It does not log in.
Your cron job visits a unique HTTPS URL on push.ranchalerts.com. Silence means down. Built for backups and workers with no public port.
Look up A, AAAA, CNAME, MX, TXT, or NS from our cities and confirm the values you listed are still there. Extra records are allowed.
Watch nameservers and registration expiry. A nameserver swap is a change alert, not a down. Expiry warnings go out before the clock runs out.
Confirmation
Checks run from a city you pick. If that vantage fails, RanchAlerts asks other healthy cities before opening a down incident — so a local ISP hiccup is not treated as your outage.
Your primary city cannot reach the target.
SuspectedTwo other healthy cities try the same check in parallel.
ConfirmedOne incident, one down message, then recovery when it is back.
AlertedCities
Every result stores the city that ran it. Today that is Dallas, Los Angeles, New York City, Chicago, Miami, Toronto, Oregon, Denver, and Atlanta. If a city’s own Internet is degraded, scheduled checks move to the next closest healthy poller without changing your saved preference.
Alerts
Contacts are the people who get alerts. Team members are the people who sign in. They are not the same list. Email is always on. Text messages are a package option, with consent, quiet hours, and a monthly cap.
Status pages
Publish a branded page for selected monitors, on a RanchAlerts URL or a hostname you CNAME to us. Visitors can subscribe by email. Probe logs stay private.
How status pages work →Security
Organizations are isolated. Passwords use Argon2id. Optional authenticator MFA. Public-Internet targets only. Firewall operators can copy our polling IPs without a login.
Monitoring IPs →Wide beta
Accounts are created by RanchAlerts and activated from an email invitation. Purchase and self-serve billing are planned for Q4 2026. Until then, there is no public checkout.
