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

GCP Availability Zone europe-west2-b connectivity issues

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

Vendor start
Oct 20, 2026, 07:32 UTC
Vendor's clock
Resolved
Oct 20, 2026, 20:09 UTC
Vendor's clock
First seen by Statuswall
Before tracking began
Statuswall's clock
Duration
12 h 36 min
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: "GCP Availability Zone europe-west2-b connectivity issues".[E1, E2]
  • The vendor marked it resolved at 2026-10-20 20:09 UTC.[E3, E7]

Affected products and regions

  • Regions: europe-west2 (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-10-20 20:09 UTC · summary s1, evidence 194755c8b272bb20

Evidence (7)
  1. E1MongoDB Atlas reports degraded. (vendor) source (opens in a new tab)
  2. E2Vendor title: "GCP Availability Zone europe-west2-b connectivity issues". (vendor) source (opens in a new tab)
  3. E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
  4. E4Vendor-reported start: 2026-10-20 07:32 UTC. (vendor) source (opens in a new tab)
  5. E5Regions written in the title (inferred): europe-west2. (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-10-20 20:09 UTC. (vendor) source (opens in a new tab)

Affected scope

europe-west2

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. Oct 20, 2026, 07:32 UTCVendor-reported startVendor time
  2. Oct 20, 2026, 20:09 UTCVendor-reported resolutionVendor time

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

MongoDB Atlas: GCP Availability Zone europe-west2-b connectivity issues — statuswall