Outage alert templates for cloud, DNS, and SaaS incidents.

What makes a good outage alert

Good outage watches name the service, the failure mode, and the scope of impact. “AWS outage” is vague; “AWS multi-region outage affecting customer services” is much easier to verify and route.

Use these when you want fast operational awareness without waiting for a polished vendor status narrative. If your team also tracks follow-on breach risk, pair this page with security breach alerts.

How to scope an outage watch without drowning in noise

Start with the exact dependency that would hurt you in production, not a whole category. “Cloudflare outage affecting major sites” is better than “internet outage,” and “Microsoft 365 outage or Exchange Online incident” is better than “Microsoft problem.”

Separate infrastructure watches from vendor watches when the escalation path is different. Your team may want one alert for DNS or CDN failures, another for collaboration stack incidents, and a third for payment processor disruption that directly affects revenue.

Go deeper

Use the broader library when you need adjacent templates, or read the editorial guides when you want to tighten your alerting rules.