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 September 16 (tracked 6d 7h)

Sep 16, 09:15 AM → Sep 22, 04:46 PM · 6d 7h · 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 6d 7h, from Wed, 16 Sep 2026 09:15:50 GMT to Tue, 22 Sep 2026 16:46:12 GMT. That is how long PulseWatch kept the incident open, not a measurement of how long the service was affected.

Duration
6d 7h
tracked by PulseWatch

Impact

PulseWatch recorded no user reports for this incident, so it cannot describe what users experienced. The vendor's own status page is the only source PulseWatch has for it.

Incident timeline

  1. Sep 16, 09:15 AM

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

  2. Sep 16, 09:15 AM

    Status updated: possible issue

  3. Sep 22, 04:46 PM

    PulseWatch closed the incident

Official updates

  1. Sep 16, 09:15 AM

    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: fallback