Skip to content
Back to MongoDB AtlasIncident Postmortem
MongoDB Atlas logo

MongoDB Atlas

Reported by the vendor · tracked by PulseWatch

Auto-drafted postmortem

MongoDB Atlas: vendor-reported major incident on October 1 (tracked 1h 44m)

Oct 1, 07:56 PM → Oct 1, 09:40 PM · 1h 44m · high

MongoDB Atlas reported a major-impact incident on its own status page. PulseWatch followed the vendor's status page and did not independently confirm the incident. PulseWatch tracked the incident for 1h 44m, from Thu, 01 Oct 2026 19:56:12 GMT to Thu, 01 Oct 2026 21:40:56 GMT. That is how long PulseWatch kept the incident open, not a measurement of how long the service was affected.

Duration
1h 44m
tracked by PulseWatch

Impact

During the 1 hour and 44 minute high-severity incident, MongoDB Atlas services experienced disruption. This event was identified through automated signals, including the vendor's own status page. No user-reported data was collected for this incident, and therefore no specific user-reported features, regions, or issue types can be detailed.

Incident timeline

  1. Oct 1, 07:56 PM

    The vendor reported a major-impact incident on its own status page; PulseWatch began tracking it

  2. Oct 1, 07:56 PM

    Status updated: possible issue

  3. Oct 1, 09:40 PM

    PulseWatch closed the incident

Official updates

  1. Oct 1, 07:56 PM

    MongoDB Atlas reported the incident on its status page.

    View official source
Draft auto-generated by PulseWatch when the incident resolved. Based on the vendor's own status page.
This postmortem was auto-generated from PulseWatch's record of the incident. · Model: gemini-2.5-flash