Live / MongoDB Cloud / Incident
MongoDB Cloud: GCP Availability Zone europe-west2-b connectivity issues
MongoDB Cloud · mongodb.comMinor incidentResolved2026-10-20 20:09 UTC
Public — what happened
Summary
MongoDB Cloud said it saw cluster nodes losing connectivity in one Google Cloud zone, europe-west2-b, beginning around 0600 UTC on 2026-10-20. The company said its Atlas clusters are spread across several zones, so three-node clusters could keep handling reads and writes from nodes in the other two zones. It said it was working with partners on the cause and later pointed to a Google Cloud status page for more details. By 11:43 UTC it reported connectivity improving and was monitoring, and the incident was marked resolved at 20:09.
Affected
MongoDB Cloud
Timeline
- Started — 2026-10-20 07:32 UTC
- Identified — 2026-10-20 07:32 UTC (2 updates)
- Monitoring — 2026-10-20 11:43 UTC
- Resolved — 2026-10-20 20:09 UTC · 12h 36m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach MongoDB Cloud against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for MongoDB Cloud: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the MongoDB Cloud report →
More from MongoDB Cloud
Covered in The Squid’s Ink, Week 44, 2026, our weekly internet health report.