Skip to content

Outage Watch

Weekly vendor outage monitoring: incidents, outages and postmortems at the vendors you depend on, with sourced durations, affected regions and confirmed impact.

Built for ops and SRE teams doing vendor outage monitoring to track vendor reliability.

01

Why this work is hard

The problem

Ops and SRE teams tracking vendor reliability spend hours on this by hand: finding the right sources, reading them, checking them against each other and writing up what matters. The work is repetitive, it is easy to miss something, and nobody can show where a claim came from.

The GREP AI agent

Outage Watch does that work as a GREP AI agent. It runs weekly and delivers each edition without you asking. Every run delivers a formatted brief, with every claim linked to its source.

02

What you get

01
On a schedule
It runs weekly and delivers each edition without you asking.
02
Sourced delivery
Every run delivers a formatted brief, with every claim linked to its source.
03
Read in minutes
The result is a brief you can read in minutes, not a thread to dig through.
04
Make it yours
Clone it, edit its instructions and make it your own in one click.
Use cases
01Ops and SRE teams tracking vendor reliability who do this work by hand today
02A standing brief that lands before the meeting it is for
03Cloud research without the tab sprawl
03

What Outage Watch delivers

Web pageOutage Watch
04

FAQ

What does Outage Watch need to run?

Outage Watch needs vendors you depend on.

How often does Outage Watch run?

It runs weekly and delivers each edition without you asking.

What does Outage Watch deliver?

Every run delivers a formatted brief, with every claim linked to its source.

Can I change what Outage Watch does?

Yes. Every GREP AI agent can be cloned into your workspace, where you can edit its instructions, add your own sources and files, and change its schedule.

Which sources does the vendor outage monitoring check?

Each vendor's own status page and incident history first, such as the AWS Health Dashboard, Google Cloud Service Health and GitHub status, then corroborating sources such as Cloudflare Radar, ThousandEyes and Downdetector.

Can I limit it to one region or service?

Yes. An entry like AWS us-east-1 or GitHub Actions limits coverage to that region or service, while AWS alone covers the whole provider.

Does it report a root cause right away?

Only once the vendor publishes one. Until then it states no root cause, and labels preliminary statements as preliminary. Community reports such as Downdetector counts are labeled as user reports, not affected-user totals.

05

More agents like this

All agents →

Run Outage Watch in minutes.

Free to start. Run it once, put it on a schedule, or clone it and make it yours.