- Level
- confirmed
- Worst impact
- Partial outage
- Components
- INTERNETCONNECTIVITY
- Regions
- sa-east-1
- Down Index
- 48of 100
What to do
Check whether you use AWS INTERNETCONNECTIVITY in sa-east-1. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 0m it lasted.
Anything that failed between 2026-02-07 18:30 UTC and 2026-02-07 18:30 UTC may need a replay.Subscribe to AWS's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=aws works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from AWS 1
- investigating
Between 6:36 AM and 7:09 AM PST, we experienced intermittent network connectivity issues between two Availability Zones (sae1-az1 and sae1-az3) in the SA-EAST-1 Region. This resulted in API error rates and latencies for AWS Services in the SA-EAST-1 Region. The issue has been resolved and all services are operating normally.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-50559bb726
Is AWS still down?
No, this incident was resolved 2026-02-07 18:30 UTC. For AWS's live state, see https://down.guide/aws.
How long did it last?
0m, from 2026-02-07 18:30 UTC to 2026-02-07 18:30 UTC, by the times AWS posted.
What was affected?
AWS named INTERNETCONNECTIVITY in sa-east-1.
What caused it?
AWS hasn't published a root cause. If it does, it shows here.
Where does this come from?
AWS's official status page, https://health.aws.amazon.com/health/status, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.