AWS outage alerts, the moment they happen

Status is checked every 60 seconds against public AWS health data. Alerts are dispatched as soon as an incident is confirmed - typically within a minute or two of AWS acknowledging it, and sometimes before it reaches social media.

The affected services, the affected regions, the current status (investigating, identified, monitoring), and a link to the live incident timeline - enough to triage without leaving your inbox.

Only incident notifications. No newsletters, no digests, no marketing. During a quiet month that can mean zero emails.

Yes. Alerts are free. The service is supported by Next Signal, the monitoring platform that powers our status checks.

The official AWS Health Dashboard and AWS post-event summaries, cross-checked against our own continuous probes. We never invent incidents - every alert links back to a verifiable source.

Yes. When you subscribe you can scope alerts to specific services (for example EC2, S3, RDS or Lambda). Leave it unscoped to be notified about every monitored service.

You can. Most teams only care about the regions they deploy to - us-east-1, eu-west-1, and so on. Region filtering keeps a Tokyo-only incident from waking up a US-only team.

Yes. You get the opening notification and a single resolved notification with the total duration, so you know when it is safe to stand your team down.

We send status transitions - investigating → identified → monitoring → resolved - rather than a message every few minutes. You stay informed without inbox spam during a multi-hour event.

Related per-service impacts are grouped into a single AWS event, so one us-east-1 outage that touches five services is one alert thread, not five. Minor blips below our confidence threshold are held back.

Yes. You can choose to hear about everything, or only major and critical incidents. Teams on call typically want everything; execs usually want critical-only.

Minor is limited or single-AZ degradation with a workaround; major is broad service impairment across a region; critical is a region-wide outage affecting many services with no easy workaround.

Email is available today. Slack, Microsoft Teams, and generic webhooks are on the roadmap through the Next Signal platform - reply to your welcome email if you want early access.

Not yet. For paging-grade escalation (SMS, phone, PagerDuty/Opsgenie), the Next Signal platform integrates with your existing on-call tooling.

Every email has a one-click unsubscribe link, and it takes effect immediately. No login, no "are you sure", no retention email.

Yes. Use the manage-preferences link in any alert to adjust your services, regions, and severity threshold at any time.

No. Your address is used only to send the alerts you asked for. We do not sell, rent, or share subscriber lists, ever.

Incident timelines are shown in UTC to match AWS’s own post-event summaries. Your email client will show the send time in your local timezone.

We track the commercial AWS regions worldwide, plus GovCloud (US-West). If AWS reports impact in a region we monitor, it can trigger an alert.

AWS is sometimes slow to update its own dashboard. Our independent probes and community signals can surface an incident before AWS acknowledges it, which is often the whole point of subscribing.

We tune for confirmed impact rather than raising an alarm on a single failed probe. If we do open an incident that AWS later reclassifies, the resolved note makes that clear.

Yes. Anyone can subscribe with their own address, or you can point a shared distribution list / alias at the alerts. There is no per-seat limit.

The AWS dashboard is pull-based - you have to go look. We are push-based and independent: we watch it for you, group the noise into one event, and email you the moment something that matters to you changes.

Every incident lives on our /incidents archive with a full timeline, affected services and regions, and a link to the official source - searchable and filterable long after the event.