Skip to content
Back to MongoDB AtlasIncident Postmortem
MongoDB Atlas logo

MongoDB Atlas

Tracked by PulseWatch

Auto-drafted postmortem

MongoDB Atlas outage on May 3 — 102d 13h disruption

May 3, 05:14 PM → Aug 14, 07:00 AM · 102d 13h · high

On May 3, 2026, an incident affecting MongoDB Atlas was detected due to an elevated volume of user reports. The service experienced a high-severity disruption. The incident was resolved on August 14, 2026.

Peak reports
26
in 15 min
Total reports
279
during the incident
Duration
102d 13h
tracked by PulseWatch

Impact

The incident was characterized by a significant increase in user-reported issues, with a peak of 26 reports within a 15-minute period. A total of 279 user reports were received throughout the duration of the incident. The most frequently reported issue types included "Website down" (248 reports), "API issues" (27 reports), and "Service disruption" (4 reports). No specific regional impact was recorded during this time.

Top reported issues

  • Website down248
  • API issues27
  • Service disruption4

Incident timeline

  1. May 3, 05:14 PM

    PulseWatch detected elevated report volume (high severity)

  2. May 4, 03:28 AM

    Status updated: major issue

  3. Aug 14, 07:00 AM

    Report volume returned to baseline — incident resolved

Official updates

  1. May 3, 05:14 PM

    MongoDB Atlas status page acknowledged the incident.

    View official source
  2. Aug 14, 07:00 AM

    Service disruption clustered from 2 sources across 26 signals. Suppressed 25 redundant alerts and flagged flapping behavior.

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