rewindex

ChangesMongoDB AtlasGCP Availability Zone europe-west2-b connectivity issues

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

Incident updateNot classified yetChanged stspg.io (opens in new tab)
Summary

Summary pending. The diff below shows exactly what changed.

Incident page: the full timeline of updates

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…”

See the cascade chart and every vendor →

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.

What changed

Struck in red is what MongoDB Atlas removed; blue is what they added. Muted text is unchanged context.

ChangedStatus#1
Before: monitoring
After: resolved
AddedResolved time#2
Before: not present
After: 2026-10-20 20:09 UTC
AddedUpdateresolved#3
Before: not present
After: This incident has been resolved.

Compared with the previous archived version of this incident (10 to 30-minute polling). View the live incident (opens in new tab).

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. That proves these records existed by then and have not been changed since, by anyone, Rewindex included.

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

History of this incident

YesterdayTuesday, October 20Tue, Oct 20

1 rewrite, 3 incident changes

All MongoDB Atlas changesMongoDB Atlas profileMarkdownJSON