Website Outage Notification vs Change Alert
Down and changed are different failures. Mixing them in one channel is how both alerts get ignored.
By AyeWatch Team3 min read
Short answer: A website outage notification tells you the site is unavailable. A change alert tells you the content moved. They are different jobs: use uptime monitoring for availability and a page monitor for content changes, with separate channels and owners.
AyeWatch monitors content, not uptime. It watches public pages and topics and sends a summary when the content you named changes.
Two different failures
An outage is a delivery failure. The page cannot be reached or returns an error. A content change is a business event. The page is up and the price, clause, job, or listing moved.
A monitor that treats both as "something is wrong" gives the on-call engineer and the pricing owner the same alert. Neither can act on it.
What uptime tools watch
Status codes, response time, DNS, TLS, and sometimes a keyword presence check. They answer "is the service reachable?" They do not summarize what changed on the page.
Pingdom, Better Stack, and UptimeRobot are built for this. Keep them on the availability channel.
What change monitors watch
Rendered content. AyeWatch reads the page, applies a plain-English rule, and summarizes the delta. It does not page you when the origin returns a 500.
That separation is useful. The on-call rotation should not receive pricing alerts, and the pricing owner should not be woken up by a CDN blip.
Why mixing them fails
A page can be down with no content change, or up with a change that matters. If both alerts land in one channel, the team learns to skim. The next outage or price cut dies in the skim.
Separate the channels, the owners, and the runbooks. The tools can coexist; the alerts should not be merged.
The right stack
Use an uptime tool for availability and a change monitor for content. Use a status page for customer communication. Use a webhook if the change should trigger an automated action.
AyeWatch covers the content half. Pro is $9/mo with 50 topics and hourly checks; Pro+ is $19/mo with 200 topics and ASAP mode.
| Event | Tool | Channel | Owner |
|---|---|---|---|
| Site returns 500 | Uptime monitor | On-call page | Engineering |
| Price changes | Page monitor | Slack or email | Pricing |
| TLS certificate expires | Uptime monitor | Ticket | Platform |
| Job listing appears | Page monitor | Recruiting | |
| CDN latency spikes | Uptime monitor | Dashboard | Platform |
Start a monitor in under a minute
Describe a topic or paste a URL. Cancel before the trial ends and you pay nothing.
Try it free for 7 daysThe bottom line
List the last five incidents your team handled. Mark each as down or changed. Put them in different channels with different owners. That separation is the whole fix.
FAQ
What is the difference between an outage alert and a change alert?
An outage alert says the site is unavailable. A change alert says the content moved. They have different tools, owners, and response playbooks.
Can AyeWatch tell me if my site is down?
No. It monitors content changes, not availability. Use an uptime monitor for status codes and response time.
Should both alerts go to the same Slack channel?
No. Separate them by owner and urgency. A mixed channel trains the team to skim, and both alerts lose meaning.
Do I need both tools?
If availability and content both matter, yes. Many teams run an uptime monitor and a page monitor side by side.