Vendor reports: partial outageOpen · vendor status “monitoring”Official status API

Impaired Cluster operations in AWS me-central-1 and AWS me-south-1

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

Official source (opens in a new tab)
Vendor start
Sep 3, 2026, 16:44 UTC
Vendor's clock
Resolved
Not yet
Still open
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 partial outage: "Impaired Cluster operations in AWS me-central-1 and AWS me-south-1".[E1, E2]
  • It is not resolved yet (vendor status "monitoring").[E3, E7]

Affected products and regions

  • Regions: me-central-1, me-south-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.
  • When it will be resolved: no estimate is shown unless the vendor publishes one on its page.

Last update in these facts: 2026-09-03 16:44 UTC · summary s1, evidence 50b1f7a26839f656

Evidence (7)
  1. E1MongoDB Atlas reports partial outage. (vendor) source (opens in a new tab)
  2. E2Vendor title: "Impaired Cluster operations in AWS me-central-1 and AWS me-south-1". (vendor) source (opens in a new tab)
  3. E3Vendor status word: "monitoring". (vendor) source (opens in a new tab)
  4. E4Vendor-reported start: 2026-09-03 16:44 UTC. (vendor) source (opens in a new tab)
  5. E5Regions written in the title (inferred): me-central-1, me-south-1. (Statuswall) source (opens in a new tab)
  6. E6Components the vendor attached: MongoDB Cloud. (vendor) source (opens in a new tab)
  7. E7Not resolved by the vendor yet. (vendor) source (opens in a new tab)

Affected scope

me-central-1, me-south-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.

What to check on your side

Verification steps only. Statuswall cannot see your systems.

  • Check connection errors, query latency and replication lag.
  • Check whether automatic failover happened and whether your application reconnected.
  • Check error rates, latency and timeouts in your own monitoring for requests that depend on MongoDB Atlas.
  • Look at synthetic checks and alerts that exercise MongoDB Atlas.
  • Compare with recent deploys on your side, so a coincidental change is not blamed on the vendor.
  • Follow the vendor's official incident page for scope changes and resolution.

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. Sep 3, 2026, 16:44 UTCVendor-reported startVendor time

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