Platform

How RanchAlerts supports your team

RanchAlerts is a hosted infrastructure monitoring service. Your people configure monitors in the portal. Independent locations check those targets, confirm failures, and notify the contacts you choose — so you hear about real outages, not a single city’s bad afternoon.

Nine polling cities

Every check result stores the city that ran it. You pick a primary city per monitor. Today we poll from:

Dallas (DTX) Los Angeles (LAX) New York City (NYC) Chicago (CHI) Miami (MIA) Toronto (TOR) Oregon (ORE) Denver (DEN) Atlanta (ATL)

If a city’s own path is degraded, scheduled checks temporarily run from the next closest healthy location without changing the preference you saved. A degraded city is not used to confirm someone else’s outage.

Firewall and WAF operators can copy current egress IPv4 addresses without a login: Monitoring IPs.

Outage confirmation

A problem in one city is not automatically your outage. When several locations are healthy, RanchAlerts asks other cities to try the same check before we open a down incident and notify you.

Confirmation runs immediately, in parallel, from healthy peers.
If only one other healthy city remains, that remote failure still confirms.
You see which cities agreed — not a black box.

Incidents that stay useful

One open outage per monitor. Further failures attach to that incident instead of sending another wave of mail. Reminders follow the interval your organization sets, then continue on a predictable cadence while it stays down.

Recovery closes the incident and sends one recovery message. Maintenance windows pause customer down, recovery, and reminder mail for the scoped monitor so a planned fiber cut is not treated as a surprise.

The infrastructure your customers reach

RanchAlerts is built to watch internet-facing websites, hosts, ports, DNS, domains, and scheduled jobs — the infrastructure partners and customers actually use. Private office networks and cloud metadata endpoints are not valid targets.

Before we connect, we resolve the name and check the addresses. Redirects are validated hop by hop. A failed PING does not mark a sibling HTTP or port check down, so you can watch reachability and the application separately.

HTTP the way operators expect it

We request the URL you give us and judge success by the response. You can require a phrase on the page, set a slow-site threshold, and treat certificate expiry as a warning instead of a fake outage. Timeouts and response size are capped so a hung origin does not stall the rest of your checks.

Heartbeats for jobs without a public port

Backups, exports, and workers can visit a unique HTTPS URL on push.ranchalerts.com. Silence means the job did not finish. Treat that URL as a secret, and only ping after the work succeeded.

Teams, roles, and a quiet security baseline

People join by invitation and set their own password. Sessions stay on the server, rotate at login, and can be signed out on every device. Optional authenticator MFA is available for anyone who wants it.

Organization roles are owner, administrator, member, and read-only. The current organization comes from the signed-in session. Customer data stays isolated between organizations.

Email and SMS that respect the people on call

Email is always available and uses verified contacts. SMS is a package option with consent, a monthly cap, and quiet hours that skip texts while email still sends. If an outage is still open when quiet hours end, held texts go out then.

Contacts receive alerts. Team members sign in. They are not the same list, which keeps a status-page subscriber or an on-call phone from accidentally becoming a portal login.