Slack
Incoming webhook
Paste a Slack incoming webhook URL. The ops channel gets the same down and recovery as email.
Infrastructure · under watch
Know when it goes down.Before your customers do.
RanchAlerts is infrastructure monitoring from thirteen cities across the U.S., Canada, and Europe. We watch the websites, hosts, ports, DNS, and jobs your business depends on. When something fails, we confirm it from another city, then notify the people and rooms you choose.
We are currently in beta testing and will be open for public access in Q4/2026. Already invited? Sign in at portal.ranchalerts.com.
Polling network
Checked from where your customers actually are.
Every result stores the city that ran it. Today that is Dallas, Los Angeles, New York City, Chicago, Miami, Toronto, Oregon, Denver, Atlanta, Ashburn, London, Paris, and Frankfurt. If a city’s own path is degraded, scheduled checks move to the next closest healthy location without changing your saved preference.
13polling cities · U.S., Canada, and Europe
DallasDTX · 32.78°N
Los AngelesLAX · 34.05°N
New York CityNYC · 40.71°N
ChicagoCHI · 41.88°N
MiamiMIA · 25.76°N
TorontoTOR · 43.65°N
OregonORE · 45.52°N
DenverDEN · 39.74°N
AtlantaATL · 33.75°N
AshburnASH · 39.04°N
LondonLON · 51.51°N
ParisPAR · 48.86°N
FrankfurtFRA · 50.11°N
When something breaks
One city’s blip should not page you.
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.
- 01 Watch
Primary city keeps probing on the interval you set.
- 02 Fail
Dallas cannot reach the target. Not an incident yet.
- 03 Verify
Chicago and Atlanta try the same check in parallel.
- 04 Alert
One incident. Email, SMS when the package includes it, and Slack, Discord, Teams, or a webhook.
- 05 Recover
The same people hear that it is back. One recovery, not a storm.
What it watches
One product for websites, hosts, jobs, and DNS.
Add a monitor, pick a method, and RanchAlerts schedules it from the city you prefer. Packages can add heartbeats, DNS, domain watches, and text alerts.
| Method | Probes | Notes |
|---|---|---|
| HTTP | HTTPS GET from a polling city | Keywords, validated redirects, slow-site warning. TLS expiry is a warning, not a fake outage. |
| PING | ICMP to a hostname or IP | Reachability only. A PING failure does not mark sibling HTTP or TCP checks down. |
| Port Monitoring | TCP connect — 443, 25, 143, 22 | Confirms the port accepts a connection. It does not log in. |
| Heartbeat | Inbound HTTPS to push.ranchalerts.com | Silence means down. For backups and workers with no public port. |
| DNS | A, AAAA, CNAME, MX, TXT, NS | Listed values must still be present. Extra records are allowed. |
| Domain | Nameservers and registration expiry | A nameserver swap is a change alert, not a down. Expiry warnings go out before the clock runs out. |
Operational visibility
The same facts the portal shows after you sign in.
Uptime is account-level. Each monitor keeps the city that ran the check, the method, and latency. Sample data only.
Dashboard
All monitors up
100%24 hours
99.98%7 days
99.95%30 days
Corporate website
HTTP
DTX
Up
Mail gateway
TCP :443
CHI
Up
Nightly invoice export
Heartbeat
—
Up
example.com nameservers
Domain
NYC
Change
Alert workflow
Contacts get email and SMS. Rooms get Slack, Teams, Discord, and webhooks.
People and destinations are not the same list. Email is always on. Text messages are a package option, with consent, quiet hours, and a monthly cap. Chat and webhooks go to the channel you paste — quiet hours do not skip them.
Discord
Channel webhook
Paste the Discord channel webhook. One destination, the same confirmed incident.
Teams
Microsoft Teams
Paste a Teams incoming webhook for the channel your on-call already watches.
HTTPS
Signed webhook
Any public HTTPS endpoint. RanchAlerts posts signed JSON so PagerDuty, n8n, or your own receiver can verify the source.
API
REST and MCP
Issue a key under Settings → API. Call https://api.ranchalerts.com/v1/ or connect Cursor and Claude at https://mcp.ranchalerts.com/mcp.
Incident
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.
Verified contacts only
A contact is a name and a verified email, with an optional mobile number. Contacts do not get a RanchAlerts login.
SMS
When you need a tap on the shoulder
Consent is required to save a number. Quiet hours skip texts while email still sends. Reply STOP on the phone to unsubscribe.
Recovery
Then a clear all-clear
When the target answers again, the same people and rooms hear that it recovered. Maintenance windows pause alerts when you already know the circuit is coming down.
Status pages
Show customers what you already monitor.
Publish a branded page for selected monitors, on a RanchAlerts URL or a hostname you CNAME to status.ranchalerts.com. Visitors can subscribe by email. Probe logs stay private.
Public uptime bars follow confirmed incidents, not unconfirmed probe noise. Pages refresh about every 60 seconds.
Platform
Built as a hosted, multi-tenant service.
- Isolation
- Organizations are isolated. The current organization comes from the signed-in session, not from a client-supplied id.
- Roles
- Owner, administrator, member, and read-only — enforced on the server. Members cannot manage membership. Read-only cannot mutate.
- Sign-in
- Invited users set their own password. Authenticator MFA is required. Sessions stay on the server and can be signed out on every device.
- Targets
- Public internet destinations only. Before we connect, we resolve the name and check the addresses. Private networks and cloud metadata are rejected.
- Egress
- Firewall operators can copy current polling IPv4 addresses without a login at Monitoring IPs.
Get Access
Join the beta, or sign in if you already have an invite.
Accounts are created by invitation — no credit card required.