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

MinorStatus: resolvededitedStarted 2026-10-20 07:32 UTCResolved 2026-10-20 20:09 UTC (13 h)4 updatesstspg.io

Summary

MongoDB Atlas changed the reported impact of the GCP Availability Zone europe-west2-b connectivity incident from none to minor, indicating customer-facing impact. The evidence provides no start time, duration, cause or fix.

Machine-written from the archived incident (Sol). Check the timeline before relying on it.

Part of an outage event

Google Cloud europe-west2 outage, Oct 20, 2026 · 19 vendors, 19 incidents

MongoDB Atlas’s incident blames Google Cloud as the cause. (hop 1, posted +1 h 25 min vs Google Cloud’s own post)

“…GCP Availability Zone europe-west2-b connectivity issues This incident has been resolved. Since 0600 UTC we have observed cluster node connectivity issues isolated to a single availability zone, GCP e…”

Swipe sideways to see the whole diagram.

MongoDB Atlas is outlined in red. Groups show up to a few vendors each; the event page lists every incident.

Mermaid source

flowchart LR
  root["Google Cloud europe-west2<br/>posted 06:08 UTC"]:::root
  before["Posted before Google Cloud did<br/>1 vendor, 1 blamed Google Cloud<br/>JFrog"]:::blames
  root --> before
  h1["Within an hour<br/>4 vendors, 4 blamed Google Cloud<br/>Aiven, Northflank, Elastic Cloud, dbt Labs"]:::blames
  root --> h1
  h4["1 to 4 hours later<br/>4 vendors, 4 blamed Google Cloud<br/>MongoDB Atlas, Sourcegraph, CockroachDB, ClickHouse Cloud"]:::blames
  root --> h4
  later["Later<br/>2 vendors, 1 blamed Google Cloud<br/>Grafana Cloud, Confluent"]:::blames
  root --> later
  me["MongoDB Atlas (this incident)<br/>posted +1 h 25 min"]:::me
  h4 --- me

Full event: timeline, evidence and all vendors →

Detected automatically from incidents that started together and named the same provider. A link means one vendor’s incident named another, not a confirmed cause.

Affected components: MongoDB Cloud

Timeline of updates

identified2026-10-20 07:32 UTC
Since 0600 UTC we have observed cluster node connectivity issues isolated to a single availability zone, GCP europe-west2-b.
Atlas clusters are distributed across multiple AZs and 3-node clusters can continue to serve reads and writes from nodes in the other 2 Availability Zones in this region.
We are working with our partners to resolve the cause of the issue and restore service to the affected nodes.
identified2026-10-20 08:38 UTC
The Google Cloud status page has been updated to report further information, follow this link for details https://status.cloud.google.com/incidents/Xs2XTHzAVC9YnafnPyzj (opens in new tab)
monitoring2026-10-20 11:43 UTC
We are seeing signs of Availability Zone connectivity improving and are continuing to monitor.
resolved2026-10-20 20:09 UTC
This incident has been resolved.

Changes Rewindex caught on this incident

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.

How the archive is checked, and what it cannot prove.

Rewindex captured this after the last checkpoint; the next run (00:41 UTC) commits it.

Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).

MongoDB Atlas profile Recent MongoDB Atlas incidents Markdown JSON