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

Issue affecting stream processing within the AWS US-EAST-1 region

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

Official source (opens in a new tab)
Vendor start
Mar 11, 2026, 20:10 UTC
Vendor's clock
Resolved
Mar 11, 2026, 20:10 UTC
Vendor's clock
First seen by Statuswall
Before tracking began
Statuswall's clock
Duration
Not available
Needs both vendor times

Summary

Built from the facts below, no AI

Potential impact, not a confirmed outage of your systems.

What the vendor confirmed

  • MongoDB Atlas reports operational: "Issue affecting stream processing within the AWS US-EAST-1 region".[E1, E2]
  • The vendor marked it resolved at 2026-03-11 20:10 UTC.[E3, E7]

Affected products and regions

  • Regions: us-east-1 (read from the title, so inferred).[E5]
  • Components: MongoDB Atlas Stream Processing.[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-03-11 20:10 UTC · summary s1, evidence bf6759296ee0f440

Evidence (7)
  1. E1MongoDB Atlas reports operational. (vendor) source (opens in a new tab)
  2. E2Vendor title: "Issue affecting stream processing within the AWS US-EAST-1 region". (vendor) source (opens in a new tab)
  3. E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
  4. E4Vendor-reported start: 2026-03-11 20:10 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 Atlas Stream Processing. (vendor) source (opens in a new tab)
  7. E7Vendor-reported resolution: 2026-03-11 20:10 UTC. (vendor) source (opens in a new tab)

Affected scope

us-east-1

Components: MongoDB Atlas Stream Processing

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. Mar 11, 2026, 20:10 UTCVendor-reported startVendor time
  2. Mar 11, 2026, 20:10 UTCVendor-reported resolutionVendor time

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