Skip to content
Back to MongoDB AtlasIncident Postmortem
MongoDB Atlas logo

MongoDB Atlas

Tracked by PulseWatch

Auto-drafted postmortem

MongoDB Atlas outage on May 2 — 104d 1h disruption

May 2, 05:28 AM → Aug 14, 07:00 AM · 104d 1h · high

An incident affecting MongoDB Atlas was detected due to an elevated volume of user reports. The disruption began on May 2, 2026, at 05:28 UTC. The service was fully restored on August 14, 2026, at 07:00 UTC.

Peak reports
14
in 15 min
Total reports
325
during the incident
Duration
104d 1h
tracked by PulseWatch

Impact

Users experienced a high severity disruption to MongoDB Atlas, detected through an elevated volume of user reports. A total of 325 reports were received during the incident, with a peak of 14 reports in a 15-minute period. The most frequently reported issues included "Website down" (282 reports), "API issues" (36 reports), and "Service disruption" (7 reports). No specific regional impact was recorded during this period.

Top reported issues

  • Website down282
  • API issues36
  • Service disruption7

Incident timeline

  1. May 2, 05:28 AM

    PulseWatch detected elevated report volume (high severity)

  2. May 3, 11:28 AM

    Status updated: possible issue

  3. May 3, 05:38 PM

    Status updated: major issue

  4. Aug 14, 07:00 AM

    Report volume returned to baseline — incident resolved

Official updates

  1. May 2, 05:28 AM

    MongoDB Atlas status page acknowledged the incident.

    View official source
Draft auto-generated by PulseWatch when the incident resolved. Based on aggregated user-report signals and the sources listed above.
This postmortem was auto-generated from PulseWatch's record of the incident. · Model: gemini-2.5-flash