Cloud Outage Feed: AWS, Azure, Google Cloud, Microsoft 365 & Cloudflare Status Alerts

One feed for the clouds you depend on. This Actor checks the official status sources of AWS, Microsoft Azure, Google Cloud and Cloudflare, plus your own Microsoft 365 tenant and any other Statuspage-based service, filters them to the regions and services you actually use, and alerts Slack or Microsoft Teams when something starts, changes or is resolved.

Schedule it every 15 minutes or hourly and you get a quiet channel that only speaks up when it matters.

What you get

🟠 Updated · Google Cloud · Cloud SQL connectivity issues in Montreal (northamerica-northeast1)
✅ Resolved · AWS · Amazon EC2: Increased API Error Rates (ca-central-1)
🔴 New · Cloudflare · Elevated latency in Toronto (Toronto, ON, Canada - (YYZ))

Every incident is also saved as a row you can export (CSV, Excel, JSON) or pull through the API:

Field	Meaning
changeType	new, updated, resolved (or unchanged when "Only report changes" is off)
provider	aws, azure, gcp, cloudflare, m365, or statuspage:<host>
status	active or resolved
severity	info, degraded, outage or unknown
title	Incident headline
services	Affected services
regions	Affected regions or locations (global if worldwide)
startedAt, updatedAt, resolvedAt	Times in UTC
latestUpdate	Text of the most recent provider update
url	Link to the incident on the provider's status page

Why use it

• Filtered to you. Watch ca-central-1, canadacentral and northamerica-northeast1 instead of reading about every region on Earth.
• Only changes. Scheduled runs report what's new, updated or resolved since the last run, so alerts don't repeat.
• No flood on day one. The first run of a new schedule quietly records what's already ongoing; alerts start from the next change.
• Your Microsoft 365 tenant, not just the public page. Connect an app registration to include the incidents and advisories Microsoft shows in your admin center.
• Add the rest of your stack. GitHub, Atlassian, Okta, Datadog and thousands of other services publish on Statuspage; paste their URLs to include them.

Sources

Provider	Source	Notes
AWS	Public AWS Health Dashboard feed	Region-level events for all AWS services. Account-specific events need the AWS Health API and aren't included.
Google Cloud	Google Cloud Service Health (incidents.json)	Products and locations use Google's stable IDs, e.g. northamerica-northeast1.
Azure	Public Azure status RSS	Microsoft only posts broad, multi-region incidents here. Most Azure issues are sent privately through Azure Service Health in your portal, so this feed is usually empty, and that's normal.
Cloudflare	Cloudflare status (Statuspage)	Data centers are listed as locations, e.g. Toronto, ON, Canada - (YYZ).
Microsoft 365	Microsoft Graph service health, your tenant	Optional; see below.
Others	Any Statuspage-based page	Optional; add URLs in "Other Statuspage-based status pages".

How to use it

1. Pick the status sources to check.
2. Optionally list regions (codes or place names, matched loosely) and services (keywords like EC2, Cloud SQL, Exchange).
3. Add a Slack or Teams webhook URL, or a generic webhook for your own system.
4. Save it as a task and schedule it, e.g. every 15 minutes.

Each task keeps its own memory of what it has already reported, so you can run separate schedules for separate clients or teams.

Slack setup

Create an incoming webhook for the channel and paste its URL.

Microsoft Teams setup

In the channel, open Workflows and use the template "Post to a channel when a webhook request is received". Paste the URL it gives you. (Classic Office 365 connectors are being retired; Workflows is Microsoft's replacement.)

Connect your Microsoft 365 tenant (optional)

1. In the Entra admin center, create an App registration.
2. Under API permissions, add Microsoft Graph → Application permissions → ServiceHealth.Read.All, then Grant admin consent.
3. Under Certificates & secrets, create a client secret.
4. Enter the tenant ID, application (client) ID and client secret in the Actor input. The secret is stored encrypted.

The permission is read-only and covers service health only. It gives no access to mail, files or users.

Pricing

• $0.003 per status check (one run, all sources).
• $0.01 per incident reported.

With "Only report changes" on, quiet runs cost only the check. An hourly schedule costs about $2.20 a month plus a cent per incident change; every 15 minutes, about $8.70 a month.

FAQ

Why is Azure always empty? By design. Microsoft reserves the public status page for incidents with broad, multi-region impact and notifies everyone else privately through Azure Service Health. When Azure has a big outage, it will show up here.

Can it read AWS events for my own account? Not yet. Account-specific AWS events come from the AWS Health API, which needs your AWS credentials (and a Business support plan or higher).

How do region filters match? Loosely and case-insensitively, against each incident's region codes and location names, with the incident title and text as a fallback. northamerica-northeast matches both Montreal and Toronto GCP regions; Toronto matches Cloudflare's YYZ data center. Global incidents are included unless you turn off "Include global incidents".

One source failed; did I lose everything? No. Each source is fetched independently. If one can't be reached, the run still reports the others and says which one failed.

Feedback

Want another provider or alert channel? Open an issue on this Actor's Issues tab.