It's not your code. It's their outage. Hear about it in minutes.

The 40-minute detour

Errors spike. Someone checks the last deploy. Someone else restarts a pod. Logs get grepped, a rollback gets discussed, and forty minutes later a person in another channel says "isn't GitHub having issues?"

Your stack runs on vendors. Payments, email, auth, hosting, DNS, AI models, CI. Each one has a status page. Nobody checks thirty status pages during an incident.

Outage Clock checks them for you, all the time, and posts to the channel your team already watches.

Setup

1. Pick your vendors. Search the list and add the services you use. Over a hundred are covered, from AWS to small SaaS tools.
2. Narrow it down. Choose components and regions, such as "AWS us-east-1 EC2" instead of all of AWS. Paid plans support component filters.
3. Choose a channel. Email, Slack, Microsoft Teams, a generic webhook or a daily digest. Then get on with your day.

What you get

Official status pages, polled often

We read each vendor's own status page every 2 to 5 minutes, depending on plan. Most publish machine-readable feeds, so we pick up incidents soon after they are posted.

One format for every vendor

Every vendor names things differently. We map each update to the same model: vendor, component, status (operational, degraded, partial outage, major outage, maintenance) and the incident text.

Component filters

Only hear about the parts you use. Following Stripe but only care about the API and webhooks? Filter the rest out.

A second signal

Vendors sometimes post late. We also run a light HTTP check against each vendor's homepage or API endpoint, so a total outage shows up even before the status page changes.

Maintenance calendar

Planned maintenance from all your vendors in one view, so a Saturday database upgrade at your email provider is not a surprise. Included on Pro.

Your dependency page

Pro includes a private status page that shows the health of everything you depend on. Handy for support teams who keep asking engineering what is going on.

Free "is it down?" pages

Every vendor we track has a public page showing its current status and recent incident history. Bookmark the ones you rely on.

FAQ

Where does your data come from?

Each vendor's official status page, plus our own reachability check. We do not crowdsource user reports.

How fast are alerts?

We poll every 5 minutes on Free and every 2 minutes on paid plans. Alerts go out as soon as a change is detected. How fast the vendor posts the incident is up to them.

Will I drown in alerts?

Not if you use component filters. You can also switch any vendor to the daily digest.

Which vendors do you cover?

Over a hundred cloud and SaaS services, including AWS, Stripe, GitHub, OpenAI, Twilio and Cloudflare. If one you use is missing, email us and we will look at adding it.

Can I send alerts to PagerDuty or Opsgenie?

Use the generic webhook to send events to any tool that accepts them. Business adds custom webhook payloads.

Is there an API?

Yes, on Business.

Are you affiliated with these vendors?

No. Vendor names identify the services we monitor. We are not affiliated with or endorsed by any of them.