Vendor reports: degradedResolved · vendor status “resolved”Official status API

AWS Availability Zone use1-az4 in US-EAST-1 Region is Impaired

Reported by MongoDB Atlas · Databases · source last read 3 min ago

Official source (opens in a new tab)
Vendor start
May 8, 2026, 02:24 UTC
Vendor's clock
Resolved
May 9, 2026, 14:24 UTC
Vendor's clock
First seen by Statuswall
Before tracking began
Statuswall's clock
Duration
1 d 12 h
From vendor start and resolution

Summary

Built from the facts below, no AI

Potential impact, not a confirmed outage of your systems.

What the vendor confirmed

  • MongoDB Atlas reports degraded: "AWS Availability Zone use1-az4 in US-EAST-1 Region is Impaired".[E1, E2]
  • The vendor marked it resolved at 2026-05-09 14:24 UTC.[E3, E7]

Affected products and regions

  • Regions: us-east-1 (read from the title, so inferred).[E5]
  • Components: MongoDB Cloud.[E6]

What is unknown

  • Whether your own systems are affected: a vendor report cannot tell you; check your monitoring.

Last update in these facts: 2026-05-09 14:24 UTC · summary s1, evidence dad3ddaac64901a6

Evidence (7)
  1. E1MongoDB Atlas reports degraded. (vendor) source (opens in a new tab)
  2. E2Vendor title: "AWS Availability Zone use1-az4 in US-EAST-1 Region is Impaired". (vendor) source (opens in a new tab)
  3. E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
  4. E4Vendor-reported start: 2026-05-08 02:24 UTC. (vendor) source (opens in a new tab)
  5. E5Regions written in the title (inferred): us-east-1. (Statuswall) source (opens in a new tab)
  6. E6Components the vendor attached: MongoDB Cloud. (vendor) source (opens in a new tab)
  7. E7Vendor-reported resolution: 2026-05-09 14:24 UTC. (vendor) source (opens in a new tab)

Affected scope

us-east-1

Components: MongoDB Cloud

Read from region codes written in the incident title, so treat it as inferred.

Potential relevance

MongoDB Atlas is not in your stack. Follow it to see whether reports like this fall inside the regions you use.

Timeline

Vendor times come from the vendor. “Seen by Statuswall” times are when Statuswall noticed a change, which can lag the vendor by a few minutes. Statuswall does not store the vendor's update text; read it on the official page.

  1. May 8, 2026, 02:24 UTCVendor-reported startVendor time
  2. May 9, 2026, 14:24 UTCVendor-reported resolutionVendor time

No changes observed yet. Statuswall began recording changes on incidents in November 2026.