MongoDB incident

Trigger processing may be delayed globally

Major Resolved View vendor source →

MongoDB experienced a major incident on October 1, 2026 affecting MongoDB Atlas App Services and Device Sync, lasting 5h 12m. The incident has been resolved; the full update timeline is below.

Started
Oct 01, 2026, 03:41 PM UTC
Resolved
Oct 01, 2026, 08:54 PM UTC
Duration
5h 12m
Detected by Pingoru
Oct 01, 2026, 03:41 PM UTC

Affected components

MongoDB Atlas App Services and Device Sync

Update timeline

  1. investigating Oct 01, 2026, 03:41 PM UTC

    As of approximately 15:00 UTC, some users of MongoDB Atlas Triggers in AWS ap-southeast-2 may experience delayed unordered trigger processing. We are investigating and working to restore normal processing.

  2. investigating Oct 01, 2026, 06:21 PM UTC

    We are continuing to investigate this issue.

  3. investigating Oct 01, 2026, 07:51 PM UTC

    Some users may find that their Atlas Triggers are not firing or are not visible in the Atlas UI. We are investigating both symptoms and working to restore trigger processing. We will provide another update as we learn more.

  4. monitoring Oct 01, 2026, 07:59 PM UTC

    Atlas Triggers are firing again, and trigger processing is operational. We are monitoring the service and verifying the status of triggers affected during the incident, including any delayed events. We will provide a further update once verification is complete.

  5. resolved Oct 01, 2026, 08:54 PM UTC

    This incident has been resolved.